83
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 22 Jan 2024
83 points (86.7% liked)
Selfhosted
61475 readers
1192 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
It would appear that blocking
app.posthog.comon the host/network resolves this. But I got the parameter to work, too, as per https://www.usememos.com/docs/advanced-settings/metrics use'--metric=false'and bam, no DNS queries!Yeah, I’d assumed it would respect the —metric=false flag when building with docker run, but docker-compose is ostensibly supported and easier to work with. I was able to successfully change other configuration options (such as setting the db to use MySQL instead of the default SQLite) using the docker-compose ‘command’ block, but the metric flag specifically was ignored. It’s entirely possible that this is a bug and not an intentional attempt to hoover up user data. Either way, data collection should be opt-in by default (by law, imo).
Ah - I actually moved away from Memos (I just wasn't using it and it was taking resources for no benefit) so I can't actually directly help, buuuuuut I want to be optimistic and assume that the 'feature' was removed given the page 404ing.
You could use something like NextDNS (or any other DNS solutions that offer logging, I just use ND on my network), set up as the server's DNS provider, and see if the domain (above) shows up in the logs after a couple days. Though if you're running other software alongside it, then it might not be from Memos, which can lead you down a 'disable, wait, check, repeat' rabbit hole. But that's how I would do it, myself.
Sorry I don't have a quick and easy solution for you :(
If you remember, reply back - someone else will surely run across this and have the same question!