Live data from Hacker News

Support for the IPFS Protocol – Firefox Bugzilla

bugzilla.mozilla.org

51–56 of 56 posts

Re: Support for the IPFS Protocol – Firefox Bugzilla

#51
post #37

Earlier quoted context omitted.

> So much faster. However, it does a poor job of blocking advertisements and trackers. I'll be going back to Firefox for that reason, I can suffer the slowness. What issues are you having with the blocking? /Disclaimer, Brave webcompat support

Not OP, but it doesn't block Twitter sponsored posts for me.

Clear cookies/cache, re-login. Check ads/trackers = Aggressive. We mostly fixed the twitter ads a while back.

Re: Support for the IPFS Protocol – Firefox Bugzilla

#52
post #7
post #2

There hasn't been a comment or status change to this bug in three years. I've been giving Brave a shot due to their recent addition of first-class support for IPFS, and the numerous positive HN comments. It's... So much faster. However, it does a poor job of blocking advertisements and trackers. I'll be going back to Firefox for that reason, I can suffer the slowness. One common response regarding performance woes on…

>It's... So much faster. However, it does a poor job of blocking advertisements and trackers. I'll be going back to Firefox for that reason, I can suffer the slowness. You can block ads just by editing your hosts file. There's no need to depend on any browser's particular functionality in order to get rid of them. Nor on extra hardware (Pi-hole), for that matter. I have a cron job download a prefilled copy from a pop…

Blocking ads via hosts file is a very basic method, delivers no flexibility to get around js/css, whitelisting sites. Acceptable only in a Pi-hole environment, but not in a stand alone browser.

Re: Support for the IPFS Protocol – Firefox Bugzilla

#53
post #34
post #2

There hasn't been a comment or status change to this bug in three years. I've been giving Brave a shot due to their recent addition of first-class support for IPFS, and the numerous positive HN comments. It's... So much faster. However, it does a poor job of blocking advertisements and trackers. I'll be going back to Firefox for that reason, I can suffer the slowness. One common response regarding performance woes on…

Firefox recently added HTTPS-Only Mode setting, basically equivalent to HTTPS Everywhere.

HTTPS only mode displays a warning every time the HTTPS version is not available.

HTTPS Everywhere/Brave tries to upgrade connections to https, if not falls back without throwing up annoying warnings.

Re: Support for the IPFS Protocol – Firefox Bugzilla

#54
post #39

Earlier quoted context omitted.

It sounds good in theory, but it just isn't true. Mozilla is null factor these days, and most of their income has actually been from Google. Google is most likely keeping them afloat just to ward off a stray monopoly charge at this point.

It became clear to me with the recent layoffs. Their strategy to grow their user share seemed twofold: better tech (through Servo/Rust) and dev-oriented features (their market share among devs was much higher than among the general population). They cut deeply into both of these.

Adding to this: Getting back dev mindshare was IMO critical for their success.

90% of https://webcompat.com/ is sites that are broken in Firefox, not necessarily because FF isn't standard compliant, but because many Web devs just dont bother testing their sites/apps with it anymore.

As for better tech I suppose they chose a 80/20 approach, but I'm not sure it will suffice.

Re: Support for the IPFS Protocol – Firefox Bugzilla

#55

Earlier quoted context omitted.

Let me tell you the future of using brave: you give chrome engine total rule of the law for web "standards". Google can mold the web to their desires. If you use firefox, google have to at least play nice. What's the point of using a browser frontend (used to be called chrome, but i guess google stole even the words) if tomorrow all the content depend on google-owned DRM? You will only be able to use your fancy ipfs…

It sounds good in theory, but it just isn't true. Mozilla is null factor these days, and most of their income has actually been from Google. Google is most likely keeping them afloat just to ward off a stray monopoly charge at this point.

Well, to be honest, nowadays I think that the sooner mozilla dies, the better for firefox :(

But anything will only happens if there's a user base as contributors are a (small) ratio from that number.

Re: Support for the IPFS Protocol – Firefox Bugzilla

#56
post #10
post #2

There hasn't been a comment or status change to this bug in three years. I've been giving Brave a shot due to their recent addition of first-class support for IPFS, and the numerous positive HN comments. It's... So much faster. However, it does a poor job of blocking advertisements and trackers. I'll be going back to Firefox for that reason, I can suffer the slowness. One common response regarding performance woes on…

Out of interest, why not use uBlock on brave? That's my setup.

Brave is based on Chrome (Chromium / Blink) and Google has deliberaely crippled ad-blocking extensions for it:

- https://www.zdnet.com/article/google-still-plans-to-cripple-...

- https://github.com/uBlockOrigin/uBlock-issues/issues/338

So you will get a sub-par ad-blocking / anti-tracking experience on Chrome or any of its clones like Brave or Vivaldi.

Post reply on HN