Regardless of whether you are using a block or an allow list, you have to maintain the list...
I'm not sure what your point is; if you want to devote your time, effort, and potential liabilities to it, that's up to you. I just figured I would share a perspective on why I didn't want to do that.
I appreciate all the hard work done by instance hosts; using individual Lemmy instances are a privelege, not a right. I would fully understand and not be upset if my home instance were to shut down at a moments notice.
Sure, but then you're left with text only and are relying on your blocklist for URLs, which is just going to be a game of whack-a-mole. I personally didn't want to have to worry about that in my free time, but I'm sure other folks feel differently.
I self hosted a Lemmy instance for a little while, but I stopped over concerns of malicious actors posting CSAM which would then get federated over to my server. I don't have the appetite to deal with that, and I'm glad I shut it down because just a few weeks later there was a big instance of it happening all over Lemmy, and I'm sure I would have had to deal with cleaning it up on my server too. Just something to keep in mind.
Otherwise though, the setup process isn't too complex.
Frankly, once you get more than just a few cameras, being able to edit a config file is so much better than having to click through settings for literally hours like with Shinobi or Motioneye.
I've personally been quite pleased with the combination of Frigate and some Amcrest POE cameras. Just make sure the cameras you are getting support RTSP though and you should be able to use them with Frigate.
Also make sure you block the cameras from reaching the public internet using your firewall, and only make them reachable from your Frigate host. Personally I use a VLAN with no internet access and enforce tagging at the switch level (i.e. don't trust the cameras to maintain their own VLAN) settings.
Looks a lot like a carburetor float needle to me. It allows the flow of gasoline into the float bowl, which sets the amount of fuel fed into the engine.
It's common for float needles (and carb parts in general) to be made of brass, and the wire clip being made out of steel is also consistent with a float needle. The plastic tip is probably used for a better seal when the float is up, closing the needle port.
I wouldn't bother with vacuum bags If I were you. I think it's fine if you're using a drying box after the filament has been sitting out a while. Doesn't hurt to try and find out at least...
Personally, I just use a big plastic storage bin with a bunch of silica desiccant in it. I just busted out some polycarbonate (notoriously hydrophyllic) recently that had been sitting in there for 4+ months and printed straight away; no stringing or anything.
Never leave anything on the toilet tank lid - you may someday have to rush to get it off so that you can push the flapper down and stop any more water from going into the bowl.
I use the washable gluesticks for my polycarbonate prints. I just put PC prints under warm water for a few minutes and they pop right off. Gluesticks generally reduce bed adhesion though IME, so it's a fine line to walk; I never use gluesticks with PETG for example because then the parts don't stick to the bed enough.
This one is from 1988 (see the right edge, top). Larson already retired from being a cartoonist in 1995.
Presumably via Xwayland, but I haven't tried it.
No? last release was 1-1-2024...
I've had a good experience with Onboard.
Tt-rss has been reliable for me, and the frontend is decent. Not to mention you can just republish feeds for a different frontend to use.
18 grams of espresso beans produces 45 grams of espresso liquid when running the machine for 30 seconds.
Yup, that's true, and I am always open to and looking for new opportunities, but that also requires them to be interested in hiring me - not a trivial feat, especially in the current job market.
I'd also wager that the number of job positions writing OSS for organizations like that is much lower than proprietary job positions.
But you know what, I'll go shop around a little in my free time the next week or two. I'd love for (more of) my work to be publicly accessible and not locked up in a proprietary codebase.
Yup, as a software dev, I would love to be able to devote all my time to writing open source, but I gotta make money to live as well. Switching to working on OSS would be a huge leap of faith that there is someone out there willing pay/donate for my work. As it is, I think it will be my way of giving back once I have saved up enough money from my proprietary work, and hopefully I will be able to switch over sooner rather than later.
Maybe I'll go take a look at what the process is for getting grants from the government or non-profit orgs like Apache foundation...