this post was submitted on 22 Jan 2024
83 points (86.7% liked)

Selfhosted

39937 readers
363 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

Check out the live demo at https://demo.usememos.com/

you are viewing a single comment's thread
view the rest of the comments
[–] wreckedcarzz@lemmy.world 12 points 9 months ago (2 children)

It would appear that blocking app.posthog.com on 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!

[–] Jimbabwe@lemmy.world 4 points 9 months ago

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).