Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://possum.city/@mook" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>mook</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@MastodonEngineering" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>MastodonEngineering</span></a></span> <br>Well, no because that's why it's explicitly <em>not a duplicate</em>:</p><ul><li><p>This should be a setting available to users and not require admin access to the instance, which your suggestion definitely need.</p></li><li><p>Also Mastodon basically doesn't have any good ways to support blocklist feeds like that - which is <em>WHY</em> I opened that issue.</p></li><li><p>If people have to manually export blocklists from their profile and than diff/merge multiple feeds on their own system just to update these and reimport that as a replacement, that's basically a <code>F-</code> in <a href="https://infosec.space/tags/UI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UI</span></a> & <a href="https://infosec.space/tags/UX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UX</span></a> because that's a shit workflow that I'd expect from a crappy <a href="https://infosec.space/tags/MSDOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MSDOS</span></a> tool and not a modern <a href="https://infosec.space/tags/WebApplication" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebApplication</span></a> that already requires <a href="https://infosec.space/tags/JS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JS</span></a> just for the UI: If anyone then Mastodon should implement these things in UI in their Software!!!</p></li><li><p><a href="https://infosec.space/tags/glitchsoc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>glitchsoc</span></a> does have <a href="https://infosec.space/tags/markdown" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>markdown</span></a> support and I use it extensively, but this should be a mainline feature and not require a <a href="https://infosec.space/tags/fork" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fork</span></a> like <code>glitchsoc</code> to begin with.</p></li></ul><p>I do have the sneaking suspicion that with <a href="https://infosec.space/tags/Mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Mastodon</span></a>, the way it's maintained is basically <span class="h-card" translate="no"><a href="https://mastodon.social/@Gargron" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>Gargron</span></a></span> does: <em>'I sez so!'</em> and that's it.</p><ul><li>Again, <a href="https://github.com/mastodon/mastodon/issues/28605" rel="nofollow noopener" target="_blank">read the issue again</a> and tell me how the average, <em><a href="https://infosec.space/tags/TechIlliterate" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechIlliterate</span></a></em> user can be helped otherwise than how every other Software like <a href="https://infosec.space/tags/pfBlockerNG" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pfBlockerNG</span></a> does it by exposing a simple UI to configure that and automatically update and merge those...</li></ul><p>If <em>any</em> solution to issues with <a href="https://infosec.space/tags/Mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Mastodon</span></a> require a user to have privilegued access, 3rd party tools or fiddle with the <a href="https://infosec.space/tags/CLI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CLI</span></a> I consider it <em>"unfixed"</em> because <em>this shouldn't have to exist to begin with</em> - espechally for the average user!</p>