toad.social

0 posts0 participants0 posts today

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://pirati.ca/profile/heluecht" rel="nofollow noopener noreferrer" target="_blank">Michael Vogel</a> <blockquote>Was anderes aus Interesse: Wieso schickst Du bei allen Posts die gleichen Hashtags mit? Ist das eine Eigenschaft von Hubzilla oder fügst Du die Hashtags immer per Hand hinzu? (und wenn ja, wieso?)</blockquote> Die schreibe ich per Hand rein. Teilweise sind die zum leichteren Auffinden auf Mastodon. Hauptsächlich sind sie aber zum Triggern von Wortfiltern. Es gibt kaum etwas, worüber ich schreibe, was nicht irgendjemanden so stören würde, daß sie es nicht rausfiltern würden. Und Hubzilla schickt anscheinend auch meine öffentlichen Kommentare an alle meine Kontakte, also auch quer über Mastodon. Klar könnte ich jetzt sagen, die meisten Mastodon-Nutzer würden nicht mal Filter benutzen, wenn ich ihnen eine Schritt-für-Schritt-Anleitung mit konkreten Beispielen posten würde. Aber wer auf Mastodon jetzt tatsächlich was filtert, kann ich blöderweise nicht mal aus Zustellungsberichten rauslesen. Die ersten vier eben, #<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> und #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a>, baue ich immer ein, wenn ein Post oder Kommentar die 500 Zeichen überschreitet, um irgendwas zu haben, womit sich Mastodon-User meine "überlangen" Beiträge vom Hals schaffen können. Ist eben so: Ich habe sehr viel mehr Publikum auf Mastodon als auf Friendica, Hubzilla und (streams) zusammen. Andererseits sind es gerade Nutzer aus unserer Ecke des Fediverse, die ich dabei erwischt habe, das Hauptthema meines Kanals auszufiltern. #<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=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://infosec.exchange/@thenexusofprivacy" rel="nofollow noopener noreferrer" target="_blank">The Nexus of Privacy</a> I'm someone who usually follows all advice about good Fediverse behaviour to a tee. That is, as far as Hubzilla lets me, as long as it doesn't require me to abandon Hubzilla's own culture in favour of only Mastodon's culture, and as long as it doesn't require me to abandon a number of Hubzilla's key features because Mastodon doesn't have them. Some may say I'm overdoing the Mastodon-style content warning thing, at least in posts. Hubzilla doesn't support content warning in comments, and if I reply to something, it's always a comment and never a post. Otherwise you'd get one big honking Mastodon-style content warning here. You do get a huge pile of filter-triggering hashtags, though. Some may say I'm overdoing the image description thing. My image descriptions in alt-text are among the longest in the Fediverse, and these are my short descriptions. My long descriptions for the same images which go into the posts are the longest, most detailed, most explanatory image descriptions in the Fediverse, full stop. And I keep raising my own standards. I only have one image description which I don't consider outdated, obsolete and sub-standard yet. So I'd normally love to fulfill everything in your post to a tee by my definition of "a tee". And my definition of "to a tee" is everyone else's definition of "Are you completely insane, man?!" But this time, it's more difficult. Call me racist, but it's more difficult. (1/7) #<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=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CW" rel="nofollow noopener noreferrer" target="_blank">CW</a> #<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=CWMeta" rel="nofollow noopener noreferrer" target="_blank">CWMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarning" rel="nofollow noopener noreferrer" target="_blank">ContentWarning</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=ContentWarningMeta" rel="nofollow noopener noreferrer" target="_blank">ContentWarningMeta</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=Filters" rel="nofollow noopener noreferrer" target="_blank">Filters</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener noreferrer" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener noreferrer" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener noreferrer" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener noreferrer" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">CWImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Racist" rel="nofollow noopener noreferrer" target="_blank">Racist</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Racism" rel="nofollow noopener noreferrer" target="_blank">Racism</a>

Jupiter Rowlandtl;dr: Why you should block me now First things first, reasons why you should block me rather than following me: <ul><li>In general, I don't behave like I'm on Mastodon. That's because I'm not on Mastodon. I'm on something that's very much not Mastodon, and that's older than Mastodon.</li><li>I regularly post over 500 characters at once. And I usually refuse to cut long posts into threads. I don't have to. My character limit is practically infinite. Also, people who hate threads are closer to me than people who demand threads.</li><li>I use text formatting.</li><li>I do other things that are impossible on Mastodon such as embedded links.</li><li>I usually use a lot of hashtags. I do so to trigger other people's filters. Filter-generated CWs are the norm where I am.</li><li>I summarise my posts in your CW field. That's because your CW field has always been my summary field, and that's since long before it was your CW field.</li><li>I can't add Mastodon-style CWs to replies.</li><li>My mentions use long names rather than the short names used by Mastodon. This may be disturbing. But I can't switch it off. It's hard-coded.</li><li>I post a lot of Metaverse-related things. And I don't denounce "the Metaverse" as being dead or stillborn. I'm not a crypto shill, though; the kind of metaverse I write about has been in operation since many years before the concept of blockchains was invented.</li><li>My non-Metaverse posts are about the Fediverse. They don't make Mastodon look good. And they tend to be technical.</li><li>My image descriptions in alt-text are always fairly long. And they're my short image descriptions. My long image descriptions are in the post. And they're usually well over 10,000 characters long.</li></ul> What this is, and what this is about This is not someone's single, general, all-purpose, personal Mastodon account. This channel (not account) was created to specialise in the topics of virtual worlds in general and, more specifically, those based on OpenSimulator. You can consider me not much more than an OpenSim avatar. Since most of you have probably never heard of OpenSim, and you're wondering what I'm talking about: <a href="https://hub.netzgemeinde.eu/item/ba1b1cb6-7c18-410e-8752-df4b4face2e0" rel="nofollow noopener noreferrer" target="_blank">Here is an article I've written about it.</a> And <a href="http://opensimulator.org" rel="nofollow noopener noreferrer" target="_blank">this is the official website and wiki.</a> In a nutshell, OpenSimulator is a free, open-source and decentralised server-side re-implementation of #<a class="" href="https://hub.netzgemeinde.eu/search?tag=SecondLife" rel="nofollow noopener noreferrer" target="_blank">SecondLife</a>, created around Second Life's own viewer API after Linden Labs made the official Second Life viewer open-source. It was launched in January, 2007, and most OpenSim-based world, usually called grids, have been federated with one another since the introduction of the Hypergrid in 2008. One could say that it is to Second Life what Mastodon is to Twitter, what Pixelfed is to Instagram, and what Lemmy is to Reddit, only that the UI can be almost identical. I've been in OpenSim since April 30th, 2020. By the way, I'm not in Second Life, and I've never been there. I occasionally post about the Fediverse with which I mean the Fediverse beyond Mastodon. That's when I have to say something that nobody else says. <a href="https://hub.netzgemeinde.eu/channel/jupiter_rowland//?cat=Memes" rel="nofollow noopener noreferrer" target="_blank">Some of my older posts contain memes</a>. Sometimes it's easier to express something in one image macro than in 5,000 words. New meme posts shall go elsewhere in the Fediverse; see below. I don't post about real life. I may occasionally comment posts about real life, but I don't post about it. This channel is not about real life. Where I am in the Fediverse Those of you who come across my channel in their Web browsers in search of my profile (which is <a href="https://hub.netzgemeinde.eu/profile/jupiter_rowland" rel="nofollow noopener noreferrer" target="_blank">here</a>, by the way), will most likely see it right away. But those who see this post in their Mastodon timelines won't, although the text formatting should be a dead give-away. So it's only fair to mention it here: I'm not on Mastodon. Yes, I'm someplace that's connected to Mastodon, but I'm not on Mastodon proper. So some of you might learn it from this post: The Fediverse is not only Mastodon. Instead, I'm using a project named <a href="https://joinfediverse.wiki/What_is_Hubzilla%3F" rel="nofollow noopener noreferrer" target="_blank">Hubzilla[/b] (see also [url=https://hubzilla.org]the official website</a>). It has tons of features that Mastodon doesn't have, including some that are highly requested on Mastodon such as full-text search, quotes, quote-posts, text formatting <a href="https://hub.netzgemeinde.eu/item/92d30357-bf1d-4c69-ab89-7e1853481ce0" rel="nofollow noopener noreferrer" target="_blank">like you wouldn't believe</a>, magic single sign-on and nomadic identity. It practically doesn't have any character limits at all. Also, Hubzilla is older than Mastodon. It had its 1.0 release in December, 2015, more than half a year before Mastodon, and it was renamed from a project named the Red Matrix that was launched as early as 2012, about four years before Mastodon. For as long as Mastodon has existed, it has continuously been connected to Hubzilla. Oh, and by the way: Mastodon was the second Fediverse project to adopt ActivityPub in September, 2017. The first one, two months earlier, was Hubzilla. Other channels My little in-world sister Juno has her own Hubzilla channel. It's even more specialising in OpenSim from her point of view. @<a class="" href="https://hub.netzgemeinde.eu/channel/juno_rowland" rel="nofollow noopener noreferrer" target="_blank">Juno Rowland</a> <a href="https://hub.netzgemeinde.eu/profile/juno_rowland" rel="nofollow noopener noreferrer" target="_blank">@⁠juno_rowland@hub.netzgemeinde.eu</a> <a href="https://hub.netzgemeinde.eu/profile/juno_rowland" rel="nofollow noopener noreferrer" target="_blank">https://hub.netzgemeinde.eu/profile/juno_rowland</a> In addition, I have another channel on an instance of a nameless Fediverse server application that can be found in <a href="https://codeberg.org/streams/streams" rel="nofollow noopener noreferrer" target="_blank">the streams repository</a>, a descendant of Hubzilla by Hubzilla's creator. I have launched that channel to be able to post images that may be sensitive in some way, e.g. that show faces which means eye contact. Hubzilla can't make Mastodon blank them out; (streams) can. Again, this channel is in the Fediverse, and you can follow it from Mastodon and anywhere else in the Fediverse. @<a class="" href="https://streams.elsmussols.net/channel/jupiter_rowland" rel="nofollow noopener noreferrer" target="_blank">Jupiter Rowland's (streams) outlet</a> <a href="https://streams.elsmussols.net/channel/jupiter_rowland" rel="nofollow noopener noreferrer" target="_blank">@⁠jupiter_rowland@streams.elsmussols.net</a> <a href="https://streams.elsmussols.net/channel/jupiter_rowland" rel="nofollow noopener noreferrer" target="_blank">https://streams.elsmussols.net/channel/jupiter_rowland</a> On the same instance, I have a channel that specialises in posting self-made memes about the Fediverse, based on established and more or less well-known meme templates. This should be clear, but I'd like to mention it anyway: These memes don't suppose that the Fediverse is only Mastodon, nor do they treat Mastodon as the centre of the Fediverse. @{fedimemes_on_streams@streams.elsmussols.net} <a href="https://streams.elsmussols.net/channel/fedimemes_on_streams" rel="nofollow noopener noreferrer" target="_blank">@⁠fedimemes_on_streams@streams.elsmussols.net</a> <a href="https://streams.elsmussols.net/channel/fedimemes_on_streams" rel="nofollow noopener noreferrer" target="_blank">https://streams.elsmussols.net/channel/fedimemes_on_streams</a> Lastly, I have a blog about OpenSim in German on WriteFreely that's somewhat dormant currently, but I still have a lot to write and post about. <a href="https://joinfediverse.wiki/What_is_WriteFreely%3F" rel="nofollow noopener noreferrer" target="_blank">WriteFreely</a> is basically Medium in the Fediverse. Again, if you understand German, you can follow the blog from anywhere in the Fediverse. But you can't reply to my blog posts; WriteFreely doesn't support comments. @<a href="https://publish.ministryofinternet.eu/jupiter-rowland/" rel="nofollow noopener noreferrer" target="_blank">Aus Hypergrid und Umgebung</a> <a href="https://publish.ministryofinternet.eu/jupiter-rowland/" rel="nofollow noopener noreferrer" target="_blank">@⁠jupiter-rowland@publish.ministryofinternet.eu</a> <a href="https://publish.ministryofinternet.eu/jupiter-rowland/" rel="nofollow noopener noreferrer" target="_blank">https://publish.ministryofinternet.eu/jupiter-rowland/</a> What it means that I'm on Hubzilla Next to my hashtags and mentions looking weird in comparison to what you're used to on Mastodon, the biggest "side-effect" of this is that my posts can grow truly massive for Mastodon standards. Where Mastodon has a hard-coded limit of 500 characters, Hubzilla does not have any real character limit at all. It has never had one, and its predecessor, Friendica, has never had one either. Thus, character limits of any kind are not part of Hubzilla's culture which is very, very different from Mastodon's culture in many ways. This means I don't do threads when I have to write a lot. I don't have to. I can put everything I want to post into one single post. Long posts are fortunately still something that Mastodon displays correctly even if you can't write them on most Mastodon instances. As far as I know, it's only above 100,000 characters that Mastodon rejects posts completely. And on Hubzilla, you can even post many times more characters than that. This post, for example, is longer than 42 Mastodon toots, and as you can see, I didn't break it down into a thread of well over 50 single posts. That is, if I really have to write something that's akin to a blog post with more than four embedded pictures, while I can do that as a regular post, I'll do it as a long-form article that doesn't federate and then link to it. I know that some of you mobile app users don't like your Web browser popping open, but trust me when I say it's the best solution, also due to what Mastodon does with embedded images which it can't display as such. Besides, I don't force you to tap that link to my newest article. It's highly unlikely that I'll post anything with that many images, though, because describing each image would be extremely tedious, and the image descriptions would take up horrendous amounts of room in the post. I'll come back to that again further down. How I handle images Which takes us to images. It's here where I do acknowledge some of Mastodon's limitations, seeing as well over 90% of the recipients of my posts are on Mastodon, what with how many newbies indiscriminately follow everything they come across to get their personal timeline busy, and others following me with the belief that I'm a Fediverse guru first and foremost. I no longer post more than four pictures at once in anything that federates into other people's or instances' timelines, streams or whatever. That's because Mastodon can't handle more than four file attachments, and Mastodon removes all embedded inline images from posts. I still embed the pictures someplace in my posts that is not at the bottom. The bottom is for hashtags which I haven't already used in the text. Yes, I make a lot of use of hashtags for everyone's convenience, and I always write them in CamelCase when appropriate and/or necessary. As for the embedded pictures, sometimes I explain in my posts where which picture that you'll find at the bottom of the post should be where in the text, but I don't always do that. How I handle alt-text and image descriptions I'm very serious about image descriptions, so I've been describing all my images for over a year. However, the topic I post pictures about, virtual worlds based on OpenSim, is very, very niche and very, very obscure. Probably only one in every over 200,000 Fediverse users has even heard of the general topic. This is not even close to common knowledge. So I have to assume that the vast majority of my audience needs it explained, needs everything in my images explained extensively to understand it. The topic of 3-D virtual worlds is a very visual topic, so it might not be interesting for blind or visually-impaired people. On the other hand, however, they may be excited about the discovery that the Metaverse is not dead, and that free, open-source, decentralised 3-D virtual worlds exist right now and have been since as long ago as 2007. Of course, they'll be curious, and they'll want to explore my images like someone would who can see them. To make that possible and satisfy their curiosity, I have to describe my images at extreme detail. In fact, I often have to do so anyway when a picture doesn't focus on anything specific. <a href="https://hub.netzgemeinde.eu/item/95b6e36d-7fcd-4791-8cc1-c93e8b9975a3" rel="nofollow noopener noreferrer" target="_blank">Here is an article in which I explain why image descriptions for virtual worlds have to be very long.</a> There is also the rule that any text within the borders of an image must be transcribed 100% verbatim. My images may contain a whole lot of bits of text. And this rule does not explicitly include or exclude text that is not fully readable for whatever reason. So I also transcribe text that can't be read in the image to be on the safe side. This means that my image descriptions may contain lots and lots of text transcripts. My full, detailed, explanatory image descriptions always go into the post text body, right below the images themselves, and not into the alt-text. They do so for two reasons. One reason is because they contain explanations and other things that may be useful for anyone, not only for blind or visually-impaired people. But not everyone can access alt-text. Some people can't handle a computer mouse steadily enough to make a mouse cursor hover above an image so that the alt-text shows up. Other people can't use pointing devices such as mice, trackballs, touchpads, trackpoints or the like at all. For example, they may use a pen in their mouth or a headpointer strapped to their forehead with which they can press the keys on the keyboard. These people can't access alt-text either. For those who can't access alt-text, any information exclusively available in alt-text and nowhere else is completely inaccessible and lost. If it's in the post itself, however, they can access it. The other reason is because my image descriptions are extremely long. If you as a Mastodon user think 800 characters are tremendously long, think again: My record for the description of one single image is <a href="https://hub.netzgemeinde.eu/item/f8ac991d-b64b-4290-be69-28feb51ba2a7" rel="nofollow noopener noreferrer" target="_blank">over 60,000 characters</a>. In words, over sixty-thousand. This is not a typo. But Mastodon, Misskey and their respective forks such as Glitch, Hometown, Ecko, Firefish, Iceshrimp, Sharkey or Catodon have a hard limit of no more than 1,500 characters for alt-text. Unlike the character limit for posts, they enforce this limit on external content by truncating it and removing all characters beyond the 1,500-character mark. I can post alt-text with 60,000 characters, but Mastodon will chop 58,500 of them off and throw them away. And even Hubzilla's Web interface is limited in how much alt-text it can show at once because it can't scroll through alt-text. Thus, my long image descriptions always go into the post itself. Nonetheless, I always write another image description for the alt-text. I have to satisfy those on Mastodon who absolutely demand a useful image description in the alt-text, no matter what. They may not care for there already being an image description in the post. In fact, I always hide these posts behind content warnings (see below), so they don't even see at first glance that there's an image description in the post unless I mention that in the content warning. To keep them from lecturing or sanctioning me for not adding alt-text to an image, I describe all my images twice. However, due to alt-text being limited in length, I can't make the description in the alt-text as informative as the one in the post. I never explain anything, and I often don't transcribe any text either if it's too much. But the alt-text always mentions the long description in the post, what it contains (explanations, transcripts) and where exactly to find it. How I handle sensitive content and content warnings First of all, Hubzilla is vastly different from Mastodon in this regard. Mastodon is a Twitter clone from 2016 that has introduced the use of the StatusNet summary field for content warnings in 2017. Hubzilla is from 2015, and it was created by renaming something from 2012 which, in turn, was a fork of a Facebook alternative from 2010. Hubzilla has never been developed against Mastodon, and it has never tried to mimic Mastodon. It was there long before there was Mastodon. And both its creator and its current maintainer don't want it to ape Mastodon. This means two things. One, the summary field which Mastodon has repurposed as a content warning field in 2017 is still a summary field on Hubzilla. It doesn't make sense to give a summary for 500 characters or fewer. But it does make sense to be able to give a summary if you're theoretically able to post millions of characters at once. So Hubzilla doesn't have Mastodon's CW field, at least not labelled "CW". And Hubzilla's culture was fully fledged and developed when Mastodon was launched in 2016, more so when Mastodon introduced the CW field in 2017, and even much more so when Mastodon exploded with Twitter refugees in 2022. Putting writer-side content warnings into the summary field (which, again, is labelled "CW" on Mastodon, but not on Hubzilla) is not part of Hubzilla's culture. Still, I do add Mastodon-style content warnings where I deem them appropriate. Apart from the usual suspects, of which I know hundreds, I add them for: <ul><li>long posts (absolutely everything over 500 characters)</li><li>Fediverse meta (whenever I post about the Fediverse)</li><li>Fediverse beyond Mastodon meta (when I post about Mastodon as well as the non-Mastodon Fediverse)</li><li>non-Mastodon Fediverse meta (when I only post about the non-Mastodon Fediverse, but not about Mastodon)</li><li>hashtag meta (whenever I post about hashtags)</li><li>alt-text meta (whenever I post about alt-text specifically)</li><li>image description meta (whenever I post about image descriptions in general)</li><li>content warning meta (whenever I post about content warnings)</li></ul> Two, Hubzilla has its own way of handling content warnings. It is called "NSFW". That's basically a simple word filter which can optionally activated that automatically hides posts behind content warning buttons, depending on the keywords in its word list. The word list is customisable, so everyone can get all the content warnings they desire, given sensitive posts have the necessary keywords or hashtags, and nobody has content warnings forced upon them they don't need. Hubzilla has had this feature since years before Mastodon introduced its CWs, and Hubzilla has inherited it from Friendica which has had it for even longer. But in order for these filters to be triggered successfully, a post needs to have the appropriate keyword or keywords in it. This works best with hashtags. This means that I have to double all my Mastodon-style content warnings with matching hashtags. However, in many cases, there is not only exactly one hashtag for the same kind of sensitive content that is universally used by everyone, not even in filters. Thus, there are often multiple hashtags going with the same content warning. In combination, this leads to masses of hashtags at the bottom of most of my posts as I add hashtags for almost all my content warnings. I know that some Mastodon users have a problem with more than four hashtags in one post, but warning people about sensitive content and triggering their filters to remove or hide said sensitive content is more important than coddling Mastodon users who still have Twitter on their brains. As for sensitive images, I have recently stopped posting any kinds of images of which I'm certain they're sensitive or triggering to someone on this channel. It is for these images that I've created (streams) channels for (see way above). (streams) can make Mastodon blank sensitive images out. Hubzilla can't do that. What it means when I follow you back Most of the time, it means nothing. It means that I let you follow me. It does not necessarily mean that I actually follow you back. This is due to a technical limitation on Hubzilla. I've set my channel up in such a way that I have to confirm all new connections. However, being a fork of a Facebook alternative, Hubzilla does not treat followers and followed as two separate things. Just like on Facebook, a connection is usually mutual by default. In practice, this means that when I confirm a new follower connection, I automatically "follow them back", i.e. create a mutual connection. This is hard-coded. I can't change it, not unless I let everyone follow me automatically without my consent. But this does not mean that all your posts actually appear on my stream. If you don't write anything that's within the scope of this channel, I won't allow you to deliver your posts to my stream. Hubzilla has an absolutely staggering set of fine-grained permission controls that makes it possible for me to deny other users the permission to send me their posts. If you write about OpenSim, I will allow your posts. If you write about Second Life, I might allow your posts. If you write about another virtual world that might be interesting for me, I might allow your posts. If you write about the Fediverse, and you don't reduce the Fediverse to only Mastodon, I might allow your posts. If you're an in-world acquaintance of mine who doesn't post about OpenSim, I very likely will allow your posts. If none of this applies, I won't allow your posts. I'll let your comments on other posts through, I'll let your direct messages through, but I won't let your posts clutter my stream. If I let your posts through, this doesn't necessarily mean I'll also let your boosts through. I can block boosts individually per connection. So unless your boosts are mostly interesting to me, I will block your boosts. If Hubzilla should ever improve their filters, and I let your posts through, I may still apply a filter that only lets through what I want to read if you post a lot of stuff that I don't find interesting within the scope of this channel. Finally If you aren't okay with any of this, feel free to block me now before it's too late. I don't care how many people follow me or can read my posts as long as the right ones can. But I will not change the way I post to make it more like Mastodon, especially not if I can't because something is hard-coded. Thanks for your patience. #<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=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=AltText" rel="nofollow noopener noreferrer" target="_blank">AltText</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener noreferrer" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener noreferrer" target="_blank">CWAltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener noreferrer" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">CWImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CW" rel="nofollow noopener noreferrer" target="_blank">CW</a> #<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=CWMeta" rel="nofollow noopener noreferrer" target="_blank">CWMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarning" rel="nofollow noopener noreferrer" target="_blank">ContentWarning</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=ContentWarningMeta" rel="nofollow noopener noreferrer" target="_blank">ContentWarningMeta</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=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=OpenSim" rel="nofollow noopener noreferrer" target="_blank">OpenSim</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=OpenSimulator" rel="nofollow noopener noreferrer" target="_blank">OpenSimulator</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Metaverse" rel="nofollow noopener noreferrer" target="_blank">Metaverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=VirtualWorlds" rel="nofollow noopener noreferrer" target="_blank">VirtualWorlds</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Introduction" rel="nofollow noopener noreferrer" target="_blank">Introduction</a>

Jupiter RowlandPossible advantages of sending my posts about virtual worlds only to those of my contacts who are involved in the topic already: <ul><li>I won't go on everyone else's nerves with these posts, especially those who don't use filters.</li><li>I won't have to spend hours or days researching for and writing image descriptions which would cause more people not to read my posts than help them understand them. To my best knowledge, none of my connections interested in virtual worlds requires image descriptions anyway. I could greatly increase my image output.</li><li>I won't have to make sure they won't see images with faces or eyes in them unless they explicitly want to. If eye contact triggered them, they'd avoid virtual worlds.</li><li>I won't even have to count characters and warn about long posts. I don't think anyone of them minds long posts.</li><li>I could reduce the number of hashtags because I wouldn't need all those which I use to trigger filters.</li></ul> On the other hand... <ul><li>Only they would ever see these posts. They won't be able to repost/boost/renote/repeat them. If they've got the capability of sharing/quote-posting them, they won't be able to do that either.</li><li>I'd break my track record of almost utmost compliance, over-compliance even, with the Fediverse's accessibility rules. Those who could possibly mind would never know because they'd never see the "offending" posts, but still.</li><li>That is, if one of the recipients managed to break the security, my utterly uncompliant post would be out there, maybe even encountered by someone who actually needs any of my usual accessibility measures.</li><li>It'd feel like weaseling out of my responsibilities as a Fediverse user.</li></ul> #<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=PrivacyGroups" rel="nofollow noopener noreferrer" target="_blank">PrivacyGroups</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Metaverse" rel="nofollow noopener noreferrer" target="_blank">Metaverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=VirtualWorlds" rel="nofollow noopener noreferrer" target="_blank">VirtualWorlds</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescription" rel="nofollow noopener noreferrer" target="_blank">ImageDescription</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptions" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">ImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWImageDescriptionMeta" rel="nofollow noopener noreferrer" target="_blank">CWImageDescriptionMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=EyeContact" rel="nofollow noopener noreferrer" target="_blank">EyeContact</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CW" rel="nofollow noopener noreferrer" target="_blank">CW</a> #<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=ContentWarning" rel="nofollow noopener noreferrer" target="_blank">ContentWarning</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> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarningMeta" rel="nofollow noopener noreferrer" target="_blank">ContentWarningMeta</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=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>

Jupiter RowlandWhen you've just written a post or a comment. When you discover it's over 500 characters. When you start pondering how you could shorten it to appease Mastodon users. And when you decide that it's much easier to add the <code>#Long #LongPost #CWLong #CWLongPost</code> filter-triggering hashtags and, if it's a post, a Mastodon-style long-post content warning in the summary. #<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=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=CharacterCount" rel="nofollow noopener noreferrer" target="_blank">CharacterCount</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=500Characters" rel="nofollow noopener noreferrer" target="_blank">500Characters</a>

Jupiter RowlandIt has become next to impossible to discuss content warnings in the Fediverse using hashtags. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CW" rel="nofollow noopener noreferrer" target="_blank">CW</a> has been hijacked by amateur radio where it stands for continuous wave. The few exceptions are about TV and refer to the CW Network. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWS" rel="nofollow noopener noreferrer" target="_blank">CWS</a> has recently been hijacked by a commercial advertising account. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarning" rel="nofollow noopener noreferrer" target="_blank">ContentWarning</a> has recently been hijacked for posts about the eponymous video game. And both #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarnings" rel="nofollow noopener noreferrer" target="_blank">ContentWarnings</a> and #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarningMeta" rel="nofollow noopener noreferrer" target="_blank">ContentWarningMeta</a> are too long to type on a screen keyboard. Not to mention that Mastodon is largely falling back into Twitter mannerisms, i.e. neglecting hashtags altogether, and most of the rest of the Fediverse has never had a hashtag culture to begin with. #<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=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://zirk.us/@theleavingyear" rel="nofollow noopener noreferrer" target="_blank">Kathryn</a> Three reasons. One, there's one Mastodon bot that scrapes cat pictures from various sources, slaps AI-generated alt-text on them with no human interaction, churns them out hourly and adds the #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener noreferrer" target="_blank">AltText</a> hashtag because they've got alt-text. Two, #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener noreferrer" target="_blank">AltText</a> should be used for discussing alt-text rather than image posts with alt-text which is why hardly any human user puts that hashtag on image posts. Three, hardly anyone seems to discuss alt-text anymore. That, or more and more Mastodon users have fallen back into Twitter mode and stopped using hashtags altogether. And outside of Mastodon, almost nobody knows about or cares for alt-text anyway. Thus, the bot-generated cat pictures dominate that hashtag. #<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=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=AltTextMeta" rel="nofollow noopener noreferrer" target="_blank">AltTextMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWAltTextMeta" rel="nofollow noopener noreferrer" target="_blank">CWAltTextMeta</a>

Jupiter Rowland@<a href="https://mastodon.social/@alttexthalloffame" rel="nofollow noopener noreferrer" target="_blank">Alt Text Hall of Fame</a> Maybe #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltText" rel="nofollow noopener noreferrer" target="_blank">AltText</a> is supposed to help with finding image posts that do have alt-text for a change. And #<a class="" href="https://hub.netzgemeinde.eu/search?tag=AltTextMeta" rel="nofollow noopener noreferrer" target="_blank">AltTextMeta</a> is for discussing it. But I don't make these definitions. #<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=CWAltTextMeta" rel="nofollow noopener noreferrer" target="_blank">CWAltTextMeta</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 RowlandI think I should add some the filter-triggering hashtags #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ReplyGuy" rel="nofollow noopener noreferrer" target="_blank">ReplyGuy</a>, #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWReplyGuy" rel="nofollow noopener noreferrer" target="_blank">CWReplyGuy</a>, #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mansplaining" rel="nofollow noopener noreferrer" target="_blank">Mansplaining</a> and #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWMansplaining" rel="nofollow noopener noreferrer" target="_blank">CWMansplaining</a> to my standard repertoire, in case my other filter-triggering hashtags aren't sufficient. They'd make it 51 characters more likely that I'll also have to add #<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> and #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> because what I've written surpasses the 500-character mark, much to many Mastodon users' chagrin. #<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=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://cupoftea.social/@MikeFromLFE" rel="nofollow noopener noreferrer" target="_blank">Mike</a> Fair warning ahead: This is going to be LONG. It often occurs that I add a whole lot of hashtags to a post. I started putting them all at the end of the post unless I'm explicitly talking about a hashtag that I also need as an actual hashtag, but still. Only about half the hashtags I use are only for discoverability. Many serve a different purpose, namely to trigger filters, including CW-generating filters. See, on Hubzilla where I am, sensitive people have their CWs individually automatically generated. Not only does this feature pre-date Mastodon's CW filters, it pre-dates Mastodon itself by several years. So it's part of our culture. But the best CW generator doesn't work if the posts, comments and DMs that need to be CW'd don't contain the appropriate keywords. And I add them as hashtags to reduce the risk of false positives. And I post a lot of stuff that people don't want to read. So I add the hashtags #<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> and #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> whenever a post or a comment exceeds 500 characters (raw count, not Mastodon count) so people can at least get rid of my long posts. It's obvious that two are only for filtering and one is partially for filtering. Whenever I write about the Fediverse, I add the hashtags #<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> and #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> because some people don't want to read anything concerning the Fediverse, even less if it's about the Fediverse outside Mastodon. When I write about hashtags, I add #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hashtag" rel="nofollow noopener noreferrer" target="_blank">Hashtag</a> and #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hashtags" rel="nofollow noopener noreferrer" target="_blank">Hashtags</a> for discoverability and #<a class="" href="https://hub.netzgemeinde.eu/search?tag=HashtagMeta" rel="nofollow noopener noreferrer" target="_blank">HashtagMeta</a> and #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWHashtagMeta" rel="nofollow noopener noreferrer" target="_blank">CWHashtagMeta</a> as a warning/filter trigger because I guess there are people who are fed up with reading about hashtags. I've got plenty of other topics with accompanying filter/CW-triggering hashtags, including but not limited to alt-text/image descriptions and content warnings themselves.

Jupiter RowlandHashtagging posts about content warnings has become nigh-impossible. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CW" rel="nofollow noopener noreferrer" target="_blank">CW</a> is most commonly used either for morse code ("continuous wave") or the CW Television Network. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarning" rel="nofollow noopener noreferrer" target="_blank">ContentWarning</a> has now been hijacked by a popular new video game of the same name, not to mention it's too long for users on phones anyway. And #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ContentWarnings" rel="nofollow noopener noreferrer" target="_blank">ContentWarnings</a> is even longer, so only those few who have hardware keyboards use it. #<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=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=ContentWarningMeta" rel="nofollow noopener noreferrer" target="_blank">ContentWarningMeta</a>

Jupiter Rowland@<a href="https://mastodon.social/@zahnfee" rel="nofollow noopener noreferrer" target="_blank">CEO Zahnfee Corporation GmbH</a> Vor allem, erklär den Leuten mal, daß in etwa die Hälfte deiner Hashtags dazu dient, Filter auszulösen. Ich glaube, die meisten Mastodon-Nutzer wissen gar nicht, daß Mastodon Filter hat, weil Mastodon keinen Filter-Button direkt in irgendeiner Timeline hat. Da, wo ich herkomme, nutzt man Filter sogar für automatische CWs. Anstelle von "CWs". #<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=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=Filter" rel="nofollow noopener noreferrer" target="_blank">Filter</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Filters" rel="nofollow noopener noreferrer" target="_blank">Filters</a>

Jupiter Rowland@<a href="https://theres.life/@DMakarios" rel="nofollow noopener noreferrer" target="_blank">Deborah Makarios</a> It's fair to mention at this point that hashtags aren't only ever used to increase visibility. They're also used to trigger the automated generation of reader-side content warnings. Yes, they exist. Not only does Mastodon itself have that feature since version 4.0 from last year. But Mistpark had it as early as 2010, almost six years before Mastodon existed. And unlike Mastodon, it did not repurpose the summary field for content warnings. From Mistpark emerged today's Friendica, Hubzilla and (streams). All three have this feature. All three don't have Mastodon's CW field; Hubzilla and (streams) still call it "summary" while Friendica lacks it altogether. At least Hubzilla and (streams) don't provide any means of adding a Mastodon CW to replies at all. And all three have had it in their cultures since they were launched to have CWs automatically generated individually for each reader by the "NSFW app". I am on Hubzilla, and I will not adjust my way of using it so that it becomes indistinguishable from posts on vanilla Mastodon by someone who only knows Mastodon. I will add 12 hashtags to this comment. The first four are to trigger filters that either remove or CW my posts and comments with over 500 characters because long posts disturb many Mastodon users. The next four are to trigger filters that either remove or CW my posts and comments about the Fediverse because many Mastodon users don't want to see that technical mumbo-jumbo. Yes, four of each. How am I supposed to know who uses which one of these in their filters? The next two are for discoverability purposes. The last two are for triggering filters again. So that's two discoverability hashtags and ten filter-triggering hashtags. #<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=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 RowlandMaybe I should start an irregular series of "What Hubzilla is like" posts for people in the Fediverse, Mastodon specifically, who don't know anything about it. Not for those who want to switch, but for those who assume that Hubzilla is just like whatever else they know. Like, for Mastodon users who blindly assume that Hubzilla is just like Mastodon with a different UI and then act accordingly. Thus, it'd mostly focus on how Hubzilla is different from Mastodon. The difficult part would be to limit these posts to only 500 characters. Minus what I'll need for the hashtags, namely #<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=FediTips" rel="nofollow noopener noreferrer" target="_blank">FediTips</a> and #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseTips" rel="nofollow noopener noreferrer" target="_blank">FediverseTips</a> to increase discoverability for those who are interested and #<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> and #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> so that these posts are automatically removed or hidden behind generated content warnings by already existing filters. Because I know for a fact that many Mastodon users won't touch anything that goes even a smidge over 500 characters. And I know that there are Mastodon users for whom any and all Fediverse meta is too nerve-gratingly techy. #<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=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 RowlandIn most of the cases, the hashtags #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mastodon" rel="nofollow noopener noreferrer" target="_blank">Mastodon</a> and #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Twitter" rel="nofollow noopener noreferrer" target="_blank">Twitter</a> mean, "lol idk how to mastodon n idk how to hashtag cuz ive never used them on twitter but u must use them here so ppl find yr toots." In fact, if you're on Mastodon or anything else that allows you to follow hashtags, following these two gives you about the same amount of meaningless noise as following everyone on your federated timeline. #<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=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>

Recent searches

Search options

Administered by:

Server stats:

#CWHashtagMeta