IPFS Support in Brave • Hacker News Board

Re: IPFS Support in Brave

#231

Post by tarruda » Wed, Jan 20, 2021, 1:46 AM UTC

jjcon wrote: post #136

tarruda wrote: post #65

Earlier quoted context omitted.

It is easier for Brave to deliver new features when the biggest work is done by Chrome team.

> It is easier for Brave to deliver new features when the biggest work is done by Chrome team. Do you think Mozilla will ever switch to chromium? It is the linux of the web - would be nice if they could finally focus and stop dressing up their dead horse.

> Do you think Mozilla will ever switch to chromium?

I don't think so. If they did, there wouldn't be much incentive for using Firefox.

> It is the linux of the web - would be nice if they could finally focus and stop dressing up their dead horse.

And what would they be focusing on exactly?

Re: IPFS Support in Brave

#232

Post by undefined1 » Wed, Jan 20, 2021, 1:56 AM UTC

autocorr wrote: post #186

undefined1 wrote: post #99

Earlier quoted context omitted.

Mozilla seems to be moving in the other direction now. "We need more than deplatforming" https://blog.mozilla.org/blog/2021/01/08/we-need-more-than-d...

Taken out of context that quote would imply "we need even more serious censorship", but admits that deplatforming a certain world leader is a not a real solution and that these actions that should be taken: > Reveal who is paying for advertisements, how much they are paying and who is being targeted. > Commit to meaningful transparency of platform algorithms so we know how and what content is being amplified, to whom…

"We need more than deplatforming" is the literal headline, and they support it in the post:

"Changing these dangerous dynamics requires more than just the temporary silencing or permanent removal of bad actors from social media platforms. Additional precise and specific actions must also be taken"

Note: More than. Additional. Also.

Re: IPFS Support in Brave

#233

Post by 0df8dkdf » Wed, Jan 20, 2021, 1:58 AM UTC

0df8dkdf wrote: post #14

needz wrote: post #11

Neat. Still can't make the switch until they have an equivalent to Firefox containers.

just use the chrom profile it is same as containers in firefox.

why is the down voted? I do like to know the difference between container in firefox vs chrome profile. The only thing is that ok bookmarks don't work across profiles. And you don't have alwasy open in container option.

Re: IPFS Support in Brave

#234

Post by musicale » Wed, Jan 20, 2021, 2:01 AM UTC

agilob wrote: post #40

Mozilla promised us Tor integration, IPFS integration and more private browsing by default. Brave delivered it all.

> Mozilla promised us Tor integration, IPFS integration and more private browsing by default. Brave delivered it all.

Interesting. When Mozilla promise this, and what sort of time frame were they talking about?

Presumably "more private browsing" has been delivered somewhat already in Firefox?

Re: IPFS Support in Brave

#235

Post by redmaverick » Wed, Jan 20, 2021, 2:05 AM UTC

There are no youtube ads that play on Brave. This is my number one reason why I use Brave.

Re: IPFS Support in Brave

#236

Post by momack2 » Wed, Jan 20, 2021, 2:07 AM UTC

neiman wrote: post #222

BrendanEich wrote: post #210

Earlier quoted context omitted.

No, other browsers and extensions use a gateway. This is a Go-IPFS local node, downloaded on demand (or you can run your own and connect via it).

No, they're using a gateway in case you didn't choose to install your own go-ipfs local node.

On this page in Brave (chrome-extension://nibjojkomfdiaoajekhjakgkdhaomnch/dist/options/options.html) you can choose any IPFS gateway you prefer (or even run your own gateway if you want!).

List of public IPFS gateways available here: https://ipfs.github.io/public-gateway-checker/

Re: IPFS Support in Brave

#237

Post by benhylau » Wed, Jan 20, 2021, 2:07 AM UTC

There are several new and exciting decentralized web protocols. I am working on a tool to publish to all of them. Right now it publishes to IPFS and Hypercore, and will eventually serve signed plaintext so content can be shared to Scuttlebutt and Aether networks.

For example, this site is published using https://github.com/hyphacoop/api.distributed.press and it can be accessed over HTTP, IPFS, and Hypercore.

https://staging.compost.digital

ipns://staging.compost.digital

hyper://staging.compost.digital

(gateway) https://ipfs.distributed.press/ipns/staging.compost.digital/

(gateway) https://hyper.distributed.press/staging.compost.digital/

Re: IPFS Support in Brave

#238

Post by abdulmuhaimin » Wed, Jan 20, 2021, 2:08 AM UTC

Brave is becoming more and more compelling.

How I wish they develop their own engine(I know, tough task), or at least use Firefox's. Chromium based browser is really a deal breaker for me

Re: IPFS Support in Brave

#239

Post by aarpmcgee » Wed, Jan 20, 2021, 2:08 AM UTC

al_chemist wrote: post #206

aarpmcgee wrote: post #192

Earlier quoted context omitted.

I don't see anything in that post about suppressing speech—can you help me see it? The main bullet points in the article don't seem to have anything to do with suppressing speech (unless that is how you are framing the bullet point which reads: "Turn on by default the tools to amplify factual voices over disinformation."

It starts with title "We need more than deplatforming" which means "deplatforming is good, but it's not enough". noun: deplatforming; noun: de-platforming the action or practice of preventing someone holding views regarded as unacceptable or offensive from contributing to a forum or debate, especially by blocking them on a particular website. It continues with "Changing these dangerous dynamics requires more than jus…

I appreciate your followup here! Thanks.

Re: IPFS Support in Brave

#240

Post by rurp » Wed, Jan 20, 2021, 2:11 AM UTC

dleslie wrote: post #81

jonathansampson wrote: post #49

Earlier quoted context omitted.

And we will continue to deliver :) Thank you for the support!

I've been using Firefox since its inception, and was a Netscape user before that. I _briefly_ tried Chrome, but swiftly returned to Firefox. Half my extensions are still broken on Firefox Android. I've been using Firefox desktop on my PinePhone off-and-on and not only do all of my extensions work, but it's snappy and has a superior UX. I can actually access and manage my bookmarks with a sane interface. And yet even…

I too have recently departed the Firefox evangelism train after a great many years promoting the browser to all of my friends and family. The org has become far too disdainful of users. The constant UI/UX regressions are awful for people who just want their browser to work (ie. the vast majority of users), and management are more interested in political posturing than browser development.