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.
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.
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.
Presumably via Xwayland, but I haven't tried it.
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.
Coffee stain
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.
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.