Lmk if you find out. Maybe something with… lasers?
Lmk if you find out. Maybe something with… lasers?
Why not leave it open? Haha, I’m just finding this thread a month later and would like a shirt…
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.
Is fondant a cake?
Hell yeah now Linux and I both will panic in style
Everything reminds me of her…
I feel like you’re taking this all a bit too seriously. Here’s a suggestion: if you don’t think the contests are fun or worthwhile, don’t submit anything and don’t look at the winners and especially don’t print any of the submitted designs.
At first I was with you.
Anyway. I’ve been finished on the toilet for a while now. Gonna go sit on the porch and drink coffee and listen to the birds and never think about the terrible, terrible injustices with Prusa’s contests again.
p.s. I think the contests are awesome and I love how Prusa engages the community and gets people thinking about new ideas.
Yeah, what the hell? I didn’t watch the video but one time use pads are crypto 101 first day of class kinda thing.
More or less, yes, but they only work in specific, emulated test environments unless you play Apple’s game and get them verified and signed and eventually in the App Store. The latest EU/GDPR stuff might change this a bit, though.
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).
All depends on what you collect, how it’s stored, how transparent you are about it, and how easy it is to opt out of. It can definitely be done well.
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.
Deck’em and Strategery
Elegant!