Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)MA
Posts
59
Comments
679
Joined
2 yr. ago

  • I already talked about why that matters in my post (didn't mention anything about a person's importance), but I'm happy to clarify and expand on it!

    To summarize again, this would allow users to follow a person across platforms. Part of the benefit of the fediverse is I can choose to get content from a microblogging platform as well as macro blogging or threaded like lemmy. It would be a good feature for me to be able to follow someone across all federated platforms without having to scavenge for them.

    Moreover, it would allow me to use other types of platforms without having to sign up on each one. This would also be useful for instance admins. If instance A trusts instance B, then it can allow instance B users to sign in without having to sign up separately.

    This could also mean that instance A could be an identity provider only

  • It is close to what I'm thinking, but the default flow would immediately start with the sign up process, choose a random instance (with good uptime record), and assume "general", unless otherwise specified (optionally).

  • I agree, but reliance on an instance is already a big issue.

    Theoretically, if this gets implemented, it could be possible to federate the ability to sign up elsewhere, or at least make your user downloadable and sign up with it elsewhere

  • If you choose a username, and I sign up with your same username before you do, then now you're screwed. So I agree this is a solution, but it is not without faults. No one prevents someone from signing up with your username (either maliciously or they just liked the same name)

  • Is it really neglected though? There are dedicated extensions for it, and movim.eu uses it without issues.

    XMPP's real strength is in real-time communication

    It's an extensible communication protocol and has been extended to many use cases, and has a good track record of performing well and handling extensions well. I'd argue this makes it a better candidate than activityPub.

    In a parallel universe, we may have had less federation issues had we gone xmpp!

  • Xmpp definitely wins in privacy. What is there to privacy more than message content and metadata? Matrix definitely fails the second one, and is E2E still an issue for public groups? I don't remember if they fixed that.

    XMPP being a protocol built for extensibility means it will be hard for it not to keep up with times.

    On your point of picking one or the other, I'd say pick the one you like and bridges will help you connect to the other. But XMPP came way before matrix, and I believe they fractured the community instead of building it.

    There's a good reason all the big techs built on top of xmpp (meta, Google, etc). It's a very good protocol and satisfies modern demands very well.

  • It worked more like true messaging app less than messages store ( unlike matrix ).

    Can you please elaborate this point? I don't understand what you mean by "true messaging app" and why that would be a bad thing?

    Requirement of permanent tcp ip connection

    Are you sure this is the case? Maybe back in the day, but my understanding is this isn't true anymore

    useful feature in xmpp ( like message history ) is optional

    Why is user choice a bad thing? There's a wealth of clients that implement the features you want

    If something doesn't work in xmpp most people would blame xmpp

    This may not be an important point, but from my experience, people always blame the client and not the underlying protocol. If I face an issue with my browser, I'd likely blame the browser before I blame http.

  • There's a reason nobody uses it anymore.

    I and many others use it! And Google, meta, etc. Have used it but decided to lock it down.

    Yes you're right, there's a reason people don't use it as much, which is because these corporations embraced it, dominated it, then extinguished it.

    But XMPP is honestly my favorite comm protocol and the most impressive imo.

  • What's the use for having update feeds in a unified format when I still have to go to each fucking site to view the full text

    This has nothing to do with RSS, it is the author's choice. It's like someone who posts links to their articles on Twitter / Facebook / Reddit, same thing. The platform doesn't prevent you from putting the entire content there, and in fact, many do, especially with RSS.

    One benefit of RSS though is that because it is an open protocol, the problem you mention already has solutions, which auto fetch the articles for you. That wouldn't be possible without an open protocol like RSS

    Moreover, I'd argue even with that, RSS is still a huge plus. To have all your content's headlines in one UI, and potentially you can filter or sort them however you want, that's pretty awesome.

  • Those problems you speak of about XMPP are not really a concern anymore and haven't been for a while.

    Matrix on the other hand is very difficult to implement, and currently there's only one (maybe two?) viable implementation choices. It is way over complicated, resource intensive, and has privacy issues.

  • As depressing as it sounds, most Twitter users actually like Twitter. They're fully okay with all of its dystopian features (some even idolize pre-Musk Twitter). Mastodon is a break from Twitter in many ways, whereas bluesky is just another Twitter in their eyes (many of them probably dgaf about federation and ignore it).