Oh, and for the record, linux is ALSO a confusing hot mess for the average person. But until linux developers accept this,
I've heard the same kind of stuff about lots... lots of things that "will never catch on". Every one of those doomsayers were wrong. Some of them unfortunately, but still, they were all wrong.
God I wish someone went and finally fixed that. It's incredible that of all the FOSS and community stuff you can find on the internet, lemmy is the big one that can't even remotely be browsed via w3m / elinks / anything-without-Javascript.
If this later returns as ed.ch
(more streamlined and lightweight, minimal featureset, perhaps not even the ability to store remote files so as to avoid the CSAM issues, etc) it'll be The Day.
This is cursed in a cool way, and viceversa.
(Me, I'm just using POSIX / regcomp; dunno if there's a handy C++ wrapper for it)
Some have thousands of followers and a few posts, but do we know if any of them are actually him? Including the newest one on .social…?
Easy. Did you check the reference back-link on their profiles?
Verification on Masto was solved long ago. Just post the adequate backlink on your site. it's literally the easiest simplest form available, not too different than "post this verification code in your profile".
You are right, other platforms (read: silos) would block or not even allow the system of putting a simple link or control code, but this is actually correct in that it demonstrates the point that this is not those people's official, verifiable site, it's the social media owner's. And thus just as trustable.
I would hav thought stuff like Lemmy would have configurations to eg.: not allow to upload images locally, only hotlink.
Anyway, an alternative is "zero knowledge" storage, where you don't know what you are storing (hence, you can't "choose" what to host or not host either). Another alternative is disjoint storage, where two different servers store different halves of a file (eg.: an Odd Bytes server and an Even Bytes server), but this means now it's necessary to hit more servers to recover a file.
But the sensible thing to do IMO is to apply "common carrier" concept. The water distribution company is not, to my knowledge, held liable when something happens like you fill a bucket of water and share it with someone else.
@lambalicious
@lemmy.sdf.org