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.)<br><br>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.<br><br>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.<br><br>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 <em>vastly</em> better than Mastodon's poster-side content warnings that are forced upon everyone all the same.<br><br>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.<br><br>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).<br><br>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.<br><br>I myself post stuff that some people don't want to see all the time. Hence, I need a whole lot of hashtags.<br><br>Let me explain the "hashtag wall" at the bottom of this comment to you.<br><br><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><br>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.<br>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><br>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.<br>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><br>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.<br>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><br>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").<br>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><br>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><br>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><br>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><br>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><br>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.<br>Why two hashtags if they're the same on Mastodon? Because they are <em>not</em> 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><br>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><br>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><br>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.<br>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><br>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><br>The same as above, but making clear that it's supposed to stand in for a content warning ("CW: hashtag meta").</li></ul><br>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.<br><br>#<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>