Emergency account of a not-so-average OpenSim avatar. Mostly active on Hubzilla.

  • 10 Posts
  • 78 Comments
Joined 1 year ago
cake
Cake day: June 25th, 2023

help-circle

  • No. The various Fediverse server applications are too different in how they work.

    First of all, it isn’t all just about object types. The architecture of various Fediverse server applications is vastly different, including how they handle objects, and how they distribute them.

    For example, on Mastodon, a thread is just a loose string of posts and more posts which, technically, are identical in properties. Mastodon doesn’t know conversations, and Mastodon doesn’t know groups. You receive the posts from those whom you follow plus, by default, the posts that mention you.

    Friendica does know conversations, and it knows groups because it has them implemented. On Friendica, a thread is one (1) post plus comments, just like on Facebook or on blogs. You receive the posts from those whom you’re connected with, but not their comments on other people’s posts. Plus, you receive all comments on posts from those whom you’re connected with. Receiving posts from those whom you’ve mentioned is optional but off by default AFAIK.

    Forte is like Friendica, but with nomadic identity. That obviously isn’t a client thing.

    Hubzilla and (streams) are like Forte, but with wholly different protocols that were made for nomadic identity in the first place and with ActivityPub as an optional extra.

    Lemmy, Mbin and PieFed are all about conversations and groups. You literally can’t follow Lemmy users (something that Mastodon users will never understand), you can only follow Lemmy communities (something that’s totally alien to many Mastodon users).

    There are many more differences.

    Mastodon’s HTML sanitiser that rips out most text formatting is on the server side AFAIK. If you make Mastodon the gold standard, say buh-bye to numbered lists, horizontal lines, tables etc. (And I’m not kidding, there are places in the Fediverse that support these. In posts.)

    Character limits are server-side. Since the huge majority of Fediverse users and many Fediverse devs think the Fediverse was made as a Twitter replacement, they also think that there has to be an arbitrary character limit, otherwise it wouldn’t be microblogging, right? Welll, then Friendica, Hubzilla, (streams) and Nomad can wave good-bye to their unlimited character counts and 100,000±character posts.

    Filters are server-side. And they work vastly differently on different Fediverse server apps. Some import filtered content and then delete it. Others reject it.

    Permissions are server-side. Permissions are absolutely essential and integral parts of Hubzilla, (streams) and Forte, but the entire rest of the Fediverse doesn’t even know they exist. Of course, it’d be great if everything down to mastodon.social implemented the (streams)/Forte permissions system, but it’d completely overwhelm those who came to mastodon.social in search of Twitter without Musk.

    Another feature that Friendica and Hubzilla could kiss good-bye if there was only one unified server backend are multiple profiles per account. Speaking of which, it’s farewell to multiple channels (identities, like accounts everywhere else) on one account/login for Hubzilla, (streams) and Forte. Unless everything else is willing to implement both.

    Lastly, Hubzilla has absolute literal shit-tons of features on top of even Friendica. Both have built-in file spaces, but Hubzilla has one with WebDAV connectivity (as do (streams) and Forte). Both have federated event calendars, but Hubzilla also uses it as a frontend for its built-in CalDAV calendar server (which is headless on (streams) and Forte). Hubzilla, (streams) and Forte have an optional CardDAV addressbook server. Hubzilla also has optional stuff like non-federating long-form articles, “cards” that work similarly, a simple built-in wiki engine for multiple wikis per channel with multiple pages each, support for simple webpages (the official Hubzilla website is on a Hubzilla channel) and so forth. I’m not even remotely kidding with any of this.

    If you want to unify Fediverse servers, they’d all have to become Hubzilla, but with nomadic ActivityPub.



  • First, Bluesky’s nomadic identity isn’t worth shit if nobody knows that there’s more than one instance.

    Next, it has yet to be proven to work because nobody has daily-driven it yet.

    Finally, if you want nomadic identity that’s actually proven to work, don’t join Bluesky. Join Hubzilla. Nomadic identity, established in 2012, some four years before Mastodon, daily-driven by probably hundreds or thousands of people since then.

    I’m not even kidding. The Fediverse had nomadic identity four years before it had Mastodon.




  • People want a 100%, 1:1, perfect clone of immediate pre-Musk Twitter. They want Twitter without Musk.

    Bluesky is a 100%, 1:1, perfect clone of immediate pre-Musk Twitter. It is Twitter without Musk.

    It looks exactly like Twitter, it feels exactly like Twitter (both the Web interface and the official app), and it’s for tech-illiterate dumb-dumbs.

    Only recently has an instance selector been added to the sign-up process of the official app, but Bluesky still markets itself to its users as the self-same kind of centralised monolithic silo as Twitter and Facebook.

    Mastodon has a vastly different UI and UX from immediate pre-Musk Twitter, but people don’t want to learn anything new. And truth be told, I’ve read from Misskey/Forkey users that Misskey and the Forkeys actually have an easier-to-use Web UI than Mastodon.

    Also, Mastodon advertises the fact that it’s decentralised with lots of instances to choose from, even though the gGmbH would rather want everyone to be on mastodon.social. This freaks people out.

    Joining Mastodon is actually no more difficult than joining Bluesky in practice because the official app railroads everyone to mastodon.social without forcing them. But people won’t know until they’ve actually installed and opened that app.

    The only reason why Mastodon grew so quickly to such an enormous size in late 2022 was because it was the only alternative to Twitter that anyone knew, including those who pulled Twitter users onto Mastodon. The only other advantage it had over anything else was that, unlike Twitter, it didn’t have Musk and uncontained droves of Nazis. Had people been sent to Akkoma or Calckey instead of Mastodon, it would have exploded the same.

    Inb4 “How can people use e-mail then?” That’s because everyone’s on Gmail, and many think e-mail is a proprietary Google product.








  • As an administrator, the only time you would want to turn on the public stream is if you are a public hub and accept new signups. It makes it easier for administrators and moderators to moderate the public content on their own server since they can see all public posts in one place. If someone is posting illegal content or spam, a moderator can see it, and remove it (and perhaps the user too).

    Even then, it wouldn’t be a federated public stream that’s in plain sight for any visitor. At most, it’d be a local pubstream in plain sight for anyone. Or a federated public stream only visible to local users.

    At least by German law, hubmins can be held liable for what’s happening on the pubstream because it’s happening on their “website”, and so they’re responsible for it. And remember that most public Hubzilla hubs and the two biggest ones are German.


  • And they can only connect to Threads because Meta doesn’t want to go after thousands of private single-user instances, clutter their blocklist with them and check every once in a while if they still exist to keep it from being clutterted too much.

    Also, at least on Hubzilla and (streams), it’s the single-user instances that are likely to have an actually public pubstream. But not necessarily the federated one that Threads wants.


  • If you decide to make it public. Or if you’re on something that doesn’t leave you any choice like Lemmy.

    If you’re on Hubzilla or (streams), and you’ve grokked it enough to use it accordingly, then you can actually post content in private to only selected users.

    There are two common fallacies. One, the Fediverse is inherently private because it isn’t corporate. Two, the Fediverse is inherently public because everything on Mastodon or Lemmy or whatever is the only Fediverse project you’re familiar with is public.



  • Hubzilla. Closely followed by the intentionally nameless fork of a fork… of Hubzilla that’s colloquially being referred to as (streams).

    Perks of both (excerpt):

    • not based on ActivityPub, it’s actually optional; you can turn/keep it off if you want to
    • nomadic identity; my channels are resilient against instance shutdown because they aren’t restricted to one instance
    • multiple channels = IDs on one and the same account/login; no need to register additional user accounts for this, and you can easily switch back and forth between channels
    • OpenWebAuth magic single sign-on, both client-side and server-side support
    • very extensive permission settings that let me control what I see, what I don’t see and what others can see and do
    • per-contact permission settings
    • per-channel blacklist/whitelist filter plus per-contact blacklist/whitelist filters plus keyword-triggered, automatically generated, reader-side content warnings, supporting regex and (except the latter) a special filter syntax for extra features
    • what’s “lists” on Mastodon is actually useful because you can use it both to filter your stream and to limit whom you send a post to, not to mention much easier to maintain
    • a concept of conversations, you can follow entire discussions, and you generally receive all replies to a post (something that at least Mastodon doesn’t have, by the way)
    • not only native support for discussion groups/forums, but they can and do host their own moderated discussion groups/forums (Mastodon has neither)
    • no arbitrary character limits, characters only limited by the instance database (on (streams), that’s theoretically over 24,000,000 characters for one post)
    • probably more text formatting options than your typical blogging platform and definitely more than any microblogging project in the Fediverse
    • full-blown blog posts rendered gracefully
    • non-standard BBcode tags for special features, often observer-aware
    • embedded links; no need to plaster URLs into your posts in plain sight
    • images can be embedded “in-line” within the post with text above them and text below them
    • no limit on how many images a post can have
    • unlimited poll options
    • multiple-word hashtags
    • post categories in addition to hashtags
    • tag cloud plus category cloud/list
    • quotes
    • “quote-tweets”
    • extensively customisable Web UI
    • built-in file storage with a built-in file manager, per-file and per-directory permissions settings and WebDAV support that’s used for images and other media you embed in your posts (unlike on Mastodon and Lemmy, you know where your uploaded images land, and you can delete them yourself if you need to)
    • federated event calendar with support for Event-type objects
    • built-in CalDAV calendar server (headless on (streams))
    • built-in CardDAV address book server (headless)
    • support for OAuth and OAuth2
    • modular; can be extended with official or, if available, third-party “apps”, widgets and themes

    Extra perks of Hubzilla:

    • currently more reliable
    • more active development
    • easier to get new users on board because hubs are listed on various Fediverse sites, and more public hubs are available
    • newer and more configurable version of the Redbasic theme
    • switchable night mode
    • multiple profiles per channel which can be assigned to certain connections
    • you can configure new connections before you confirm them
    • can also connect to diaspora*
    • can also subscribe to RSS and Atom feeds
    • event calendar also doubles as a basic frontend for the CalDAV server
    • non-federating, long-form articles
    • “cards” that work largely the same
    • built-in wiki engine based on either BBcode or Markdown for as many wikis of your own as you want to, each with as many pages as you want
    • support for webpages (the official Hubzilla website is on a Hubzilla channel itself)

    Extra perks of (streams):

    • more advanced
    • better integration of ActivityPub into the two supported nomadic protocols
    • contact suggestions also include ActivityPub contacts
    • new default theme in addition to an older Redbasic version
    • reworked, more powerful but easier-to-use permissions system
    • easier to use once you’re on board
    • supports BBcode, Markdown and HTML within the same post
    • can set Mastodon’s sensitive flag for images
    • built-in announcement/boost/repost/renote/repeat remover, no need to use filter syntax for that
    • extra protection against both mention spam and hashtag spam
    • alt-text can be added to images upon upload, no need to graft it into the image-embedding markup code
    • verification of external identities (available on Mastodon as well, but not on Hubzilla)