Great tip! Might save someone some time troubleshooting that issue.

Ah, I didn’t know about the incomplete timeline / mesh propagation issue. Sounds like a notable incentive.

Why do people tend to pile onto the same instance? Is there some benefit I’m missing?

Input sanitization typically handles this as a string that only allows characters supported by the data type specified by the table field in question. A permissive strategy might scrub the string of unexpected characters. A strict one might throw an error. The point, however, is to prevent the evaluation of inputs as anything other than their intended type, whether or not reserved characters are present.

Thank you!

The only way to add a backdoor to E2EE is to make it not E2E, so I don’t see how apple bad here, in this case. Can somebody clue me in?

Nice! Hadn’t heard of this project. The old chromebooks are easy to find in e-waste lots, mostly from schools. Hardware’s not ancient. Presumably optimized for web services. Just a lot of broken screens and keyboards.

But if you stack ‘em like server blades in a beowulf cluster you might have a decently power-efficient and scalable host for microservices, web apps, lemmy instances, whatever. With UPS for each node lol. Basically free.

I dunno, could be a fun class project for the kids to learn on with a minimal budget?