shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

258
active users

#cromite

0 posts0 participants0 posts today
Naty<p>I've stopped using Firefox since the drama a while back... Using <a href="https://fosstodon.org/tags/ZenBrowser" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ZenBrowser</span></a> and <a href="https://fosstodon.org/tags/LibreWolf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LibreWolf</span></a> mainly on macOS and on <a href="https://fosstodon.org/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Android</span></a>, <a href="https://fosstodon.org/tags/Ironfox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ironfox</span></a> and <a href="https://fosstodon.org/tags/Cromite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Cromite</span></a> (as an alt browser). But I'm having quite a lot of website functionality problems when using Ironfox. Can't create accounts, forms not working, can't use <a href="https://fosstodon.org/tags/webauthn" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>webauthn</span></a>, pages not loading correctly, checkouts or shopping sites broken, etc. I guess I need to have <a href="https://fosstodon.org/tags/Firefox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Firefox</span></a> still installed... It's annoying. What's your workaround? <a href="https://fosstodon.org/tags/browsers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>browsers</span></a> <a href="https://fosstodon.org/tags/androidbrowser" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>androidbrowser</span></a></p>
Fabio Manganiello<p><span class="h-card"><a class="u-url mention" href="https://floss.social/@danslerush" rel="nofollow noopener noreferrer" target="_blank">@<span>danslerush</span></a></span> <span class="h-card"><a class="u-url mention" href="https://exquisite.social/@thomholwerda" rel="nofollow noopener noreferrer" target="_blank">@<span>thomholwerda</span></a></span> I still use Firefox on my mobile devices (mostly because it’s the only mobile browser that allows extensions), and <a class="hashtag" href="https://manganiello.social/tag/cromite" rel="nofollow noopener noreferrer" target="_blank">#Cromite</a> for everything that usually requires PWAs (Mozilla’s support for PWAs is still outrageously primitive, and I feel like they’ve really run out of excuses).</p><p>The problem is that, even though Cromite is basically a version of the open Chromium browser minus all things Google, it’s still based on the same engine.</p><p>I feel the urge for a new rendering engine, but let’s admit that, given the complexity of today’s Web technologies, we shouldn’t expect a community-driven project to get to the point where it can compete with Blink (or even Gecko and WebKit) any time soon. Unless the EU starts putting its wallet where its mouth is and pours a couple of billions into such an initiative, instead of burning $300B just to chase the AI train.</p><p>Btw WebKit-based browsers (like surf) could be an option in the meantime, but outside of Safari I don’t see much development happening on that front.</p><p>Unfortunately Mozilla lost this train long ago when it decided that it didn’t want to decouple Gecko excessively from Firefox, so it’s harder to build browsers on their engine than it is with Blink/WebKit (unless you just provide Firefox with a different menu and a different skin).</p><p>I would also rephrase this constraint:</p><blockquote><p>And usable with uBlock Origin</p></blockquote><p>As:</p><blockquote><p>Committed to be compatible with Extensions Manifest V2, forever and without compromises</p></blockquote><p>At the current stage even the browsers that have stated that they’ll keep supporting Manifest V2 (namely Firefox and Brave) have also added a “let’s see how feasible it is on the long run” as an asterisk.</p><p>Personally I wouldn’t mind using a Blink/WebKit-based browser, as long as it meets all the other requirements and, most of all, if it commits to support V2 forever.</p>
Fabio Manganiello<span class="h-card"><a class="u-url mention" href="https://twit.social/@rlounsbury" rel="nofollow noopener noreferrer" target="_blank">@<span>rlounsbury</span></a></span> After a coupe of hours using <a class="hashtag" href="https://manganiello.social/tag/cromite" rel="nofollow noopener noreferrer" target="_blank">#Cromite</a> I actually wish I had discover it earlier - it literally ticks all the boxes.