Lingolol

1 post1 participant0 posts today

Jupiter Rowland@<a href="https://mitra.social/users/weekinfediverse" rel="nofollow noopener noreferrer" target="_blank">Week in Fediverse :fediverse_light:</a> Also, <a href="https://fediversity.site/item/0d8c963e-b262-4154-9b00-141962917e7d?f=&zid=jupiter_rowland%40hub.netzgemeinde.eu" rel="nofollow noopener noreferrer" target="_blank">the 25.5.14 "15th anniversary" releases of the streams repository and Forte</a>. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=WeekInFediverse" rel="nofollow noopener noreferrer" target="_blank">WeekInFediverse</a>

small circle 🕊 in calmness<a href="https://hollo.social/@hongminhee" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@hongminhee</a> <a href="https://hachyderm.io/@thisismissem" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@thisismissem</a> <a href="https://mastodon.social/@PuercoPop" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@PuercoPop</a> For your information, I recently opened an issue to track current <a href="https://social.coop/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityPub</a> C2S implementations.This is the list thus far: <a href="https://social.coop/tags/ActivityPods" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ActivityPods</a> <a href="https://social.coop/tags/Epicyon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Epicyon</a> <a href="https://social.coop/tags/Onepage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Onepage</a>.pub <a href="https://social.coop/tags/Pleroma" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Pleroma</a> <a href="https://social.coop/tags/RDFPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RDFPub</a> <a href="https://social.coop/tags/Vocata" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Vocata</a> <a href="https://social.coop/tags/FedBOX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FedBOX</a> <a href="https://social.coop/tags/Mitra" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mitra</a> <a href="https://social.coop/tags/streams" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#streams</a> <a href="https://social.coop/tags/forte" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#forte</a><a href="https://codeberg.org/fediverse/delightful-fediverse-apps/issues/130" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://codeberg.org/fediverse/delightful-fediverse-apps/issues/130</a>Client-side <a href="https://social.coop/tags/AndStatus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AndStatus</a> is a well-known attempt to implement it:<a href="https://github.com/andstatus/andstatus/issues/499" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/andstatus/andstatus/issues/499</a>

Jupiter Rowland@<a href="https://social.vivaldi.net/@ajsadauskas" rel="nofollow noopener noreferrer" target="_blank">AJ Sadauskas</a> <blockquote>I mean, the Fediverse already has Lemmy, KBin, and MBin. So there's already an ecosystem of pre-built communities out there.</blockquote> /kbin is dead. Has been since last year. The last instances that haven't moved to Mbin are withering away. However, in the "Lemmy clone" category, there's also PieFed, and Sublinks is still in development. Also, the Facebook alternative <a href="https://joinfediverse.wiki/Friendica" rel="nofollow noopener noreferrer" target="_blank">Friendica</a> ("Facebook alternative" not as in "Facebook clone", but as in "better than Facebook") has had <a href="https://dir.friendica.social/group" rel="nofollow noopener noreferrer" target="_blank">groups</a> since its launch in, 2010, five and a half years before Mastodon. <a href="https://joinfediverse.wiki/Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> has had groups since 2012 when it still was a Friendica fork named Red. <a href="https://joinfediverse.wiki/(streams)" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> (2021) and <a href="https://codeberg.org/fortified/forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a> (2024) have groups, too. All four are part of the same software family, created by the same developer. And interacting with their groups from Mastodon is somewhat smoother than interacting with a Lemmy community. On Friendica, a group is simply another user account, but with different settings: In "Mastodon speak", it automatically boosts any DM sent to it to all its followers. In reality, it's a little more complicated because, unlike Mastodon, Friendica has a concept of threaded conversations. (No, seriously, Mastodon doesn't have it. If you think Mastodon has it, use Friendica for a year or two as your only daily driver, and then think again.) Likewise, on Hubzilla, (streams) and Forte, it's another <a href="https://joinfediverse.wiki/Channels_(Hubzilla_%26_(streams))" rel="nofollow noopener noreferrer" target="_blank">channel</a> with similar settings. CC: @<a href="https://sauropods.win/@futurebird" rel="nofollow noopener noreferrer" target="_blank">myrmepropagandist</a> @<a href="https://mastodon.social/@jasperb" rel="nofollow noopener noreferrer" target="_blank">Jasper Bienvenido</a> @<a href="https://mastodon.cc/@sebastian" rel="nofollow noopener noreferrer" target="_blank">sebastian büttrich</a> @<a href="https://pnw.zone/@Asbestos" rel="nofollow noopener noreferrer" target="_blank">Asbestos</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener noreferrer" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseGroups" rel="nofollow noopener noreferrer" target="_blank">FediverseGroups</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Groups" rel="nofollow noopener noreferrer" target="_blank">Groups</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=PieFed" rel="nofollow noopener noreferrer" target="_blank">PieFed</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Sublinks" rel="nofollow noopener noreferrer" target="_blank">Sublinks</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Friendica" rel="nofollow noopener noreferrer" target="_blank">Friendica</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a>

Jupiter Rowland@<a href="https://mastodon.social/@jorgecandeias" rel="nofollow noopener noreferrer" target="_blank">Jorge Candeias</a> Bad idea. (<a href="https://joinfediverse.wiki/Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> user here.) Hashtags are not only for discoverability (and critically so on Mastodon). They're also the preferred way of triggering the automatic generation of individual reader-side content warnings. Content warnings that are automatically generated for each user individually based on keyword lists have a long tradition in the Fediverse. Friendica has had them long before Mastodon even existed, much less before Mastodon hijacked the summary field for content warnings. Hubzilla has had them since its own inception which was before Mastodon, too. (streams) has them, Forte has them. On all four, automated reader-side content warnings are an integral part of their culture. And users of all four (those who are not recent Mastodon converts at least, i.e. those who entered the Fediverse by joining Friendica in the early 2010s) insist in automated reader-side content warnings being vastly better than Mastodon's poster-side content warnings that are forced upon everyone all the same. Oh, and by the way, Mastodon has this feature, too. It has only introduced it in October, 2022, and since the re-definition of Mastodon's culture in mid-2022 pre-dates it, it is not part of Mastodon's culture. But Mastodon has this feature. However, in order for these content warnings to be generated, there needs to be a trigger. The safest way is by hashtags: If you post content that not everyone may want to see, add corresponding hashtags, enough to cover as many people as possible. If you don't want to see certain content right away, add the corresponding hashtags as keywords to NSFW (Friendica, Hubzilla, (streams), Forte) or a CW-generating filter (Mastodon). In fact, hashtags can also be used to completely filter out content that you don't want to see at all. And they can be used to trigger such filters. This should work everywhere in the Fediverse. I myself post stuff that some people don't want to see all the time. Hence, I need a whole lot of hashtags. Let me explain the "hashtag wall" at the bottom of this comment to you. <ul><li>#<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a>, #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> This comment is over 500 characters long. Many Mastodon users don't want to see any content that exceeds 500 characters. They can filter either or both of these hashtags and at least get rid of my content with over 500 characters. Why two hashtags? Because I can't know beforehand which one of them people will filter. And because I can't know beforehand which of one of them people will search for or follow.</li><li>#<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a>, #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> The same as above, but making clear that it's supposed to stand in for a content warning ("CW: long (over 8,300 characters)"). Also, filtering these instead of the above has less of a chance of false positives than the above. Why two hashtags? Because I can't know beforehand which one of them people will filter. And because I can't know beforehand which of one of them people will search for or follow.</li><li>#<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a>, #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> This comment contains Fediverse meta content. Some people don't want to read anything about the Fediverse, not even as by-catch or boosted to them by someone whom they follow or even only on their federated timeline. They can filter either or both of these. Why two hashtags? Because I can't know beforehand which one of them people will filter. And because I can't know beforehand which of one of them people will search for or follow.</li><li>#<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a>, #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> The same as above, but making clear that it's supposed to stand in for a content warning ("CW: Fediverse meta" or, in this case, "CW: Fediverse meta, Fediverse-beyond-Mastodon meta"). Why two hashtags? Because I can't know beforehand which one of them people will filter. And because I can't know beforehand which of one of them people will search for or follow.</li><li>#<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener noreferrer" target="_blank">Fediverse</a> This comment is about the Fediverse. If you don't like it, you can filter it out. Otherwise, click it or tap it to find more content on the topic. Also, the hashtag helps people looking for content about the Fediverse find my comment.</li><li>#<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mastodon" rel="nofollow noopener noreferrer" target="_blank">Mastodon</a> This comment touches Mastodon as a topic. If you don't like it, you can filter it out. Otherwise, click it or tap it to find more content on the topic. Also, the hashtag helps people looking for content about Mastodon find my comment.</li><li>#<a class="" href="https://hub.netzgemeinde.eu/search?tag=Friendica" rel="nofollow noopener noreferrer" target="_blank">Friendica</a> This comment touches Friendica as a topic. If you don't like it, you can filter it out. Otherwise, click it or tap it to find more content on the topic, especially if you don't know what the hell <a href="https://friendi.ca" rel="nofollow noopener noreferrer" target="_blank">Friendica</a> is, but you're curious. Also, the hashtag helps people looking for content about Friendica find my comment.</li><li>#<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> This comment touches Hubzilla as a topic. If you don't like it, you can filter it out. Otherwise, click it or tap it to find more content on the topic, especially if you don't know what the hell <a href="https://hubzilla.org" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> is, but you're curious. Also, the hashtag helps people looking for content about Hubzilla find my comment.</li><li>#<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a>, #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> This comment touches (streams) as a topic. If you don't like it, you can filter it out. Otherwise, click it or tap it to find more content on the topic, especially if you don't know what the hell <a href="https://codeberg.org/streams/streams" rel="nofollow noopener noreferrer" target="_blank">the streams repository</a> is, but you're curious. Also, the hashtag helps people looking for content about (streams) find my comment. Why two hashtags if they're the same on Mastodon? Because they are not the same on Friendica, Hubzilla (again, that's where I am), (streams) itself and Forte. If I have to choose between catering to the technologies and cultures of Friendica, Hubzilla, (streams) and Forte and catering to Mastodon's, I will always choose the former.</li><li>#<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a> This comment touches Forte as a topic. If you don't like it, you can filter it out. Otherwise, click it or tap it to find more content on the topic, especially if you don't know what the hell <a href="https://codeberg.org/fortified/forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a> is, but you're curious. Also, the hashtag helps people looking for content about Forte find my comment.</li><li>#<a class="" href="https://hub.netzgemeinde.eu/search?tag=MastodonCulture" rel="nofollow noopener noreferrer" target="_blank">MastodonCulture</a> This comment touches Mastodon culture as a topic. If you don't like it, you can filter it out. Otherwise, click it or tap it to find more content on the topic, including critical views upon how Mastodon users try to force Mastodon's 2022 culture upon the users of Fediverse server applications that are very different from Mastodon, and that have had their own culture for much longer. Also, the hashtag helps people looking for content about Mastodon culture find my comment.</li><li>#<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hashtag" rel="nofollow noopener noreferrer" target="_blank">Hashtag</a>, #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hashtags" rel="nofollow noopener noreferrer" target="_blank">Hashtags</a> This comment touches hashtags as a topic. If you don't like it, you can filter it out. Otherwise, click it or tap it to find more content on the topic. Also, the hashtag helps people looking for content about hashtags and their implications find my comment. Why two hashtags? Because I can't know beforehand which one of them people will filter. And because I can't know beforehand which of one of them people will search for or follow.</li><li>#<a class="" href="https://hub.netzgemeinde.eu/search?tag=HashtagMeta" rel="nofollow noopener noreferrer" target="_blank">HashtagMeta</a> This comment contains hashtag meta content. Some people don't want to read anything about it, not even as by-catch or boosted to them by someone whom they follow or even only on their federated timeline. They can filter either it.</li><li>#<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWHashtagMeta" rel="nofollow noopener noreferrer" target="_blank">CWHashtagMeta</a> The same as above, but making clear that it's supposed to stand in for a content warning ("CW: hashtag meta").</li></ul> By the way: Hashtags for triggering filters are even more important on Hubzilla in comments when Mastodon users may see them. That's because Hubzilla cannot add Mastodon-style content warnings to comments (= everything that replies to something else; here on Hubzilla, it's very different from a post that isn't a reply). What's a content warning on Mastodon is still (and justifiedly so) a summary on Hubzilla. But from a traditional blogging point of view (Hubzilla can very much be used for full-fledged long-form blogging with all bells and whistles), a summary for a comment doesn't make sense. Thus, the comment editors have no summary field on Hubzilla. Thus, I can't add Mastodon-style CWs to comments here on Hubzilla. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener noreferrer" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mastodon" rel="nofollow noopener noreferrer" target="_blank">Mastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Friendica" rel="nofollow noopener noreferrer" target="_blank">Friendica</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MastodonCulture" rel="nofollow noopener noreferrer" target="_blank">MastodonCulture</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hashtag" rel="nofollow noopener noreferrer" target="_blank">Hashtag</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hashtags" rel="nofollow noopener noreferrer" target="_blank">Hashtags</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=HashtagMeta" rel="nofollow noopener noreferrer" target="_blank">HashtagMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWHashtagMeta" rel="nofollow noopener noreferrer" target="_blank">CWHashtagMeta</a>

Jupiter Rowland@<a href="https://io.waxandleather.com/@alisynthesis" rel="nofollow noopener noreferrer" target="_blank">Alison Wilder</a> Because if you want full-blown user rights and all the same features as a local user on all over 30,000 Fediverse instances, you need a local user account on each one of them. This means two things: <ul><li>If you come over to the Fediverse for the first time, and you register your first account on Mastodon, you automatically also register an account on 30,000+ more instances.</li><li>If you decide to host your own instance of whatever, and you spin it up for the first time, your instance immediately creates tens of millions of user accounts. One for everyone who has ever joined the Fediverse. Because anyone may decide to come over to your instance and use it, just like so.</li></ul> For one, this is utter overkill. Besides, this is technologically impossible. This would require all Fediverse instances to know all other Fediverse instances. With no exceptions. Like, if I start up my own (streams) instance for the first time, and half a second later, someone on the other side of the globe starts up a Gancio instance, they would immediately have to know each other. And all the other instances in the Fediverse. And, of course, it would require a newly-launched instance to know all Fediverse users. Again, with no exception. How and from which source are they supposed to know? That said, there is a single sign-on system for the Fediverse. It's called <a href="https://magicsignon.org/page/openwebauth/home" rel="nofollow noopener noreferrer" target="_blank">OpenWebAuth</a>. It was created by @<a class="" href="https://fediversity.site/channel/mikedev" rel="nofollow noopener noreferrer" target="_blank">Mike Macgirvin 🖥️</a> (creator of Friendica and all its descendants) in the late 2010s already for now-defunct <a href="https://joinfediverse.wiki/The_Zotlabs_projects#Zap" rel="nofollow noopener noreferrer" target="_blank">Zap</a>, a fork (of a fork?) of <a href="https://joinfediverse.wiki/Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> which, in turn, is a fork of the currently hyped Facebook alternative <a href="https://joinfediverse.wiki/Friendica" rel="nofollow noopener noreferrer" target="_blank">Friendica</a>. It was backported to Hubzilla in 2020. Everything that came after Zap, including the still existing <a href="https://joinfediverse.wiki/(streams)" rel="nofollow noopener noreferrer" target="_blank">streams repository</a>, got it, too. However, first of all, OpenWebAuth is only fully implemented on Hubzilla, (streams) and Forte. Plus, it has client-side support on Friendica. This means that Hubzilla, (streams) and Forte recognise logins on all four, but Friendica doesn't recognise logins from anywhere. As for Mastodon, OpenWebAuth implementation was actually developed to the point of an official merge request in Mastodon's GitHub repository. As far as I know, it was rejected. Mastodon won't implement OpenWebAuth, full stop. Besides, it doesn't give you all the same power as a local user. You can't log into Friendica, go to a Hubzilla hub and create a wiki or a webpage or a CalDAV calendar, just like so. OpenWebAuth is only for guest permissions. Because on Hubzilla, (streams) and Forte, permissions are everything. For example, let's assume you have an account and a channel on (streams). Let's also assume that your (streams) channel and this Hubzilla channel of mine here are connected. Furthermore, let's assume that I've decided to only allow my own full connections to see my profile. If you're logged out, and you go to my profile page, you see nothing. But then you log in. And you come back to my profile page (provided your browser is configured so that the Hubzilla hub that I call home is allowed to create cookies). My home hub recognises your login on (streams). It identifies you as you, as one of my contacts. Thus, it identifies you as someone who is permitted to see my profile. And all of a sudden, you see my profile. That, for example, is what OpenWebAuth is for. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener noreferrer" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Friendica" rel="nofollow noopener noreferrer" target="_blank">Friendica</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Zap" rel="nofollow noopener noreferrer" target="_blank">Zap</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=SingleSignOn" rel="nofollow noopener noreferrer" target="_blank">SingleSignOn</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=OpenWebAuth" rel="nofollow noopener noreferrer" target="_blank">OpenWebAuth</a>

Jupiter Rowland@<a href="https://stefanbohacek.online/@stefan" rel="nofollow noopener noreferrer" target="_blank">Stefan Bohacek</a> <blockquote>And yes, I hope better reply/interaction controls are coming soon, I know some of that is planned right after quote posts are finished. Really can't wait to see that!</blockquote> And that, too, will only work within Mastodon. Also, that, too, won't be a "Mastodon first" feature. At least Hubzilla, (streams) and Forte have reply and interaction controls included in their permissions systems which, in a way, work Fediverse-wide. Within themselves and each other, they actually make impossible what isn't allowed. For example, if you aren't allowed to repeat (= boost) or share (= quote-post) a post or a comment, you don't even have the button. These permissions aren't understood anywhere outside these three yet, but I've got higher hopes that this permissions system will be cast into FEPs than that Mastodon's hacks will be. In fact, Hubzilla, (streams) and Forte have reply control on three levels: <ul><li>channel-wide (who is generally allowed to reply; Hubzilla has eight levels, (streams) and Forte have three)</li><li>for individual connections</li><li>per post (on Hubzilla, commenting on a post can be disallowed altogether; on (streams) and Forte, additionally, commenting can be limited to your full connections, and a time can be defined from which commenting will no longer be allowed)</li></ul> Again, within these three, if commenting is not allowed, the UI elements for commenting will be missing. Outsiders may be able to comment, but all three block disallowed comments on a server level, i.e. they aren't deleted from the inbox, they are kept from entering the inbox in the first place. And so they don't appear in the thread for all those who support threaded conversations. It'd really be nice if this permissions system became one or a set of FEPs for others to pick up. CC: @<a href="https://climatejustice.social/@PaulaToThePeople" rel="nofollow noopener noreferrer" target="_blank">PaulaToThePeople</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener noreferrer" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ReplyControls" rel="nofollow noopener noreferrer" target="_blank">ReplyControls</a>

Jupiter Rowland@<a href="https://hachyderm.io/@juancho_me" rel="nofollow noopener noreferrer" target="_blank">Juancho</a> @<a href="https://mastodon.social/users/dansup" rel="nofollow noopener noreferrer" target="_blank">Daniel Supernault</a> Not the only one. Mike Macgirvin, the creator of Friendica and Hubzilla, has made a whole tree of at least (...counts...) nine forks after Hubzilla, eight of which were nomadic. Two of them still exist. One is intentionally nameless, intentionally brandless, intentionally not a project and intentionally released into the public domain. Since the community needed to address to it by something, they took the name of the code repository (which needed a name), put parentheses around it and called it <a href="https://codeberg.org/streams/streams" rel="nofollow noopener noreferrer" target="_blank">(streams)</a>. It's a fork (2021) of a fork (Roadhouse; 2021) of three forks (Osada, Mistpark 2020 a.k.a. Misty, Redmatrix 2020; 2020) of a fork (Zap; 2018) of maybe another fork (Osada; non-nomadic; 2018; if Zap was forked from Osada rather than directly from Hubzilla;) of Hubzilla. (streams) is reduced in features and connectivity in comparison with Hubzilla, but so were the first Osada and Zap. However, in terms of permission control and nomadicity, it's at least up-to-par with Hubzilla. In fact, it isn't quite as difficult to use as Hubzilla because permission handling has been adapted what the Fediverse of the 2020s actually requires as opposed to what a hypothetical Fediverse of the mid-2010s centred around the Red Matrix would require. I've made a series of tables that compare Mastodon, Friendica, Hubzilla and (streams). You can find them <a href="https://hub.netzgemeinde.eu/item/0a75de76-eb27-4149-b708-f20b2f79d392" rel="nofollow noopener noreferrer" target="_blank">here</a>. The other still existing fork is <a href="https://codeberg.org/fortified/forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a> from August, 2024. Forte is a direct fork of (streams). It's highly experimental because all support for the Nomad protocol was removed, and it has to rely on ActivityPub for nomadic identity. Thus, it is not officially released yet, it does not have public instances, and it is not recommended as a stable, reliable daily driver yet. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener noreferrer" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mastodon" rel="nofollow noopener noreferrer" target="_blank">Mastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Friendica" rel="nofollow noopener noreferrer" target="_blank">Friendica</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a>

Jupiter Rowland@<a href="https://flipboard.social/@mike" rel="nofollow noopener noreferrer" target="_blank">Mike McCue</a> Does this feed include anything concerning the guy who is the technological edge of the Fediverse personified, @<a class="" href="https://fediversity.site/channel/mikedev" rel="nofollow noopener noreferrer" target="_blank">Mike Macgirvin 🖥️</a>? #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Nomad" rel="nofollow noopener noreferrer" target="_blank">Nomad</a>

Jupiter's Fedi-Memes on (streams)Tired: Inviting Facebook users to Mastodon. Wired: Inviting Facebook users to Friendica. Hired: Inviting Facebook users to Hubzilla. Desired: Inviting Facebook users to (streams). Admired: Inviting Facebook users to Forte. Misfired: Inviting Facebook users to Lemmy. Expired: Inviting Facebook users to diaspora*. Fired: Inviting Facebook users to Bluesky. Explanation: Based on the <a href="https://knowyourmeme.com/memes/tired-wired" rel="nofollow noopener noreferrer" target="_blank">Tired/Wired</a> meme template. Inviting everyone to Mastodon has been the standard and in fact apparently with no alternative during the various Twitter migration waves. But Mastodon is a wannabe Twitter clone and not an appropriate replacement for Facebook. Those who invite Facebook users to Mastodon either don't know that there's more to the Fediverse than Mastodon. Or they haven't understood the Fediverse, they want to get into/stay in contact with those who come over from Facebook, and they can't for the lives of them imagine that Mastodon is federated with anything that isn't Mastodon. Or they're fanatic Mastodon supremacists who are fully convinced that Mastodon is best at everything. Or they simply can't stand the thought that someone could join something that isn't Mastodon. <a href="https://friendi.ca" rel="nofollow noopener noreferrer" target="_blank">Friendica</a> was launched in July, 2010, fourteen and a half years ago, five and a half years before Mastodon, and it was designed as an alternative to Facebook right away. Not as a clone, nobody wanted to make decentralised 1:1 clones of anything back then. But as something that's actually better than Facebook with features that Facebook can't offer, but that (not only) Facebook converts may find useful, while keeping everything that a social network needs. It's the only Facebook alternative in the Fediverse with native mobile apps available. But it is not the be-all, end-all Facebook alternative. <a href="https://hubzilla.org" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> came to life in early 2012 as a fork of Friendica by Friendica's own creator. It was created to implement the Zot protocol and nomadic identity. Originally named Red, renamed Red Matrix the same year, it was renamed and rebuilt into the "decentralised social CMS" Hubzilla in 2015. Its wealth in features is second to none in the Fediverse, its security and access permissions control is only matched by its own descendants. However, it also has the steepest learning curve of everything on the list. Still, the Hubzilla community is trying to get its share of Facebook refugees. <a href="https://codeberg.org/streams/streams" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> is from October, 2021, a fork of a fork of three forks of a fork (of a fork?) of Hubzilla by the same creator. And it's officially and intentionally nameless, brandless, not a project and released into the public domain. It's slimmed down in features from Hubzilla while still having features that Friendica lacks, it's dramatically slimmed down in non-nomadic connection options to only ActivityPub, but it's a lot easier to handle than Hubzilla because its handling has been optimised for the modern-day Fediverse and the way it's most likely being used. However, it is almost completely unknown outside of the Hubzilla community, and it needs both more users and more public instances. Getting people on board, however, is made more difficult by the few public instances being almost impossible to find. <a href="https://codeberg.org/fortified/forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a> is a (streams) fork by the same creator yet again from August, 2024. Essentially, it's (streams) without specialised nomadic protocols, only relying on ActivityPub even for nomadic identity and being the first to do so. Thus, it is highly experimental and potentially unstable, and it doesn't have any public instances. Still, a few people who aren't Forte's maintainer have set out or want to set out to try it, maybe even as a daily driver. If someone was crazy enough to set up a public, open-registration Forte instance for Facebook refugees, you could only admire their mixture of fearlessness and insanity. <a href="https://join-lemmy.org" rel="nofollow noopener noreferrer" target="_blank">Lemmy</a> is sometimes seen as an alternative to Facebook by those who reduce Facebook to its groups. But it's similarly far away from Facebook as Mastodon: It's an all-out Reddit clone. While Mastodon doesn't support groups, Lemmy supports nothing else. In addition, you'd have Facebook users, most of whom don't even know that something like Internet culture exists, end up in a place where shitposts, dank maymays, petty downvotes, power-trippin' mods and rampant xenophobia against anyone and everyone who wasn't raised on Reddit culture lurk around every corner. The same thing that's the natural habitat for Redditors who make up over 99% of all Lemmy users. <a href="https://diasporafoundation.org/" rel="nofollow noopener noreferrer" target="_blank">diaspora*</a> is considered the first Facebook alternative by those who don't consider Google+ the first Facebook alternative. However, not only is diaspora* pretty lack-lustre in comparison with Friendica and its descendants, but it's constantly shrinking. Shortly before New Year's Eve 2024, several big pods shut down, and depending on the statistics, diaspora* may have lost over half its users. Also, diaspora* may be decentralised, but it barely has any connections to the outside world, all of which were established from the outsie world (Friendica, Hubzilla, Socialhome) because diaspora* is not interested in federating with something else. Bluesky has as little to do with Facebook as Mastodon. It's something entirely different from Facebook. It's an all-out Twitter clone. Basically, switching from Facebook to Bluesky is akin to switching from Facebook to X. Bluesky may not be as ripe with Nazis, but it's for-profit, it's practically a centralised silo, and its enshittification is running at full steam. Whoever invites Facebook users to Bluesky out of all places hasn't understood anything. #<a class="hashtag" href="https://streams.elsmussols.net/search?tag=Facebook" rel="nofollow noopener noreferrer" target="_blank">Facebook</a> #<a class="hashtag" href="https://streams.elsmussols.net/search?tag=Facebook%20alternative" rel="nofollow noopener noreferrer" target="_blank">Facebook alternative</a> #<a class="hashtag" href="https://streams.elsmussols.net/search?tag=Mastodon" rel="nofollow noopener noreferrer" target="_blank">Mastodon</a> #<a class="hashtag" href="https://streams.elsmussols.net/search?tag=Friendica" rel="nofollow noopener noreferrer" target="_blank">Friendica</a> #<a class="hashtag" href="https://streams.elsmussols.net/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="hashtag" href="https://streams.elsmussols.net/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="hashtag" href="https://streams.elsmussols.net/search?tag=Forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a> #<a class="hashtag" href="https://streams.elsmussols.net/search?tag=Lemmy" rel="nofollow noopener noreferrer" target="_blank">Lemmy</a> #<a class="hashtag" href="https://streams.elsmussols.net/search?tag=diaspora%2A" rel="nofollow noopener noreferrer" target="_blank">diaspora*</a> #<a class="hashtag" href="https://streams.elsmussols.net/search?tag=Bluesky" rel="nofollow noopener noreferrer" target="_blank">Bluesky</a> #<a class="hashtag" href="https://streams.elsmussols.net/search?tag=Meme" rel="nofollow noopener noreferrer" target="_blank">Meme</a> #<a class="hashtag" href="https://streams.elsmussols.net/search?tag=FediMeme" rel="nofollow noopener noreferrer" target="_blank">FediMeme</a> #<a class="hashtag" href="https://streams.elsmussols.net/search?tag=Fediverse%20Meme" rel="nofollow noopener noreferrer" target="_blank">Fediverse Meme</a> #<a class="hashtag" href="https://streams.elsmussols.net/search?tag=Tired%2FWired" rel="nofollow noopener noreferrer" target="_blank">Tired/Wired</a>

Jupiter Rowland@<a href="https://triangletoot.party/@monkeyborg" rel="nofollow noopener noreferrer" target="_blank">monkϵyborg 🦾🐵</a> There is quite some talk about Hubzilla. Not so much on Mastodon, especially not widespread, but on Hubzilla itself, especially some of the Hubzilla forums on Hubzilla. There's quite a bit of criticism within Hubzilla where we actually know it inside out. As powerful as it is, it isn't exactly easy to use. Not so much because it's so complex (that, too; you can have used it since the 2010s and still learn something new), but because its default (and now only official) UI is too convoluted and too confusing. It's basically stuck in 2012 when Hubzilla was still Red, and even for 2012 standards, it isn't pretty. New features seem to have been slapped onto the UI randomly. There are even UI pages with no links to them. @<a class="" href="https://loves.tech/channel/scott" rel="nofollow noopener noreferrer" target="_blank">Scott M. Stolz</a> is working on all-new themes (which, by other Fediverse software standards, means entirely new UIs, but you can switch between them as a user). But I'm not sure if they will be officially shipped with new installs in the future. Tying in with this is that there is practically no mobile app for Hubzilla. All there is is a glorified Web app on F-Droid that hasn't been maintained in over five years. But there are no mobile apps with fully native mobile UIs in the Apple App Store and the Google Play Store, especially not official apps. This alone makes Hubzilla not only unattractive, but practically non-existent for phone users, even though Hubzilla can be installed as a PWA. Then again, in order for a native app to be useful and fully replace the Web UI for most users, it would have to be so massive and complex that FairEmail would pale in comparison. Also, while Hubzilla has a client API, no-one has ever tried to use it, so for all we know, it may not even work. Another issue which the community is working on fixing is the built-in documentation which is hopelessly outdated to the point of being outright wrong (I've seen parts that were last touched in 2012 because they still speak of Red), and which in some parts has always been incomplete. @<a class="" href="https://hub.hubzilla.hu/channel/pepecyb" rel="nofollow noopener noreferrer" target="_blank">Der Pepe (Hubzilla) ⁂ ⚝</a> <a href="https://help.hubzilla.hu/en/" rel="nofollow noopener noreferrer" target="_blank">has this covered</a>. He also has the <a href="https://info.hubzilla.hu/" rel="nofollow noopener noreferrer" target="_blank">Hubzilla KnowledgeDB</a> which is currently mostly in German. By the way: Since that article was published on Medium in 2017, Mike has done a whole lot more. A semi-chaotic tree of at least seven forks, all significantly slimmed down in comparison to Hubzilla, but increasingly modernised, before he presented <a href="https://codeberg.org/streams/streams" rel="nofollow noopener noreferrer" target="_blank">the streams repository</a> in October, 2021. It contains his latest stable creation which is intentionally not a project, without a name, without a brand, almost without any nodeinfo code and released into the public domain (except for some third-party add-ons). The community colloquially refers to it as (streams) with parentheses because it isn't really a name. (streams) may not be the super-powerful "decentralised social CMS" that Hubzilla is. But it's still powerful. It has advanced a lot, as has its underlying protocol which is named Nomad now. It only supports its own and Hubzilla's versions of Nomad plus ActivityPub, but modern-day Nomad is geared towards ActivityPub compatibility so well that ActivityPub no longer has to be an optional, off-by-default add-on; instead, it has been merged into the core. A few other things have been improved, too. The permission system has lost permission levels which no-one ever really needed or at least no-one needs anymore in today's Fediverse. In general, it has been made more secure by discarding the Public channel role and at the same time so easy and convenient to use that you don't even need a Public channel role anymore. Sometimes Hubzilla is being called outdated because it uses BBcode for text formatting in posts, comments, DMs and also the optional articles and cards (wikis can alternatively use Markdown; webpages can alternatively use Markdown or HTML). (streams) doesn't have articles, cards, wikis and webpages anymore, but in posts, comments and DMs, you can use BBcode, Markdown and HTML next to each other. BBcode won't disappear anytime soon, I guess, because some specific features are only available via BBcode. Officially, Mike has retired from Fediverse development at the end of last August, some two weeks after announcing his newest project, Forte (basically (streams) with only ActivityPub and therefore the first Fediverse software that relies on ActivityPub for nomadic identity). But this only means he has slowed down his development after a fast-paced summer. Both (streams) and Forte are still being developed. Forte is still so experimental that only Mike is using it for his secret private channel, but (streams) has stabilised again after a troublesome summer. And even if it relies on the browser or being installed as a PWA for mobile, too, and even if it direly lacks public instances (I only know two with open registration), it could make for another safe and modern Facebook alternative. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a>

Jupiter Rowland@<a href="https://newsmast.social/@newsmast" rel="nofollow noopener noreferrer" target="_blank">Newsmast Foundation</a> It's next to impossible to cover everything anyway. You'd have to follow a lot of sources. Not everything gets reposted/repeated/boosted/renoted; for example, Mike Macgirvin's development news are always private. And how do you, as a newscaster, want to keep up with the constant creation of new Forkeys? #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener noreferrer" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forkey" rel="nofollow noopener noreferrer" target="_blank">Forkey</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forkeys" rel="nofollow noopener noreferrer" target="_blank">Forkeys</a>

Jupiter RowlandDer Standard ist eigentlich PascalCase: Erster Buchstabe von jedem Wort ist groß. CamelCase wäre eher "camelCase", also erster Buchstabe des ersten Wortes klein, erster Buchstabe von allen anderen Wörtern groß. Aber das ist für die, die zu faul sind, Großbuchstaben zu schreiben. Am elegantesten sieht natürlich ein Hashtag aus mehreren Wörtern aus. Zumindest auf Hubzilla, (streams) und Forte kann man ihn mit Anführungszeichen generieren: <code>#"The Prodigy"</code>. In der Darstellung verschwinden dann die Anführungszeichen, und man sieht einen durchgängig linkenden Hashtag mit mehreren Wörtern. Eventuell geht das auch auf Friendica. Ich weiß jetzt allerdings nicht, wie gut das in Screenreadern funktioniert. Vorlesen können sie das definitiv, aber das Risiko besteht, daß sie einen Hashtag aus mehreren Wörtern nicht als Hashtag aus mehreren Wörtern erkennen und nur das erste Wort als Teil des Hashtags erkennen. In der Mastodon-Suche spielt das übrigens keine Rolle. Beim Indizieren von Hashtags schmeißt Mastodon alle Zeichen raus, die auf Mastodon in Hashtags nicht funktionieren. <code>#TheProdigy</code>, <code>#The-Prodigy</code> und <code>#"The Prodigy"</code> (das dann ja zu <code>#The Prodigy</code> wird) sind im Suchindex von Mastodon alle gleichermaßen <code>#TheProdigy</code>. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LangerPost" rel="nofollow noopener noreferrer" target="_blank">LangerPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLangerPost" rel="nofollow noopener noreferrer" target="_blank">CWLangerPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener noreferrer" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Friendica" rel="nofollow noopener noreferrer" target="_blank">Friendica</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hashtag" rel="nofollow noopener noreferrer" target="_blank">Hashtag</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hashtags" rel="nofollow noopener noreferrer" target="_blank">Hashtags</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=HashtagMeta" rel="nofollow noopener noreferrer" target="_blank">HashtagMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWHashtagMeta" rel="nofollow noopener noreferrer" target="_blank">CWHashtagMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ScreenReader" rel="nofollow noopener noreferrer" target="_blank">ScreenReader</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=A11y" rel="nofollow noopener noreferrer" target="_blank">A11y</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Accessibility" rel="nofollow noopener noreferrer" target="_blank">Accessibility</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Barrierefreiheit" rel="nofollow noopener noreferrer" target="_blank">Barrierefreiheit</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediTips" rel="nofollow noopener noreferrer" target="_blank">FediTips</a>

Jupiter Rowland@<a href="https://mastodon.social/users/Mrfunkedude" rel="nofollow noopener noreferrer" target="_blank">Mr. Funk E. Dude</a> The hashtag would be #<a class="" href="https://hub.netzgemeinde.eu/search?tag=EyeContact" rel="nofollow noopener noreferrer" target="_blank">EyeContact</a> And, in addition to the one above, if you really want to drive the point home that the hashtag is there with a content-warning function to a) trigger post-removing/post-rejecting filters, b) trigger post-hiding filters on Mastodon and c) trigger the "NSFW" post-hiding feature on Friendica, Hubzilla, (streams) and Forte: #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWEyeContact" rel="nofollow noopener noreferrer" target="_blank">CWEyeContact</a> I don't think there's any consensus on whether #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CW" rel="nofollow noopener noreferrer" target="_blank">CW</a> and #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarning" rel="nofollow noopener noreferrer" target="_blank">ContentWarning</a> should be used as actual content warning hashtags or for content warning discussions, which should be tagged #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWs" rel="nofollow noopener noreferrer" target="_blank">CWs</a>, #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarnings" rel="nofollow noopener noreferrer" target="_blank">ContentWarnings</a>, #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWMeta" rel="nofollow noopener noreferrer" target="_blank">CWMeta</a> and/or #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarningMeta%E2%81%A0" rel="nofollow noopener noreferrer" target="_blank">ContentWarningMeta⁠</a>, or for both. I mean, apart from #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CW" rel="nofollow noopener noreferrer" target="_blank">CW</a> being constantly used for either "continuous wave" in amateur radiotelegraphy or the CW Television network. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener noreferrer" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mastodon" rel="nofollow noopener noreferrer" target="_blank">Mastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Friendica" rel="nofollow noopener noreferrer" target="_blank">Friendica</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Filters" rel="nofollow noopener noreferrer" target="_blank">Filters</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediTips" rel="nofollow noopener noreferrer" target="_blank">FediTips</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hashtag" rel="nofollow noopener noreferrer" target="_blank">Hashtag</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hashtags" rel="nofollow noopener noreferrer" target="_blank">Hashtags</a>

Jupiter Rowland@<a href="https://mastodon.ar.al/users/aral" rel="nofollow noopener noreferrer" target="_blank">Aral Balkan</a> Does it only work with local content on instances with the Mastodon API? If so, that excludes any and all content from Fediverse instances without the Mastodon API, e.g. Hubzilla, (streams), Forte. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener noreferrer" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MastodonAPI" rel="nofollow noopener noreferrer" target="_blank">MastodonAPI</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a>

Jupiter Rowland@<a href="https://thefolklore.cafe/@juergen_hubert" rel="nofollow noopener noreferrer" target="_blank">Jürgen Hubert</a> There's hardly anything else that tries to get people on board by trying to pretend it's a monolithic silo like Mastodon. As far as contact discovery goes, that point goes to the actual social networking server apps in the Fediverse, the Facebook alternatives, rather than the microblogging server apps that are being misused as social networks. I think 𝕏 doesn't suggest potential new contacts to you, and Mastodon definitely doesn't. But Facebook does, and so do Friendica and the rest of its family (Hubzilla, (streams), Forte). (streams) could be the king of this because it can find both all kinds of ActivityPub actors (unlike Hubzilla) and actors using the nomadic protocols on which Hubzilla and (streams) itself are based (unlike Friendica), if only it had more and especially larger public instances. By the way, only a week ago, I wrote <a href="https://hub.netzgemeinde.eu/item/7a3cd8cd-3eee-481f-ac61-4c900551050a" rel="nofollow noopener noreferrer" target="_blank">an article about this</a>. Also, all four are better equipped for finding your own kind of people. You don't need instances for specific target audiences which newbies will almost never hear of. You don't have to fumble around with hashtags, not even knowing what the "right" hashtag for a certain topic is. That's because all four have native built-in support for discussion groups. Pretty much all the Fediverse can connect to these groups, but it's here where these groups are at home, and Mastodon doesn't even understand the concept of groups. Not to mention that, unlike Guppe groups, these groups can be moderated. And at least on Hubzilla, (streams) and Forte, they can be fully private so that non-members can't look inside and even hidden from public directories. As far as moderation goes, especially Hubzilla, (streams) and Forte are geared towards self-moderation. They have extensive permissions systems on three levels (per channel, per contact, per post). In combination with their understanding and system of conversations (which Mastodon completely lacks as well), you can moderate your own threads and even delete offending comments. Unfortunately, you can't have them purged from the whole Fediverse. Also, the reliance on self-moderation means that neither of the three has a Report button or even only a report system built in, so they don't understand Mastodon's report system either. If you need to report something to one of the instance admins, you'll have to send them a DM. Most public Hubzilla hubs only reveal who the admins are in the JSON-formatted siteinfo. On (streams) and Forte, you'll have to go to the directory, have only local channels shown, sort them by age and guess which of the oldest actually local channels are admins. That said, Hubzilla, (streams) and Forte have much more radical methods at hand for keeping unwanted stuff out than Mastodon. Most Fediverse server applications allow for admins to block entire instances, many, (streams) and Forte included, even give users this power. But (streams) and Forte have received a new feature called "user agent filter" in September which is capable of blocking entire Fediverse projects on a per-instance level. It was mainly designed as a more advanced counter-measure against Threads, but it can just as well be used to lock out the entirety of Mastodon, Glitch included, or the entirety of Pleroma, for example. It can even operate on an allowlist which, in addition to (streams)/Forte's own instances, only allows certain other server apps. And since Hubzilla and (streams) both aren't based on ActivityPub, and ActivityPub is optional on both, they can theoretically completely raise the drawbridge and cut everything based on ActivityPub off in one fell swoop. In this case, they can only interact with each other, and Hubzilla can also optionally interact with diaspora* and Friendica via the diaspora* protocol. In fact, I know one (streams) group where ActivityPub was deactivated with the very intention to keep Mastodon out. The main issue of all four has to be UX. None of the four has an official iOS and/or Android app. Friendica is from 2010 and designed for standard desktop browsers, and the others are the only survivors of a long family of forks. They can all be set up as progressive Web apps, but nobody knows what that even is, much less how to do that. Also, people need something with the same name as the server application that they can install from the Apple App Store or the Google Play Store. Friendica is the only one of the four with third-party apps with a native mobile UI. Even then, there's exactly one app readily available in the Apple App Store and the Google Play Store, RaccoonForFriendica, and it's so brand-new that it has only just had its first "stable" release (version 0.1.0). All that Hubzilla has is Nomad, an app only available on F-Droid that's a specialised browser for the Web interface, and that has last seen a new version almost five years ago. (streams) has nothing, Forte even less because it's so new and bleeding-edge that it currently has exactly one private instance with exactly one user. Truth be told, a mobile app with a fully native mobile UI for (streams) and Forte would be so deep that it'd rival K-9 Mail in complexity, and such an app for Hubzilla would be even more complex. Friendica supports the Mastodon client API, but no app out there that can be used with Friendica covers more than a small subset of Friendica's features. Basically, unless it's Fedilab, you're forced to use Friendica like Mastodon. In this regard, it'd be completely foolish to add the Mastodon client API to Hubzilla, (streams) or Forte. It wouldn't happen anyway because the devs refuse to have too much proprietary, non-standard Mastodon technology on board. One could say that the UX is a general issue. This is partially because, again, Friendica was geared towards the desktop almost one and a half decades ago with a Web UI designed by a protocol developer. At least, its UI has taken some cues from Misskey apparently. Hubzilla's only remaining theme was dolled up this year with more colour configuration options, but otherwise, its only available theme and therefore its entire UX is stuck in 2012 when it was still named Red. New third-party themes are still in development. And while (streams) got a brand-new, fresh theme (appropriately named Fresh) which Forte inherited, it isn't modelled in the style of a 2024 mobile app either. It certainly doesn't help that Friendica is a very complex piece of software. Forte is more complex. (streams) is another bit more complex. and Hubzilla is the most complex one of the four by far and, while technologically still more advanced than most of the Fediverse, stuck in 2012 in other UX-related things. In addition, Hubzilla is the only one of the four where you have to turn ActivityPub support on, and finding that "switch" is anything but straight-forward. What doesn't help either is people's expectations. I'd say that people escaping from Facebook might get used to Friendica without too many problems, probably more easily than Mastodon which works entirely differently. But what most people coming to the Fediverse are looking for is Twitter. Or something as close to Twitter as possible. You see it in the many Mastodonians who keep using Mastodon like Twitter. Bluesky is an all-out, 1:1 clone of Twitter from about ten years ago, all the way to appearing to be (and actually mostly being) a centralised, monolithic silo just like Twitter. Mastodon already repels people escaping from 𝕏 by both not really looking and feeling like Twitter and the prospect of having to choose an instance (which is FUD because the official app railroads newbies to mastodon.social). The millions who joined two years ago only joined because the vast majority of them were basically "told" that Mastodon, and therefore the Fediverse, is only one website: mastodon.social. Or mas.to. Or mstdn.social. You get the point, I guess. Friendica, Hubzilla, (streams) and Forte aren't Twitter clones. They don't aim to be just like Twitter with all its shortcomings included. They aim to be sort of like Facebook, but better, with extra features and with Facebook's shortcomings removed. Facebook looks, feels and works nothing like 𝕏. It never has. And so, these four are about as far away from being anything like 𝕏 as they could possibly be. And that's by design. But it isn't user-friendly to those who are looking for the closest thing to the official 𝕏 mobile app. CC: @<a href="https://hachyderm.io/@mekkaokereke" rel="nofollow noopener noreferrer" target="_blank">mekka okereke :verified:</a> @<a href="https://mas.to/@stooovie" rel="nofollow noopener noreferrer" target="_blank">Jiří Fiala Total Landscaping</a> @<a href="https://mstdn.social/@Remittancegirl" rel="nofollow noopener noreferrer" target="_blank">Madeleine Morris</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener noreferrer" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Friendica" rel="nofollow noopener noreferrer" target="_blank">Friendica</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Onboarding" rel="nofollow noopener noreferrer" target="_blank">Onboarding</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Moderation" rel="nofollow noopener noreferrer" target="_blank">Moderation</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=UI" rel="nofollow noopener noreferrer" target="_blank">UI</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=UX" rel="nofollow noopener noreferrer" target="_blank">UX</a>

Jupiter RowlandOne of the worst aspects of Mastodon's plans to introduce quote-posts with a switch: You keep having to tell Mastodon users that the Fediverse is not only Mastodon. That (insert a long list of Fediverse server applications here¹) have had quote-posts from the beginning. That they're all in the Fediverse. That they're all fully federated with Mastodon. That they can all quote-post any Mastodon toot they can possibly receive or import. And that they will be able to quote-post any Mastodon toot they can in the future, regardless of Mastodon account settings. Up until this point, they were fully, firmly convinced that they're 100% safe from quote-posts on Mastodon. Either because they could not for the lives of them imagine that anything in the Fediverse has them. Or simply because they "knew" up until this point that the Fediverse is Mastodon. And if Mastodon introduces an opt-out or opt-in switch, this switch will mean absolute, 100% water-tight safety from quote-posts. But for the Fediverse outside of Mastodon, the quote-post switch will be completely useless. Again: These lots of Fediverse server apps have had quote-posts before Mastodon introduced them. They had quote-posts before Mastodon invented the opt-in or opt-out switch. I mean, at least two of them have had quote-posts since before Mastodon even existed! So how are they supposed to support a proprietary, non-standard, Mastodon-specific switch which probably won't be documented anywhere before Mastodon rolls out quote-posts? I'll tell you what'll happen. Mastodon users will deactivate quote-posts for their accounts or not activate them in the first place. Non-Mastodon users, not knowing about the status of that switch, will quote-post them regardless with zero resistance. Upon which these Mastodon users will shit brix. And they'll call for either blocking that obviously rogue Mastodon user instance-wide, or blocking that user's instance, or Fediblocking that user's instance. At this point, someone else who is not on Mastodon either will chime in and tell them: That particular user is, in fact, not on Mastodon. The Fediverse is not only Mastodon. That user is on Friendica. No, Friendica is not a rogue Mastodon instance. Friendica is not Mastodon at all. No, Friendica isn't a Mastodon fork either. Friendica has nothing to do with Mastodon. In fact, Friendica is older than Mastodon. On Friendica, quote-posts are perfectly normal. Friendica has had quote-posts for longer than Mastodon has even existed. And so forth. Cue the Mastodon user shitting brix again, foaming with anger and calling for a Fediblock of all of Friendica. In fact, I'm pretty sure that if Mastodon's quote-post feature and the rest of the Fediverse disregarding it leads to more awareness of the non-Mastodon Fediverse and its non-Mastodon features on Mastodon, it will also lead to demands for being able to completely block everything that isn't Mastodon, either on an account level (and then on by default, of course) or on an instance level or both. Oh, by the way: The ability to completely lock out entire Fediverse projects already exists in the Fediverse right now, too. It's exclusive to two other Fediverse server apps that aren't Mastodon, both of which introduced this feature in September. ¹Here's a probably incomplete list of still-active Fediverse server apps with quote-posts which, yes, can quote-post Mastodon toots right now and will be able to quote-post Mastodon toots regardless of opt-in or opt-out: <ul><li>Pleroma</li><li>Akkoma</li><li>Misskey</li><li>Firefish</li><li>Sharkey</li><li>Iceshrimp</li><li>Iceshrimp.NET</li><li>CherryPick</li><li>Neko</li><li>Catodon</li><li>Meisskey</li><li>Tanukey</li><li>Metaskey</li><li>Mitra</li><li>Friendica</li><li>Hubzilla</li><li>(streams)</li><li>Forte</li></ul>And both Threads and the Bridgy Fed Bluesky bridge support quote-posts, too. (Inb4 both Oliphant and The Bad Space trying hard to catch all instances of the server apps mentioned above to blocklist them all.) #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener noreferrer" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=NotOnlyMastodon" rel="nofollow noopener noreferrer" target="_blank">NotOnlyMastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseIsNotMastodon" rel="nofollow noopener noreferrer" target="_blank">FediverseIsNotMastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MastodonIsNotTheFediverse" rel="nofollow noopener noreferrer" target="_blank">MastodonIsNotTheFediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mastodon" rel="nofollow noopener noreferrer" target="_blank">Mastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Pleroma" rel="nofollow noopener noreferrer" target="_blank">Pleroma</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Akkoma" rel="nofollow noopener noreferrer" target="_blank">Akkoma</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Misskey" rel="nofollow noopener noreferrer" target="_blank">Misskey</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Calckey" rel="nofollow noopener noreferrer" target="_blank">Calckey</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Firefish" rel="nofollow noopener noreferrer" target="_blank">Firefish</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Sharkey" rel="nofollow noopener noreferrer" target="_blank">Sharkey</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Iceshrimp" rel="nofollow noopener noreferrer" target="_blank">Iceshrimp</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Iceshrimp.NET" rel="nofollow noopener noreferrer" target="_blank">Iceshrimp.NET</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CherryPick" rel="nofollow noopener noreferrer" target="_blank">CherryPick</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Neko" rel="nofollow noopener noreferrer" target="_blank">Neko</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Catodon" rel="nofollow noopener noreferrer" target="_blank">Catodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Meisskey" rel="nofollow noopener noreferrer" target="_blank">Meisskey</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Tanukey" rel="nofollow noopener noreferrer" target="_blank">Tanukey</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Metaskey" rel="nofollow noopener noreferrer" target="_blank">Metaskey</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mitra" rel="nofollow noopener noreferrer" target="_blank">Mitra</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Friendica" rel="nofollow noopener noreferrer" target="_blank">Friendica</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Threads" rel="nofollow noopener noreferrer" target="_blank">Threads</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=BridgyFed" rel="nofollow noopener noreferrer" target="_blank">BridgyFed</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Bluesky" rel="nofollow noopener noreferrer" target="_blank">Bluesky</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuotePost" rel="nofollow noopener noreferrer" target="_blank">QuotePost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuotePosts" rel="nofollow noopener noreferrer" target="_blank">QuotePosts</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteTweet" rel="nofollow noopener noreferrer" target="_blank">QuoteTweet</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteTweets" rel="nofollow noopener noreferrer" target="_blank">QuoteTweets</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteToot" rel="nofollow noopener noreferrer" target="_blank">QuoteToot</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteToots" rel="nofollow noopener noreferrer" target="_blank">QuoteToots</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteBoost" rel="nofollow noopener noreferrer" target="_blank">QuoteBoost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteBoosts" rel="nofollow noopener noreferrer" target="_blank">QuoteBoosts</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuotedShares" rel="nofollow noopener noreferrer" target="_blank">QuotedShares</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuotePostDebate" rel="nofollow noopener noreferrer" target="_blank">QuotePostDebate</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteTootDebate" rel="nofollow noopener noreferrer" target="_blank">QuoteTootDebate</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediblockMeta" rel="nofollow noopener noreferrer" target="_blank">FediblockMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Oliphant" rel="nofollow noopener noreferrer" target="_blank">Oliphant</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=TheBadSpace" rel="nofollow noopener noreferrer" target="_blank">TheBadSpace</a>

Jupiter Rowland@<a href="https://infosec.exchange/@thenexusofprivacy" rel="nofollow noopener noreferrer" target="_blank">The Nexus of Privacy</a> A remark on "A Tale of Two Prototypes": The Fediverse did not start with Mastodon. You wrote that, quote, <blockquote>Mastodon and its forks have also prototyped [...] <ul><li>A <a href="https://privacy.thenexus.today/free-fediverses-and-consent/" rel="nofollow noopener noreferrer" target="_blank">consent-based culture</a> that (while imperfect and intermittent) points to a very different path than surveillance capitalism</li><li>A real-life testbed for all the complexities of decentralized moderation and federated diplomacy</li><li>A protocol-based platform for (somewhat) interoperaable social media operations</li></ul></blockquote> End quote. No, they didn't. Mastodon and Glitch invented next to nothing. It has all been there before 2016, before Mastodon, just like the Fediverse itself. Allow me to quote-post myself: <a href="https://hub.netzgemeinde.eu/channel/jupiter_rowland?f=&zid=lingo.lol%40lingo.lol" rel="nofollow noopener noreferrer" target="_blank"></a><a href="https://hub.netzgemeinde.eu/channel/jupiter_rowland?f=&zid=lingo.lol%40lingo.lol" rel="nofollow noopener noreferrer" target="_blank">Jupiter Rowland</a> schrieb den folgenden <a href="https://hub.netzgemeinde.eu/item/fc5844c4-9a5c-4cfc-b167-9be69833ba5e?f=&zid=lingo.lol%40lingo.lol" rel="nofollow noopener noreferrer" target="_blank">Beitrag</a> Tue, 05 Nov 2024 20:38:26 +0100 Three golden rules for the Fediverse. One: Whatever you think Eugen Rochko has invented in the Fediverse was most certainly actually invented by either Evan Prodromou or Mike Macgirvin long before Mastodon. Two: If you think the Fediverse should introduce a feature because Mastodon doesn't have it, the Fediverse most certainly does have it because any one of Mike Macgirvin's creations (<a href="https://joinfediverse.wiki/What_is_Friendica%3F" rel="nofollow noopener noreferrer" target="_blank">Friendica</a>, <a href="https://joinfediverse.wiki/What_is_Hubzilla%3F" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a>, <a href="https://codeberg.org/streams/streams" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> and/or <a href="https://codeberg.org/fortified/forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a>) has it. It's likely that other projects have it, too. And if it's on Friendica or Hubzilla, they've had it before Mastodon was made. Three: At no point in history has the Fediverse ever been only Mastodon. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fedi" rel="nofollow noopener noreferrer" target="_blank">Fedi</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener noreferrer" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mastodon" rel="nofollow noopener noreferrer" target="_blank">Mastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Friendica" rel="nofollow noopener noreferrer" target="_blank">Friendica</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=NotOnlyMastodon" rel="nofollow noopener noreferrer" target="_blank">NotOnlyMastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseIsNotMastodon" rel="nofollow noopener noreferrer" target="_blank">FediverseIsNotMastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MastodonIsNotTheFediverse" rel="nofollow noopener noreferrer" target="_blank">MastodonIsNotTheFediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fedi" rel="nofollow noopener noreferrer" target="_blank">Fedi</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener noreferrer" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mastodon" rel="nofollow noopener noreferrer" target="_blank">Mastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Friendica" rel="nofollow noopener noreferrer" target="_blank">Friendica</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=NotOnlyMastodon" rel="nofollow noopener noreferrer" target="_blank">NotOnlyMastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseIsNotMastodon" rel="nofollow noopener noreferrer" target="_blank">FediverseIsNotMastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MastodonIsNotTheFediverse" rel="nofollow noopener noreferrer" target="_blank">MastodonIsNotTheFediverse</a>

Jupiter Rowland@<a href="https://hachyderm.io/@jenniferplusplus" rel="nofollow noopener noreferrer" target="_blank">Jenniferplusplus</a> I sincerely hope that you aren't building Letterbook to only interact with itself and Mastodon. Sooner or later, Letterbook will encounter content coming in from instances of software created by @<a class="" href="https://fediversity.site/channel/mikedev" rel="nofollow noopener noreferrer" target="_blank">Mike Macgirvin ?️</a>, namely <a href="https://joinfediverse.wiki/What_is_Friendica%3F" rel="nofollow noopener noreferrer" target="_blank">Friendica</a>, <a href="https://joinfediverse.wiki/What_is_Hubzilla%3F" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> (these two are actually older than Mastodon), <a href="https://codeberg.org/streams/streams" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> or <a href="https://codeberg.org/fortified/forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a>. For reference: I am on Hubzilla. You/it will have to expect and be able to deal with the following: <ul><li>Enclosed one-post-many-comments conversations instead of threads that consist of posts loosely tied together</li><li>Permissions of all comments/replies firmly defined by the start post; permissions/visibility can't be changed within a running conversation</li><li>"Monster posts" of any length because none of them has a character limit</li><li>Not just Note-type objects, but also Article-type objects (from Friendica right now, the others may implement them once Mastodon introduces sensible support for them)</li><li>Full HTML text formatting, up to and including numbered lists, tables, horizontal lines, character size and character colour</li><li>Both quotes (as done in bulletin-board forums) and quote-posts (posts fully embedded in other posts like quote-tweets)</li><li>Embedded links (this comment makes a whole lot of use of them)</li><li>Inline images embedded within the text, and more than four of these in one post</li><li>Inline audio streams embedded within the text</li><li>Inline videos embedded within the text</li><li>"Weird" mentions and hashtags with the @ or the # not part of the link (look at the mentions and the hashtags in this comment, then look at mentions and hashtags on Mastodon and compare them)</li><li>"Summaries in the CW field" (because Mastodon repurposed StatusNet's summary field, which was used by StatusNet, Friendica and Hubzilla as an actual summary field, for content warnings in 2017; several Fediverse server apps continue to use it for summaries)</li><li>All four support titles in addition to summaries</li></ul> Some of the above may also come in from elsewhere, e.g. a wider range of text formatting than Mastodon allows itself to render is fully supported by just about everything that isn't Mastodon. Also, ActivityPub is currently evolving. New FEPs are being put to use and bringing in new features far away from how Mastodon is working. In particular, (streams) and Forte and @<a href="https://mitra.social/users/silverpill" rel="nofollow noopener noreferrer" target="_blank">silverpill</a>'s <a href="https://codeberg.org/silverpill/mitra" rel="nofollow noopener noreferrer" target="_blank">Mitra</a> use decentralised identifiers as per <a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61" rel="nofollow noopener noreferrer" target="_blank">FEP-ef61 (Portable Objects)</a>. Forte has <a href="https://joinfediverse.wiki/What_is_nomadic_identity%3F" rel="nofollow noopener noreferrer" target="_blank">nomadic identity</a> fully implemented via ActivityPub while (streams) at least supports it. And all three have <a href="https://codeberg.org/streams/streams/src/branch/release/doc/develop/en/Containers.mc" rel="nofollow noopener noreferrer" target="_blank">conversation containers</a> implemented, silverpill wants to make them <a href="https://codeberg.org/silverpill/feps/src/branch/main/171b/fep-171b.md" rel="nofollow noopener noreferrer" target="_blank">an FEP</a>, and Hubzilla is planning to implement them with version 10. This means three things. One, weird identifiers. Two, weird actor identities: What looks like one user automatically cross-posting to another account on another instance to non-nomadic ActivityPub implementations is actually the very same actor residing simultaneously on multiple server instances. Three, again, conversations work drastically different from Twitter and Mastodon. Lastly, it may be a good idea to implement a little server type display from the get-go so that the user knows what kind of Fediverse instance something comes from. Misskey and its forks have it, Friendica has it, (streams) has it, Forte has it. Just because Mastodon doesn't have it, doesn't mean it's a good idea not to have it. Besides, if content from certain server applications malfunctions on Letterbook, users can pinpoint right away what server application causes that trouble when submitting a bug report. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener noreferrer" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mitra" rel="nofollow noopener noreferrer" target="_blank">Mitra</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Friendica" rel="nofollow noopener noreferrer" target="_blank">Friendica</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Conversations" rel="nofollow noopener noreferrer" target="_blank">Conversations</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ConversationContainers" rel="nofollow noopener noreferrer" target="_blank">ConversationContainers</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FEP_ef61" rel="nofollow noopener noreferrer" target="_blank">FEP_ef61</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=NomadicIdentity" rel="nofollow noopener noreferrer" target="_blank">NomadicIdentity</a>

Jupiter RowlandOh, by the way, in case you haven't noticed because chances are that you actually haven't: Forte has entered the Fediverse yesterday. Mike Macgirvin has rebased his private, semi-secret instance from his own streams repository to his most recent project. Just yesterday, Mike sent the very first message from Forte into the Fediverse, a comment on a post from his public (streams) channel. Unfortunately, the whole thread is private, as is the comment. So, what is Forte? <a href="https://codeberg.org/fortified/forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a> is the very first and currently only Fediverse project that features nomadic identity via only ActivityPub. It's a fork of <a href="https://codeberg.org/streams/streams" rel="nofollow noopener noreferrer" target="_blank">the streams repository</a>, created in mid-August this year. To put it in a nutshell, Forte is (streams) without Nomad and without support for Zot, purely relying on ActivityPub. Also, unlike (streams), Forte has a name, it has a branding (which, however, can be changed on the instance level just like on (streams)), it has nodeinfo, it has a license, and it's a project again. At least as of now, Forte may have trouble connecting to Mastodon. This may be because Mastodon doesn't understand decentralised IDs as per FEP-ef61, it may be because Forte also had some non-standard, Mastodon-specific code removed. Or it may be due to the user agent filter that Mike has introduced to (streams) and most likely also Forte a few weeks ago that actually has the capability of, for example, blocking Mastodon in its entirety on an instance level. Whatever it is that may or may not stand in Mastodon's way of connecting with Forte, Mike declared it "intentional". Speaking of "intentional", I'm intentionally not posting this to Fediverse News. While this may go largely unnoticed outside the Hubzilla/(streams) bubble, maybe plus Friendica, it may just as well prompt people to set up their own instances. People who haven't even laid their hands on Friendica, much less Hubzilla or (streams), and who don't know how the "Facebook-like" side of the Fediverse looks and feels, much less how nomadic identity is handled. They may expect another "Mastodon + more characters + x on top", end up disappointed because nothing on Forte looks, feels or works like Twitter or Mastodon, and declare that Forte objectively sucks. Also, as long as Mike doesn't at least hint at Forte being stable and daily-driveable for people who don't develop it, it probably isn't. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener noreferrer" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a>

Jupiter Rowland@<a href="https://digitalcourage.social/@chbmeyer" rel="nofollow noopener noreferrer" target="_blank">Ch M[ae][iy]e?r 🖤🤍</a> <blockquote>Die Misskey-Familie ist am leistungsfähigsten, aber stark fragmentiert. Firefish und Calkey sind "tot"?</blockquote> Firefish ist Calckey. Oder war es. Ich versuche mal, die Geschichte nachzuzeichnen: Calckey entstand, indem Kainoa Kanter einen Soft-Fork von Misskey angelegt hat. Damals war es noch üblich, daß jeder Forkey einen Namen mit "-key" am Ende hat (FoundKey, Meisskey, Tanukey etc.). Das war im Grunde immer ein Soloprojekt. Es gab noch ein paar Extra-Entwickler. Aber: Nur Kainoa durfte in den Release-Code einpflegen und neue Versionen rausbringen, außerdem gehörten Kainoa die Domain der Website, die Domain des Code-Repository und die Domain der Leuchtturminstanz, die auch nur Kainoa administrierte. Anfang 2023, eigentlich war Akkoma gerade der heiße Scheiß, schob ein einzelner Calckey-Fan mit massiver Werbung einen Calckey-Hype an. Weil sich die Leute reihenweise auf Calckey stürzten, kam der Gedanke auf, für ein so populäres Projekt ist "Calckey" eigentlich ein doofer Name. Also wurde Calckey in Firefish umbenannt. Im Oktober 2023 ist Kainoa dann ziemlich komplett von der Bildfläche verschwunden, jedenfalls komplett aus dem Fediverse. Monatelang überhaupt gar nichts. Zu dem Zeitpunkt war Firefish noch einigermaßen synchron mit Misskey, das auf Version 12 war. Zwischenzeitlich ging Misskey auf Version 13, dann auf Version 14. Aber Firefish zog nicht nach, weil Kainoa nicht da war. Die anderen Devs konnten Patches einreichen, aber nur Kainoa durfte die in den Produktivcode einpflegen. Anfang 2024 war Firefish allmählich kritisch veraltet. Nicht nur das, sondern die Leuchtturminstanz, die mit Abstand größte Instanz kackte komplett ab und funktionierte überhaupt nicht mehr. Außer Kainoa konnte sich da aber niemand drum kümmern. An diesem Punkt wurde Firefish für tot erklärt. Leute sprangen reihenweise ab. Ganze Instanzen migrierten von Firefish zu Sharkey, einem anderen, jüngeren Misskey-Soft-Fork, der vor allem aktueller und aktiv gepflegt war. Ganze Firefish-Instanzen wurden auf Sharkey umgestellt. Meines Wissens waren es die anderen Firefish-Entwickler, die das sinkende Schiff verließen. Sie forkten Firefish zu Iceshrimp, um zumindest ein paar Firefish-Features behalten zu können. Es war ein Hard Fork, weil sie eh nicht damit rechneten, daß mit Firefish noch irgendwas passiert. Und sie haben Iceshrimp praktisch unmittelbar nach den Fork nach Misskey rebaset, um den "Unterbau" vom asbach-uralten Misskey 12 auf Misskey 14 hochziehen zu können. Im Frühjahr ist Kainoa wieder aufgetaucht. Der Grund für die Auszeit war ein Abschluß und ein Jobeinstieg. Und jetzt sollte es mit Firefish weitergehen. Nur war vom alten Firefish nicht mehr viel übrig. Und wohl erst jetzt erfuhr Kainoa, daß alle anderen Entwickler abgesprungen waren und nicht gedachten zurückzukehren. Letztlich gab Kainoa den Quellcode an eine neue Entwicklerin ab, Naskya. Aber nur den Code. Die drei Domains mitsamt dranhängenden Websites zu übertragen, war wohl zuviel Aufwand. Kainoa hat alle drei abgeschaltet, weshalb die meisten Leute glauben, Firefish sei tot, weil die ganzen alten Weblinks nicht mehr funktionieren. Naskya hat vorher den Quellcode auf ein neues Repository gesichert. Das aktuelle Firefish ist also rein technisch gesprochen ein Fork des alten Firefish unter demselben Namen. Außerdem hat Naskya eine neue Leuchtturminstanz gestartet auf einer Unterdomain des Repository. Letzten Monat hat sie dann bekanntgegeben, daß es viel zuviel Aufwand ist, Firefish ganz alleine zu pflegen, und Hilfe hat sie ja keine. So kann sie das unmöglich weiterführen. Also hat sie die Weiterentwicklung von Firefish gestoppt. Es wird jetzt nur noch gewartet und auch das nur bis Jahresende, dann ist mit Entwicklung Schluß. Und im Februar 2025 werden Code-Repository und Leuchtturminstanz abgeschaltet. <blockquote>Gibt es da irgendwelche Tendenzen, das zu Einen?</blockquote> Absolut nicht. Im allgemeinen sind Forkeys, die direkt von Misskey geforkt wurden, entstanden, um mehr Features an Misskey dranzukleben. So auch Calckey. Die Idee hinter Sharkey war wohl quasi, den ultimativen Forkey zu bauen. Sharkey ist ein Misskey-Soft-Fork, wo teilweise Sachen aus Calckey/Firefish drangebaut wurden und zusätzlich noch Eigengezüchtetes. Iceshrimp startete als der Versuch, einen stabilen Ersatz für Firefish zu haben. Es wurde von Firefish hartgeforkt, dann zwecks Aktualisierung der Basis auf das viel aktuellere Misskey rebaset. Dann hat man gemerkt, daß viele Probleme von Misskey selbst geerbt worden waren und es zu aufwendig wäre, die zu flicken. Ich meine, sonst hätte Firefish selbst das gemacht, sonst hätte Sharkey das gemacht oder wer auch immer. Also haben die Entwickler Iceshrimp auf Wartung gesetzt, die Weiterentwicklung komplett gestoppt und sich drangesetzt, das ganze Iceshrimp von Grund auf neu zu schreiben. Und zwar nicht mehr in TypeScript und Node.js, weil JavaScript für Serveranwendungen Käse ist, sondern in C#. Zwischenzeitlich ist von Iceshrimp Catodon geforkt worden. Das hat wieder einen anderen Fokus, und zwar will es ein Forkey für Mastodon-Umsteiger sein. Mit einem ähnlichen Featuresatz wie Mastodon, also mit viel Firefish- und sogar Misskey-Klimbim rausgeschmissen und mit Mastodons Standard-Weboberfläche. Catodons Entwicklung ist meines Wissens auch gestoppt, ich glaube, die warten darauf, daß Iceshrimp.NET fertig wird, damit sie Catodon darauf rebasen können. Dann gibt's noch CherryPick, einen japanischen Sharkey-Fork. Der hat sich zum Ziel gesetzt, die Macken, die das völlig überzüchtete Sharkey hat, auszubügeln. Das ist wohl zu großen Teilen auch schon gelungen. Schätze, die CherryPick-Entwickler haben es auch geschafft, Sharkeys legendär grottenschlechte Mastodon-API-Implementation durch die neue zu ersetzen, auf die die Sharkey-Entwickler schon ewig warten. <blockquote>Markdown (Fett, Links, unterstrichen), keine Zeichenbegrenzung und flexiblere Umfragen. Sonst noch was wichtiges?</blockquote> Markdown geht bei Misskey und den Forkeys noch weiter. Zeichenbegrenzung haben sie alle, nur nicht auf 500 Zeichen. Je nach Projekt hast du 3000 hartgecodete Zeichen (Misskey) oder ein paar tausend, aber durch den Admin einstellbar. (Fast) ganz ohne Zeichenbegrenzung sind nur die Sachen von Mike Macgirvin, also Friendica, Hubzilla, (streams) und das wohl noch experimentelle noch gar nicht richtig gestartete Forte. Die letzteren beiden haben nur eine durch die Serverdatenbank bedingte Zeichenbegrenzung von über 24.000.000 Zeichen. CC: @<a href="https://moppels.bar/@crossgolf_rebel" rel="nofollow noopener noreferrer" target="_blank">crossgolf_rebel - kostenlose Kwalitätsposts</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LangerPost" rel="nofollow noopener noreferrer" target="_blank">LangerPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLangerPost" rel="nofollow noopener noreferrer" target="_blank">CWLangerPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Misskey" rel="nofollow noopener noreferrer" target="_blank">Misskey</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forkey" rel="nofollow noopener noreferrer" target="_blank">Forkey</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forkeys" rel="nofollow noopener noreferrer" target="_blank">Forkeys</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Calckey" rel="nofollow noopener noreferrer" target="_blank">Calckey</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Firefish" rel="nofollow noopener noreferrer" target="_blank">Firefish</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Sharkey" rel="nofollow noopener noreferrer" target="_blank">Sharkey</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Iceshrimp" rel="nofollow noopener noreferrer" target="_blank">Iceshrimp</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Iceshrimp.NET" rel="nofollow noopener noreferrer" target="_blank">Iceshrimp.NET</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Catodon" rel="nofollow noopener noreferrer" target="_blank">Catodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CherryPick" rel="nofollow noopener noreferrer" target="_blank">CherryPick</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Friendica" rel="nofollow noopener noreferrer" target="_blank">Friendica</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a>

Recent searches

Search options

Administered by:

Server stats:

#forte