@cwg1231 Similar experience. In my particular case, most inbound connections were from Russia, so applying a geo-block on RU did wonders.

It's still pinging more than I'd think it should, but at least it's banning the offenders.

@notesnook Heard really good things about Zen. Might have to give it a spin.

Love the work you're doing on Notesnook! Keep up the great work! 🫶

@notesnook Not sure if you're aware, but there's been a clarification added.
https://www.ghacks.net/2025/02/27/mozillas-new-terms-of-use-causes-confusion-among-firefox-users/

Again, I agree the wording is troubling. We'll have to see how this plays out. I feel like very little has changed, they've just updated their legal terms.

I, for one, won't be dropping @firefox. I already use Brave (and LibreFox and Cromite) as well for uncooperative websites and specific use cases.

If you're truly worried about this, I'd urge you to look into LibreFox or another fork.

@notesnook @brave I'll have to do more digging on the legal docs.

My point isn't necessarily to disable everything. You need to understand which toggles actually have an effect. This info is widely known for Firefox (hence projects like arkenfox and Betterfox).

It is troubling to see this sort of wording in a Mozilla policy.

Nothing against Brave, btw. If you insist on sticking to Chromium, it's not a bad option. I'd just hate to see Firefox lose more users, as it's the only alt to Chromium.

@notesnook @brave Simple solution: don't input or upload data to Firefox. If you need to sync bookmarks, use Floccus or Syncthing.

Disable search suggestions, AI, translation, etc. It's quite easy to avoid giving them data if you're willing to dive into the settings.

For the record, Brave takes even more work to disable that crap. I'm nearly certain Brave already has clauses like this. There's simply no way they could provide AI tools without them.

Fret not, @firefox is alive and well.

@rdp I've no idea what "Login Mode for Public Hotspots" is, but IME the most common cause of an inability to reach the captive portal is a modified system DNS configuration.

For example, if I enable 'Secure DNS' on my Android phone, which utilizes the #NextDNS filtering service, I won't see captive portals. Even if you've just hardcoded in 1.1.1.1 or similar, that will prevent the device from reaching the captive portal.

Try resetting to defaults if anything's been changed.

@gophergrad If I didn't know this was happening across the country, I'd think this were a joke.

🤦‍♂️

Prohibition, censorship, and otherwise authoritarian methods for controlling the actions of citizens have proven ineffective time and again. Will we ever learn?