Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Support for the IPFS Protocol – Firefox Bugzilla

bugzilla.mozilla.org

Post reply on HN
Print view View original

31–40 of 56 posts

Re: Support for the IPFS Protocol – Firefox Bugzilla

#31

Post by [deleted] »

arduinomancer wrote: post #15
Funes- wrote: post #7

Earlier quoted context omitted.

>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…

That doesn't work if the website serves the ads from the same domain as the content. For example YouTube ads.

[deleted]

Re: Support for the IPFS Protocol – Firefox Bugzilla

#34

Post by mbaye »

dleslie wrote: 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.

Re: Support for the IPFS Protocol – Firefox Bugzilla

#36

Post by toomim »

miohtama wrote: post #35

Is there any reason IPFS wizards could not implement IPFS or equivalents over WebRTC peer-to-peer, as in-page JavaScript application? Even if this were not the real thing, it would bring it closer to the mainstream more quickly.

It's technically feasible. IPFS not so different from Bittorrent, and Bittorrent can run over WebRTC: https://webtorrent.io/

In fact, webtorrent happens to be my favorite bittorrent client.

In general, I wish that more decentralized web tech didn't go about creating incompatible protocols. (Context: I'm working on Braid (https://braid.news) which is adding decentralized tech into today's WWW.)

Re: Support for the IPFS Protocol – Firefox Bugzilla

#37

Post by mp3geek »

dleslie wrote: 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…

> 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

Re: Support for the IPFS Protocol – Firefox Bugzilla

#38

Post by bawolff »

isaacimagine wrote: post #3

There are lots of very interesting and useful protocols, from ipfs to gopher, hyper to i2p, from freenet to zeronet, etc. - I think it would be cool if browsers added an extensible framework for adding new protocols.

Isn't that what extensions are?

Re: Support for the IPFS Protocol – Firefox Bugzilla

#39

Post by pygy_ »

RedComet wrote: post #22
gcblkjaidfj wrote: post #19

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.

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.

Re: Support for the IPFS Protocol – Firefox Bugzilla

#40

Post by j-james »

miohtama wrote: post #35

Is there any reason IPFS wizards could not implement IPFS or equivalents over WebRTC peer-to-peer, as in-page JavaScript application? Even if this were not the real thing, it would bring it closer to the mainstream more quickly.

It's so technically feasible that it already exists. Admittedly still in alpha, but rather feature-complete. There's even a nice demo built into the landing page.

https://js.ipfs.io/

Post reply on HN