Musician.Social

Kevin Karhan :verified:<a href="https://tweesecake.social/@adisonverlice" class="u-url mention" rel="nofollow noopener" target="_blank">@adisonverlice</a> <a href="https://piraten-partei.social/@nick" class="u-url mention" rel="nofollow noopener" target="_blank">@nick</a> precisely.<ul><li>Whereas <a href="https://chaos.social/@delta" class="u-url mention" rel="nofollow noopener" target="_blank">@delta</a> couldn't hand over any data even if they wanted to and since it's <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FLOSS</a> any attempts at i.e. hardcoding a <a href="https://infosec.space/tags/backdoor" class="mention hashtag" rel="nofollow noopener" target="_blank">#backdoor</a> or <a href="https://infosec.space/tags/blocking" class="mention hashtag" rel="nofollow noopener" target="_blank">#blocking</a> domains would be trivial to detect and undo by virtue of <a href="https://infosec.space/tags/forking" class="mention hashtag" rel="nofollow noopener" target="_blank">#forking</a>.</li><li>Whereas with <a href="https://mastodon.world/@signalapp" class="u-url mention" rel="nofollow noopener" target="_blank">@signalapp</a> one has to rely on <a href="https://mastodon.world/@Mer__edith" class="u-url mention" rel="nofollow noopener" target="_blank">@Mer__edith</a> et. al.'s promise that the code they release - regardless if app but esoechally backend - is the code they run.</li></ul>Which is doubtful at best aka. "<a href="https://infosec.space/tags/TrustMeBro" class="mention hashtag" rel="nofollow noopener" target="_blank">#TrustMeBro</a>!" - level of guarantee…<ul><li>Also <a href="https://infosec.space/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Signal</a>'s business is unsustainable as unlike <a href="https://monocles.social/@monocles" class="u-url mention" rel="nofollow noopener" target="_blank">@monocles</a> they don't recoup operational costs from their users but act as <a href="https://infosec.space/tags/VCmoneyBurningParty" class="mention hashtag" rel="nofollow noopener" target="_blank">#VCmoneyBurningParty</a>, and that will inevitaboy backfire…</li></ul>

Kevin Karhan :verified:<a href="https://mastodon.social/@nixCraft" class="u-url mention" rel="nofollow noopener" target="_blank">@nixCraft</a> The problem is that <a href="https://mastodon.social/@mozillaofficial" class="u-url mention" rel="nofollow noopener" target="_blank">@mozillaofficial</a> refuses to acknowledge that <a href="https://infosec.space/tags/Firefox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Firefox</a> and it's promise of <a href="https://infosec.space/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#privacy</a> and <a href="https://infosec.space/tags/openness" class="mention hashtag" rel="nofollow noopener" target="_blank">#openness</a> is their "core <a href="https://infosec.space/tags/product" class="mention hashtag" rel="nofollow noopener" target="_blank">#product</a>" and that many people, including myself, will <a href="https://infosec.space/tags/divest" class="mention hashtag" rel="nofollow noopener" target="_blank">#divest</a> and <a href="https://infosec.space/tags/boycott" class="mention hashtag" rel="nofollow noopener" target="_blank">#boycott</a> any <a href="https://infosec.space/tags/donations" class="mention hashtag" rel="nofollow noopener" target="_blank">#donations</a> to them until they apologize and undo the harm they pushed with "<a href="https://infosec.space/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#AI</a>" / <a href="https://infosec.space/tags/LLM" class="mention hashtag" rel="nofollow noopener" target="_blank">#LLM</a> - based <a href="https://infosec.space/tags/Enshittification" class="mention hashtag" rel="nofollow noopener" target="_blank">#Enshittification</a>. <ul><li>And if that means we'll have the same situation as with <a href="https://infosec.space/tags/OpenOffice" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenOffice</a>, <a href="https://infosec.space/tags/Solaris" class="mention hashtag" rel="nofollow noopener" target="_blank">#Solaris</a> and <a href="https://infosec.space/tags/ZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#ZFS</a>, (where <a href="https://infosec.space/tags/Oracle" class="mention hashtag" rel="nofollow noopener" target="_blank">#Oracle</a> basically "mobbed" <a href="https://infosec.space/tags/developers" class="mention hashtag" rel="nofollow noopener" target="_blank">#developers</a> into <a href="https://infosec.space/tags/forking" class="mention hashtag" rel="nofollow noopener" target="_blank">#forking</a>-off into <a href="https://fosstodon.org/@libreoffice" class="u-url mention" rel="nofollow noopener" target="_blank">@libreoffice</a>, <a href="https://infosec.space/tags/illumos" class="mention hashtag" rel="nofollow noopener" target="_blank">#illumos</a> and <a href="https://mastodon.social/@openzfs" class="u-url mention" rel="nofollow noopener" target="_blank">@openzfs</a> ), then so be it.</li></ul>In fact, I hope <a href="https://infosec.space/tags/Firefox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Firefox</a> gets handed over to <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@torproject</a> and <a href="https://infosec.space/tags/TorBrowser" class="mention hashtag" rel="nofollow noopener" target="_blank">#TorBrowser</a> becomes the new <a href="https://infosec.space/tags/Upstream" class="mention hashtag" rel="nofollow noopener" target="_blank">#Upstream</a>!

Recent searches

Search options

Administered by:

Server stats:

#forking