bolha.us

0 posts0 participants0 posts today

jbz<a href="https://indieweb.social/tags/Librefox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Librefox</a> is too "secure", some fonts don't even show up because of it's strong RFP I guess.

Le͢ẃ Gr͏ant͡If you've wondered what's going on with the recent <a href="https://ohai.social/tags/mozillafirefox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mozillafirefox</a> <a href="https://ohai.social/tags/firefox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#firefox</a> kerfuffle <a href="https://mastodon.online/@gardiner_bryant" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@gardiner_bryant</a> has posted a video that is a good catch-up and throws a little water <a href="https://youtu.be/m_TdA7AdTww" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://youtu.be/m_TdA7AdTww</a> Though my job as a software developer means I use a lot of browsers and platforms for testing my non-testing use is currently : <a href="https://ohai.social/tags/Safari" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Safari</a> in <a href="https://ohai.social/tags/MacOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MacOS</a>, FireFox on <a href="https://ohai.social/tags/windows" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#windows</a> and <a href="https://ohai.social/tags/LibreFox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LibreFox</a> on <a href="https://ohai.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a>. So I'm chrom(e/ium) free... except all those pesky <a href="https://ohai.social/tags/Electron" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Electron</a> apps ¯\_(ツ)_/¯

PointlessOne :loading:> No, we are absolutely not prepared to do that. We are a (very) small team with a rather limited amount of time (and energy) to work on LibreWolf even with it just the way it currently is. We would not even remotely be able to fork and maintain a browser fully, let alone to continually develop and improve it. Nor would we have the expertise to do so. Which would mean that if we tried to do that, we would most certainly release an insecure product, getting worse over time, which I would not ever want to be responsible for. > > Sorry to disappoint on that front – but: it is what it is.<a href="https://codeberg.org/librewolf/issues/issues/2252#issuecomment-2886286" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://codeberg.org/librewolf/issues/issues/2252#issuecomment-2886286</a><a href="https://status.pointless.one/tags/librefox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#librefox</a> <a href="https://status.pointless.one/tags/firefox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#firefox</a>

Recent searches

Search options

Administered by:

Server stats:

#librefox