Comment on The crusade against Lemmy devs, lemmy.ml, and so-called "tankies"
vacuumflower@lemmy.sdf.org 5 weeks agoEnough of personal perspective to be banned for mentions of things they don’t like, or comments that can be interpreted in a myriad ways. Mods there consciously want people to fall in line. Fuck them, they are worthless idiots.
Not even talking about the surrealistic feeling of some fat American leftist who can’t read in Russian telling you sitting in walking distance from Gorky Park how you’re all wrong and superficial on bloody USSR. And they don’t get any ideas when you tell them that.
Cricket@lemmy.zip 5 weeks ago
Ok, fair enough, thanks for providing your perspective, but do you think that the proper way to address that is for everyone to defederate an instance that has a lot of good non-political content or for people who are bothered by the mods in political discussions there to block the instance or the problematic communities where the mods exercise a heavy hand?
vacuumflower@lemmy.sdf.org 5 weeks ago
I think talking about federated services is different from talking about federated data. In Lemmy they are the same, which is why it’s not a good architecture. In Usenet they were not the same, but outside of mammoth technology there’s no similar solution.
Think about bittorrent trackers. They do serve the job of helping peers find each other. But nothing is tied to them, mostly, outside of many closed ones.
Lemmy instances also provide storage and relay services, functionally.
All of these can be separate, and user identities can be untied from instances of some service.
Trackers help you find relays and storage nodes serving specific users and groups. User and group identities are cryptographic (hope so, but one can have separate authentication services, why the hell not ; then it may be analogous to Lemmy instances in regards to bans and moderation).
Doing that isn’t easy, though. But I suppose a competent programmer can implement a tracker (simplest by far - announce, clear, request and storage, the tracker just has to check signatures if identity is, say, hash of public key), a storage service (an object storage with authentication, similar to previous, but perhaps paid with additional registration for that identity), a relay (not much more complex than a toy chat server, but perhaps similar to storage service) and a client application (that one is complex, but not too much, because all the logic of finding stuff by trackers and assembling\replaying group\user\post states is on the client) in not too horrible time.
OK, I’ve started writing a prototype for that in an TCL/Tk recently, lost willpower (ASD, BAD, bad sleep, bad food habits) after adding replays and before adding networking, and when thinking about convenience of integration with ready libraries and such, suspect C or C++ from the beginning would be easier. Bitwise operations not being PITA as a bonus.
Cricket@lemmy.zip 5 weeks ago
Thanks, there’s an interesting technical discussion to be had about how to address these issues with Lemmy and the Fediverse in general. I’m not much of an actual programmer although I’ve programmed a lot in school over the years. With that caveat, nowadays I would be inclined to only start brand new coding projects using memory-safe languages. There are so many wonderful ones to choose from nowadays that are not only more secure but also more productive, and most of them can use C and C++ libraries.
Getting back to my previous message though, given the two choices that are currently available, defederate from an instance that may have some issues in some of their communities, or let users decide whether to block them, which one would you chose?
vacuumflower@lemmy.sdf.org 5 weeks ago
The latter.