ohai.social

Jupiter Rowland@<a href="https://stefanbohacek.online/@stefan" rel="nofollow noopener" target="_blank">Stefan Bohacek</a> <blockquote>Also worth mentioning that quote boosts, which have also recently received funding, will include work on privacy and safety features around them, possibly extending to other areas of the online experience.</blockquote> These "privacy and safety features" are non-sense. They're proprietary, they're non-standard, they're Mastodon-specific. And they are expected to work only by respecting a proprietary, non-standard, Mastodon-specific quote-post permission flag which probably won't even be documented anywhere except Mastodon's server code. The opt-out feature will only work within a 100% Mastodon bubble and even that only if no non-Mastodon user finds content from within this bubble by searching mastodon.social for hashtags. Mastodon is selling its whole quote-post feature as a total revolution, as the very introduction of quote-posts to the Fediverse. And it will work. I've once run <a href="https://hub.netzgemeinde.eu/item/4c8c73a8-84cb-4df3-adb1-59791deda635" rel="nofollow noopener" target="_blank">a poll on whether the Fediverse has quote-posts</a>. 71% of all voters thought the Fediverse does not have quote-posts right now. And that was in my bubble which, in comparison to Mastodon in general, is fairly Fediverse-savvy and full of non-Mastodon users. But as a matter of fact, the Fediverse does have quote-posts right now! Almost everything that can do microblogging in a way has quote-posts. Pleroma has quote-posts. Akkoma has quote-posts. Misskey has quote-posts. Firefish has quote-posts. Iceshrimp has quote-posts. Iceshrimp.NET has quote-posts. Sharkey has quote-posts. Catodon has quote-posts. Friendica has quote-posts. Hubzilla has quote-posts. (streams) has quote-posts. And so forth. They haven't introduced quote-posts to spite Mastodon. Some of them have had quote-posts since before Mastodon even existed. Friendica, for example, was created with quote-posts available, and that was five and a half years before Mastodon was created. For as long as Mastodon has existed, Friendica could quote-post Mastodon toots. And so could Hubzilla, created ten months before Mastodon. In fact, all of the above can quote-post any Mastodon toot right now, with no problems, with zero resistance. Guess what'll change when Mastodon introduces quote-posts plus the opt-in switch. Well, Mastodon will be able to quote-post. Mastodon might be able to display quote-posts from outside properly, but probably not because it's ignoring that the rest of the Fediverse can quote-post. But the rest of the Fediverse will still be able to quote-post just about all Mastodon toots. With no problems. With zero resistance. Even with the opt-in switched to off. Because that switch is proprietary, non-standard and Mastodon-specific. Because only Mastodon even supports it. This switch will cause many many more Mastodon users to learn the hard way that the Fediverse is more than Mastodon. Namely by encountering a post or comment from something that does not behave like Mastodon. And many many more Mastodon users will shit bricks in sheer terror upon this revelation. If Mastodon really wanted this switch to be 100% waterproof, it would have to implement the feature request in its entirety. That includes defederation from all Fediverse instances that don't respect the opt-in switch. Mind you, the defederation clause and the entire feature request came from someone in the firm belief that the Fediverse is Mastodon, only Mastodon and nothing but Mastodon. Just like about every other Mastodon user out there. So it was only targetted at rogue Mastodon instances with hacked source code. In reality, however, it would require entire non-Mastodon Fediverse projects to be Fediblocked because they can quote-post without respecting Mastodon's quote-post opt-in switch. All instances of Pleroma, of Akkoma, of Misskey, of Firefish, of Iceshrimp including Iceshrimp.NET, of Sharkey, of Catodon, of Friendica, of Hubzilla, of (streams) and so forth would have to be Fediblocked because they can quote-post without respecting Mastodon's quote-post opt-in switch. Every last one of them. Mastodon's quote-post feature will either cause a rift through the Fediverse if this rule is put into action or even more people to shit bricks in terror and escape to Bluesky if it isn't. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fedisplaining" rel="nofollow noopener" target="_blank">Fedisplaining</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFedisplaining" rel="nofollow noopener" target="_blank">CWFedisplaining</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuotePost" rel="nofollow noopener" target="_blank">QuotePost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuotePosts" rel="nofollow noopener" target="_blank">QuotePosts</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteTweet" rel="nofollow noopener" target="_blank">QuoteTweet</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteTweets" rel="nofollow noopener" target="_blank">QuoteTweets</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteToot" rel="nofollow noopener" target="_blank">QuoteToot</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteToots" rel="nofollow noopener" target="_blank">QuoteToots</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteBoost" rel="nofollow noopener" target="_blank">QuoteBoost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteBoosts" rel="nofollow noopener" target="_blank">QuoteBoosts</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuotedShares" rel="nofollow noopener" target="_blank">QuotedShares</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuotePostDebate" rel="nofollow noopener" target="_blank">QuotePostDebate</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteTootDebate" rel="nofollow noopener" target="_blank">QuoteTootDebate</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Pleroma" rel="nofollow noopener" target="_blank">Pleroma</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Akkoma" rel="nofollow noopener" target="_blank">Akkoma</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Misskey" rel="nofollow noopener" target="_blank">Misskey</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forkey" rel="nofollow noopener" target="_blank">Forkey</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forkeys" rel="nofollow noopener" target="_blank">Forkeys</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Firefish" rel="nofollow noopener" target="_blank">Firefish</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Iceshrimp" rel="nofollow noopener" target="_blank">Iceshrimp</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Iceshrimp.NET" rel="nofollow noopener" target="_blank">Iceshrimp.NET</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Sharkey" rel="nofollow noopener" target="_blank">Sharkey</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Catodon" rel="nofollow noopener" target="_blank">Catodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Friendica" rel="nofollow noopener" target="_blank">Friendica</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=NotOnlyMastodon" rel="nofollow noopener" target="_blank">NotOnlyMastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseIsNotMastodon" rel="nofollow noopener" target="_blank">FediverseIsNotMastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MastodonIsNotTheFediverse" rel="nofollow noopener" target="_blank">MastodonIsNotTheFediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediblockMeta" rel="nofollow noopener" target="_blank">FediblockMeta</a>

Jupiter Rowland@<a href="https://social.tchncs.de/@jesuisatire" rel="nofollow noopener" target="_blank">jesuiSatire  …ᘛ⁐̤ᕐᐷ</a> Sorry, but I have to pick this apart, sitting on what might be the opposite end of the Fediverse. <blockquote>How to destroy the essential tools of our decentralized setup and there for the #<a class="" href="https://hub.netzgemeinde.eu/search?tag=fediVerse" rel="nofollow noopener" target="_blank">fediVerse</a>:</blockquote> ...where "Fediverse" is synonymous for "Mastodon", I guess. <blockquote>* don't boost</blockquote> I can't boost. Hubzilla doesn't have that feature. Hubzilla "quote-tweets" instead. It has done so since before there was Mastodon. You don't want me to do that instead, do you? <blockquote>* don't use #<a class="" href="https://hub.netzgemeinde.eu/search?tag=hashTags" rel="nofollow noopener" target="_blank">hashTags</a></blockquote> Okay, I can do that. But from your typical Mastodon and formerly Twitter user's point of view, I guess I use way too many because I also use them to trigger filters. So I use a whole lot of them. <blockquote>* don't follow #<a class="" href="https://hub.netzgemeinde.eu/search?tag=hashTags" rel="nofollow noopener" target="_blank">hashTags</a></blockquote> Hubzilla can't follow hashtags either. <blockquote>* don't follow groups @a.gup.pe * don't post to groups @a.gup.pe</blockquote> First of all, there isn't a single Guppe group that even remotely covers the primary topic of this channel. There is a Lemmy community for that topic, though, and I'm connected to it. Besides, I'm connected to various Friendica, Hubzilla and (streams) forums/groups which blow gup.pe clean out of the water feature-wise. <blockquote>* don't read, understand or follow #<a class="" href="https://hub.netzgemeinde.eu/search?tag=fediTips" rel="nofollow noopener" target="_blank">fediTips</a></blockquote> Right, I don't read them. Because they're all so Mastodon-centric it hurts. Almost none of them can be sensibly carried over to here. Not to mention the edge-cases I have to deal with that FediTips don't cover, for example when it comes to describing images. I don't have to put everything into the alt-text. I don't have a 500-character limit that prevents me from describing stuff in the post text body and forces me to use only the alt-text. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fedisplaining" rel="nofollow noopener" target="_blank">Fedisplaining</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFedisplaining" rel="nofollow noopener" target="_blank">CWFedisplaining</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=NotOnlyMastodon" rel="nofollow noopener" target="_blank">NotOnlyMastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MastodonIsNotTheFediverse" rel="nofollow noopener" target="_blank">MastodonIsNotTheFediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseIsNotMastodon" rel="nofollow noopener" target="_blank">FediverseIsNotMastodon</a>

Jupiter Rowland@<a href="https://lgbtqia.space/@alice" rel="nofollow noopener" target="_blank">🅰🅻🅸🅲🅴</a> Okay, here's a bit more. And I'm trying to write this from a Mastodon point of view, but as someone who has got experience outside of Mastodon. If you're on Mastodon which you probably are, get used to the lingo. <ul><li>(Twitter) tweet = (Mastodon) toot or post </li><li>(Twitter) retweet = (Mastodon) boost </li><li>(Twitter) like = (Mastodon) fave</li></ul> This may come as a surprise, but the Fediverse is not only Mastodon. There are many other projects in the Fediverse which are connected to Mastodon. Some of them have actually already been around before Mastodon. And they have features that Mastodon doesn't have. So don't freak out if you see a post with over 500 characters. Or with italics. Or with bold type. Or with a <code>code block</code>. Or using the content warning for a summary. Or with a quote. Or with a "quote-tweet". Outside of Mastodon, all this is standard and perfectly normal. Get used to it. <blockquote>⚠️ Use content warnings (CW) to make browsing the #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener" target="_blank">Fediverse</a> safer for all.</blockquote> Double your content warnings with hashtags. Some projects in the Fediverse outside of Mastodon use text filters to automatically generate individual content warnings for those who need them. And Mastodon can do that, too, so even some Mastodon users do it. If a post with content that you may deem sensitive has only got these hashtags but no actual content warning, this is not necessarily due to ill intent or neglect. Some Fediverse projects outside of Mastodon can't do content warnings the Mastodon way. Hubzilla can only do them in first posts, but not in replies. On Friendica, they're generally very difficult to do. So don't immediately call for moderation. <blockquote>🖼️ Use #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener" target="_blank">AltText</a> on *all* your pictures! Visually impaired people like memes too.</blockquote> Actually describe your images in alt-text. And do only that. No hashtags in alt-text. No links in alt-text. No SEO keyword spamming in alt-text. If there's text in your picture, transcribe it in alt-text word by word. <blockquote>⛔ You can mute, block, and/or report people, depending on the severity of their actions. That said, most people here are pretty cool, so give 'em a chance unless they're being a willful ass-hat.</blockquote> Don't forget: Different instances have different rules. So don't report someone on another instance for not adding a content warning that's mandatory on your instance but not on theirs or the like. And don't forget either: Different projects have different capabilities and different cultures of using them. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fedisplaining" rel="nofollow noopener" target="_blank">Fedisplaining</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFedisplaining" rel="nofollow noopener" target="_blank">CWFedisplaining</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MastodonIsNotTheFediverse" rel="nofollow noopener" target="_blank">MastodonIsNotTheFediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=NotOnlyMastodon" rel="nofollow noopener" target="_blank">NotOnlyMastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseIsNotMastodon" rel="nofollow noopener" target="_blank">FediverseIsNotMastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hashtag" rel="nofollow noopener" target="_blank">Hashtag</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hashtags" rel="nofollow noopener" target="_blank">Hashtags</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener" target="_blank">AltText</a>

Jupiter Rowlandtl;dr: Must add lots of hashtags because some people use them for CW text filters, some people only do that for CW, others may want to find my stuff, and yet others want to hide my stuff with filters. @<a href="https://mstdn.social/@DemocracySpot" rel="nofollow noopener" target="_blank">The Eddie Show   📷 🎧 ❤️</a> @<a href="https://mastodonapp.uk/@the_roamer" rel="nofollow noopener" target="_blank">the roamer</a> Guilty as charged. I regularly use a lot of hashtags. But I always put them all at the end of the post unless I'm talking about certain hashtags. I actually have to. I know that not everyone in the Fediverse is using Mastodon 4.x like it's still Mastodon 3.x or older. Some Fediverse users use text filters to automatically generate content warnings. Some prefer it. Here on <a href="https://joinfediverse.wiki/What_is_Hubzilla%3F" rel="nofollow noopener" target="_blank">Hubzilla</a>, what Mastodon perceives as a content warning field is actually a summary field. Content warnings are optionally automatically generated by a text filter. All this has been part of Hubzilla and its culture since its first release in 2015, a year before Mastodon was launched. In fact, Mastodon's content warning field has actually been StatusNet's summary field since 2008. When I write a post, I always give out content warnings two-fold: in the summary field so that those used to Mastodon 3.x and older have their content warnings and as hashtags so that those who use text filters have their content warnings automatically generated. When I write a comment right now, I can't write a Mastodon-style content warning. Hubzilla doesn't have Mastodon's Twitter-like many-posts thread model. Hubzilla has a one-post-many-comments model like Facebook, Tumblr or blogs. And why would you want to put a summary on a blog comment?! That's why Hubzilla doesn't have a "content warning field" for comments. That's why I can't write Mastodon-style content warnings for replies. Hashtags are my only way of flagging sensitive content in replies. I take content warnings seriously. And I post a whole lot of potentially sensitive or triggering content. This starts with long posts. Many Mastodon users don't want to see posts with more than 500 characters. Hubzilla doesn't have a character limit at all, and it's extremely hard for me to stay under 500 characters. At least some Mastodon users demand all posts with over 500 characters have a content warning. So whenever I exceed 500 characters, I add "(CW:) long (n characters)" to the Mastodon-style content warning and the four hashtags #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener" target="_blank">Long</a>, #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener" target="_blank">LongPost</a>, #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener" target="_blank">CWLong</a> and #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener" target="_blank">CWLongPost</a> to the end of the post because I can't know who uses what for their filters. Then there are those who don't want to read about the Fediverse on Mastodon. It's too technical for them or I don't know what. So whenever I write about the Fediverse, I add "(CW:) Fediverse meta" and often also "non-Mastodon Fediverse meta" to warn those who don't want to read about the Fediverse not only being Mastodon. In addition, I add the hashtags #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener" target="_blank">FediMeta</a>, #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener" target="_blank">FediverseMeta</a>, #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener" target="_blank">CWFediMeta</a> and #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener" target="_blank">CWFediverseMeta</a> for those who use filters. If I explain something Fediverse-related without having been asked to do so, not even indirectly, I add "(CW:) Fedisplaining" and the hashtags #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fedisplaining" rel="nofollow noopener" target="_blank">Fedisplaining</a> and #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFedisplaining" rel="nofollow noopener" target="_blank">CWFedisplaining</a>. If I write about content warnings, I add "(CW:) content warning meta" and the hashtag #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWMeta" rel="nofollow noopener" target="_blank">CWMeta</a>. If I could write a summary/Mastodon-style content warning for this, I'd write, "I need hashtags not only to cover the topics I write about, but also to trigger text filters which some people use for automated content warnings; CW: long (almost 6,400 characters), Fediverse meta, non-Mastodon Fediverse meta, Fedisplaining, content warning meta, hashtag meta, doing things differently from the standard Mastodon way in the Fediverse". Similarly, all my other content warnings are always present as hashtags and in (start) posts as Mastodon-style content warnings as well. Also, of course, I have to indicate what I write about so that my posts can be found by those who might be interested in the topic and filtered by those who aren't. And this regularly requires multiple hashtags. The primary topic of this Hubzilla channel is 3-D virtual worlds, especially those based on OpenSimulator. In order to make such posts discoverable, I add the hashtag #<a class="" href="https://hub.netzgemeinde.eu/search?tag=OpenSimulator" rel="nofollow noopener" target="_blank">OpenSimulator</a>. But there's also the short-hand OpenSim which is used even more often, so I also have to add the hashtag #<a class="" href="https://hub.netzgemeinde.eu/search?tag=OpenSim" rel="nofollow noopener" target="_blank">OpenSim</a>. If my post is partly or entirely about Second Life, I add #<a class="" href="https://hub.netzgemeinde.eu/search?tag=SecondLife" rel="nofollow noopener" target="_blank">SecondLife</a>. In addition, I need more general hashtags. One is #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Metaverse" rel="nofollow noopener" target="_blank">Metaverse</a>. No, this term wasn't invented by Zuckerberg in 2022. The OpenSim community has used it a lot before 2010, maybe as early as 2008 or even 2007. And it was the name of a Second Life conference in 2007. The other one is #<a class="" href="https://hub.netzgemeinde.eu/search?tag=VirtualWorlds" rel="nofollow noopener" target="_blank">VirtualWorlds</a>. If I write about a special topic within this topic, e.g. if I mention a certain grid or an event, I add that as a hashtag. Larger events in OpenSim usually have their official hashtags for commercial social media, and I use them here. And so forth. The secondary topic of this channel has become the Fediverse itself. As I've written above, this alone requires four hashtags by default even without going over 500 characters. If it's somewhat about the Fediverse as a whole or in general, I add #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener" target="_blank">Fediverse</a>. If it touches one or multiple certain projects, I tag them all. And I know a lot of Fediverse projects. If a post explains that the Fediverse extends beyond Mastodon to an actual or imaginary audience that thinks otherwise, my go-to hashtags, all of which have existed before, are #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MastodonIsNotTheFediverse" rel="nofollow noopener" target="_blank">MastodonIsNotTheFediverse</a>, #<a class="" href="https://hub.netzgemeinde.eu/search?tag=NotOnlyMastodon" rel="nofollow noopener" target="_blank">NotOnlyMastodon</a> and most recently #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseIsNotMastodon" rel="nofollow noopener" target="_blank">FediverseIsNotMastodon</a>. Certain details such as protocols, OpenWebAuth or nomadic identity require their own hashtags. I can never know who might be searching for what, especially if I'm about to provide exactly what they're looking for. And I can also never know who's tired of reading what, and who has set up a hashtag filter to get rid of that kind of content. As far as alt-text is concerned: I never skip the image description when I post an image, not even when I link to one. And I write the longest and most detailed image descriptions in the whole Fediverse. There are only two exceptions. One are my profile picture (Mastodon: "avatar") and my channel picture (Mastodon: "banner"). There are no adequate means for me to describe them in such a way that the descriptions can easily be associated with the images. And I'd need a whole lot of character space for that. The other one are link preview images automatically generated by Mastodon because I can never know beforehand which image Mastodon will place there, if any.

Jupiter Rowlandtl;dr: Hubzilla has had at least some of this for over a decade now. And it won't replace any of it with a new standard tailor-made for Mastodon. @<a href="https://mitra.social/users/silverpill" rel="nofollow noopener" target="_blank">silverpill</a> If you look past projects based on ActivityPub and at projects that have ActivityPub as an additional protocol, some of this already exists. <blockquote>- Data portability. In my opinion, this is the most important problem. I'm in favor of <a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md" rel="nofollow noopener" target="_blank">FEP-ef61</a>, which also solves identity portability and unlocks many new features.</blockquote> Exists in the shape of nomadic identity. Invented by @<a class="" href="https://fediversity.site/channel/mikedev" rel="nofollow noopener" target="_blank">Mike Macgirvin 🖥️</a> in 2011 with his Zot protocol and first deplayed in 2012 with the Red Matrix, nowadays known as <a href="https://joinfediverse.wiki/What_is_Hubzilla%3F" rel="nofollow noopener" target="_blank">Hubzilla</a>. Also available on <a href="https://codeberg.org/streams/streams" rel="nofollow noopener" target="_blank">(streams)</a>, Mike's current project at the end of a string of forks from Hubzilla, now based on the Nomad protocol. Mike would like to see nomadic identity and other special features of the Zot and Nomad protocols included in the ActivityPub protocol. He has actually submitted a number of proposals for this. They were all rejected. Even though he is a protocol developer first and foremost, and he has both created and worked on more Fediverse protocols than anyone else, so he should be considered competent. Nomadic identity with ActivityPub won't come unless either Evan Prodromou and the W3C commission cave in and allow Mike's suggestions, or someone re-invents the wheel from scratch in a way that's utterly incompatible to Hubzilla and (streams). And it won't come to Mastodon unless Eugen Rochko can imply that Mastodon has had it first. And there will never be a nomadic identity standard that meets Mike's requirements as well as Eugen's wishes. <blockquote>- End-to-end encryption. <a href="https://en.wikipedia.org/wiki/Messaging_Layer_Security" rel="nofollow noopener" target="_blank">MLS</a> has become a standard, and it would be wise to adopt it. <a href="https://codeberg.org/fediverse/fediverse-ideas/issues/3" rel="nofollow noopener" target="_blank">Issue 3 at fediverse-ideas</a> provides a good overview of what we have at the moment (not much). Some variation of <a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/ae97/fep-ae97.md" rel="nofollow noopener" target="_blank">FEP-ae97</a> is likely needed to make end-to-end encryption work.</blockquote> AFAIK, all three of Mike's still existing projects, <a href="https://joinfediverse.wiki/What_is_Friendica%3F" rel="nofollow noopener" target="_blank">Friendica</a> from 2010, Hubzilla from 2012/2015 and (streams) from 2021, have it. Optionally, but still. I think Friendica actually advertises military-grade encryption. <blockquote>- Plugins. Something like <a href="https://docs.pleroma.social/backend/configuration/mrf/" rel="nofollow noopener" target="_blank">Pleroma MRF</a>, but cross-platform (e.g. Wasm-based). Also, pluggable timeline algorithms.</blockquote> Friendica, Hubzilla and (streams) have had support for add-ons, including third-party add-ons, plus a number of official add-ons since their respective inceptions. If you want a cross-platform add-on standard, I hope you don't expect these three to throw their own standards over board in favour of the new standard. Otherwise, good luck developing a replacement for Pubcrawl that makes Zot-based Hubzilla compatible with ActivityPub while working on ActivityPub-based Mastodon just the same. Friendica, Hubzilla and (streams) rely on add-ons for all federation beyond their respective base protocols (DFRN, Zot, Nomad). <blockquote>- Groups. We have several competing standards for groups: <a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/1b12/fep-1b12.md" rel="nofollow noopener" target="_blank">FEP-1b12</a>, <a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/400e/fep-400e.md" rel="nofollow noopener" target="_blank">FEP-400e</a>, Mastodon developers are working on their own standard. It would be nice to converge on a single standard, that also supports private groups.</blockquote> Friendica, Hubzilla and (streams) have had support for discussion groups/forums since their respective inception. On Friendica, a group is a user account with special settings; on Hubzilla and (streams), it's a <a href="https://joinfediverse.wiki/What_are_channels_on_Hubzilla_and_(streams)%3F" rel="nofollow noopener" target="_blank">channel</a> with special settings. In addition, especially Hubzilla and (streams) have access permission control on a level that most people for whom the Fediverse is only ActivityPub couldn't imagine in their wildest dreams. All three can be used by users from all over the Fediverse already now. Good luck forcing Friendica to give up its 13-year-old standard that's used by <a href="https://venera.social/profile/fediversenews" rel="nofollow noopener" target="_blank">Fediverse News</a>, just to name one, and Hubzilla to give up its 11-year-old standard that blows everything else but what (streams) does out of the water. Good luck forcing them to adopt something inferior. On the other hand, good luck forcing <a href="https://joinfediverse.wiki/What_is_Lemmy%3F" rel="nofollow noopener" target="_blank">Lemmy</a> and <a href="https://joinfediverse.wiki/What_is_Kbin%3F" rel="nofollow noopener" target="_blank">/kbin</a> to switch to a wholly different standard. Don't forget that these two exist as well. And good luck having the Fediverse outside of Hubzilla and (streams) adopt both server-side and client-side OpenWebAuth. And I'm not even talking about how different Fediverse projects handle threads differently. Mastodon has a Twitter-like thread structure: many posts, tied together with mentiones. Just about everything that's built on ActivityPub has taken this over. Friendica, Hubzilla and (streams) have a Facebook/blog/Tumblr-like thread structure: one post, the start post, and many comments which aren't posts. It's similar on Lemmy and /kbin which are Reddit clones, only that they don't allow thread starters to moderate their own threads. <blockquote>- Quoting. <a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/e232/fep-e232.md" rel="nofollow noopener" target="_blank">FEP-e232</a> is a proposed standard, but most fediverse applications still use non-standard properties. Mastodon developers are trying to invent something completely different.</blockquote> This is something that almost the whole Fediverse has implemented, save for Mastodon. And again, Friendica has had quotes since its inception in 2010, almost six years before Mastodon was launched (which, by the way, federated with Friendica and Hubzilla on the spot). Hubzilla has had quotes since 2012, inherited from Friendica. Their way of quoting is dead-simple: BBcode. <code>[quote][/quote]</code> (streams) supports Markdown and HTML in addition to BBcode, but otherwise it's the same. Oh, and by the way: Friendica, Hubzilla and (streams) have also supported quote-posts a.k.a. quote-tweets a.k.a. quote-toots a.k.a. quote-boosts from their very beginnings. <blockquote>- Markets. So far there's only <a href="https://codeberg.org/silverpill/mitra" rel="nofollow noopener" target="_blank">one</a> server implementation capable of processing payments.</blockquote> At least two. Hubzilla has a payment add-on, too. It isn't installed on all hubs, but it's there. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFedisplaining" rel="nofollow noopener" target="_blank">CWFedisplaining</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mastodon" rel="nofollow noopener" target="_blank">Mastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=MastodonIsNotTheFediverse" rel="nofollow noopener" target="_blank">MastodonIsNotTheFediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=NotOnlyMastodon" rel="nofollow noopener" target="_blank">NotOnlyMastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ActivityPub" rel="nofollow noopener" target="_blank">ActivityPub</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Friendica" rel="nofollow noopener" target="_blank">Friendica</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=DFRN" rel="nofollow noopener" target="_blank">DFRN</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Zot" rel="nofollow noopener" target="_blank">Zot</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Nomad" rel="nofollow noopener" target="_blank">Nomad</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Lemmy" rel="nofollow noopener" target="_blank">Lemmy</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=kbin" rel="nofollow noopener" target="_blank">kbin</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%2Fkbin" rel="nofollow noopener" target="_blank">/kbin</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=NomadicIdentity" rel="nofollow noopener" target="_blank">NomadicIdentity</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=OpenWebAuth" rel="nofollow noopener" target="_blank">OpenWebAuth</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Group" rel="nofollow noopener" target="_blank">Group</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Groups" rel="nofollow noopener" target="_blank">Groups</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forum" rel="nofollow noopener" target="_blank">Forum</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forums" rel="nofollow noopener" target="_blank">Forums</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Quote" rel="nofollow noopener" target="_blank">Quote</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Quotes" rel="nofollow noopener" target="_blank">Quotes</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Encryption" rel="nofollow noopener" target="_blank">Encryption</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=E2EE" rel="nofollow noopener" target="_blank">E2EE</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=E2EEncryption" rel="nofollow noopener" target="_blank">E2EEncryption</a>

Jupiter RowlandDraft preamble for posts that go out to Mastodon; CW: long (over 2,850 characters), fedisplaining, Fediverse meta, Mastodon vs non-Mastodon meta, mentioning features that Mastodon doesn't have and not refusing to use them

Recent searches

Search options

Administered by:

Server stats:

#CWFedisplaining