• 0 Posts
  • 8 Comments
Joined 1 year ago
cake
Cake day: September 18th, 2023

help-circle


  • The “joke” is that it’s an issue that people feel compelled to comment on, but the sleeping person can’t. Predictably, most people are blowing straight past this and commenting their opinions, but most of the other replies are joking or whimsical. Yours is straightforward no-nonsense. If I had to guess, I’d say that’s why you’re being singled out.




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



  • I thought I’d give this a shot, but the metrics/data collection flag was turned on by default and when I added a command to my docker-compose to turn them off, it was ignored. Then, I created an account and looked for a way to turn them off in the settings and there was none. You expect people interested in self-hosting OSS to be cool with sending data out of their network every time the server is started, a memo is created, a comment is created, a webhook is dispatched, a resource or a user is created?! Also, the metrics are collected by a 3rd party with their own ToS that could change at any time?

    Holy hell, hard pass. I’d rather use a piece of paper.