If AI was reliable, maybe. MAYBE. But guess what? It turns out that “advanced autocomplete” does a shitty job of most things, and I bet false positives will be numerous.

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.

1. You’re mad that the contest was moderated?
2. Unsafe bath toys? That sounds bad. Your reason? Rubber bands and small parts? Okay well I don’t think that’s a problem if your kid is over the age of 3 or so. If less than 3, no reasonable parent would be leaving them unsupervised in the bath anyway.
3. PLA is great for quick proof of concept and handles exposure to water just fine in lots of cases. User discretion isn’t an unreasonable ask. The 3D printing community is an intelligent group, typically. If you love the print but your PLA version failed after a while, print it using something else?
4. Voters voted on the submissions they liked the most. Get over it.
5. Voters voted on the submissions they liked the most. Get over it.
6. Honestly I stopped reading. Something about a paid part integration that you got mad about because it’s heavily discounted and you can submit photos even if you don’t have one or something?

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.

Bon voyage!

I use Amcrest, mostly because the guy who makes frigate recommended them, and has affiliate links on his site. As a software developer myself, I have to say frigate (and HA) are two jewels of open source software and so I’m happy to support them however I can.

That being said, the cameras work well and are easy to integrate with both frigate and HA. They all try to phone home at first, but stop if you tell them to (I’ve confirmed this by monitoring the traffic on my dns servers).

I couldn’t find a privacy friendly wifi camera with a big enough battery to run continuously, so I ended up building my own with a solar panel, an inverter, and a 9ah lithium battery that sits on a fence post at the end of my driveway. It was a fun project, but I wish I could buy it.

Another small gripe is that the PTZ cameras from Amcrest all seem to be crazy expensive or have mixed reviews, so I’ve just held off on those for now.

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.

Neat!