lingo.lol is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for linguists, philologists, and other lovers of languages.

Server stats:

55
active users

#manifest3

0 posts0 participants0 posts today
J. R. DePriest :verified_trans: :donor: :Moopsy: :EA DATA. SF:<p><a href="https://www.bleepingcomputer.com/news/google/google-chrome-warns-ublock-origin-may-soon-be-disabled/" rel="nofollow noopener" target="_blank">Google Chrome warns uBlock Origin may soon be disabled</a></p><p>As it was written, so it begins. </p><p>There is no Manifest v3 compatible uBlock Origin. It is simply not possible. <br>Firefox has its problems and its controversies and plenty of dumb decisions, but Manifest v3 is not one of them. Going forward, some variant of Firefox will be your only bet if you want robust ad-blocking extensions. <br>A PiHole can only get you so far. Unless you want to run a full traffic intercepting proxy at home with SSL decryption, you need something at the application layer. </p><p><a href="https://infosec.exchange/tags/Chrome" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Chrome</span></a> <a href="https://infosec.exchange/tags/ManifestV3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ManifestV3</span></a> <a href="https://infosec.exchange/tags/Manifest3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Manifest3</span></a> <a href="https://infosec.exchange/tags/Firefox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Firefox</span></a> <a href="https://infosec.exchange/tags/uBlockOrigin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>uBlockOrigin</span></a></p>
Cybarbie<p><span class="h-card" translate="no"><a href="https://tech.lgbt/@LilahTovMoon" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>LilahTovMoon</span></a></span> <a href="https://mastodon.social/tags/Brave" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Brave</span></a> will remain unaffected by the 3.0 change because it does not use easily bypassed extensions to enforce privacy controls and instead relies on an internal Rust-based engine. Barring that there is still no reason to use Firefox since <a href="https://mastodon.social/tags/mullvad" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mullvad</span></a> is based on the same engine and doesn't come with the <a href="https://mastodon.social/tags/Mozilla" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Mozilla</span></a> baggage. Finally I would like to point out that the impact is wider than just the browser. </p><p><a href="https://mastodon.social/tags/FuckTheseGuys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FuckTheseGuys</span></a> <a href="https://mastodon.social/tags/Manifest3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Manifest3</span></a></p>