Live data from Hacker News

IPFS Support in Brave

brave.com

351–360 of 464 posts

Re: IPFS Support in Brave

#351
post #312

Earlier quoted context omitted.

Brave is the new firefox...or should I say the old.

Not at all. It is based on the Web engine of the most used browser. Firefox is still Firefox, the big difference for me with the 2000s being the decline of its market share and that it doesn't compete with a browser with a non standard-compliant browser. Instead, it competes with a browser that defines the standards.

Old Firefox was a platform that ran a unique ecosystem of extensions, had innovative features that nobody on IE6 had and represented a push towards a web that didn't quite exist yet - an open place with standards where developers were free of having some disinterested tyrant controlling what they could do.

It is still Firefox, but that battle has been won. Firefox won it, then Google came in with Chrome and pounded the old way into the dust. It is gone now, mostly forgotten and good riddance.

Brave is a more in the character of Firefox than Firefox in many ways. There is a vision in there somewhere of a new web where users are one of the primary beneficiaries of advertising dollars (!) and intermediaries like Google are cut out of the picture. That is a very bold vision. I don't think Mozilla is capable of that sort of out-there visionary approach to browser design. Succeed or fail, Brave is trying.

Re: IPFS Support in Brave

#352

Earlier quoted context omitted.

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…

Freedom of speech should not guarantee 'right to global reach'. People should be allowed to say what they think to an amount of people who they can have personal relationships with, their neighbors, relatively close colleagues and similar. Deplatforming should not take this away, it should just take the biggest megaphone away mankind invented to date.

It’s still speech suppression and support of it, even if you think it’s justified.

Re: IPFS Support in Brave

#353

I tried to switch fully to Brave, but I had issues with Sync, messing up my 400+ bookmarks (thanks regular backups for the recovery), plus I really dislike uphold, as I had terrible experiences with them. Any plan to at least allow using other crypto platforms like coinbase?

Sorry for the sync problem -- should be fixed now, if you are willing to try it again. We talk to many custodians and would love to partner with Coinbase. We've added Gemini (creator wallets now, user next) and are adding bitFlyer. So options beyond Uphold to comply with regional regulations, as well as to give users choice, are coming.

Lovely, thanks for the info :)

Re: IPFS Support in Brave

#354

I know little about this protocol. It seems to make things better like client privacy, server versioning and censorship of good actors. As usual, nobody bothered to worry about problems it worsens. Do we want more anonymity and less censorship for bad actors? Good and bad may be subjective, but nearly everyone looks at that issue pragmatically in some instances (to pick an unlikely example: some demented billionaire…

The people who produce anti-censorship tools usually philosophically believe that it’s not the job of a communications tool to enforce acceptable speech. It’s sort of like complaining that making it easier to vote brings the average voter education level down. The people making it easier are certainly aware but don’t think it’s right to make it more difficult to vote.

The first paragraph is a good assessment of the current state of affairs.

That said, it's not a given that it be all or nothing. In fact, my complaint is specifically that we don't often ask such questions.

There might be ways we haven't exploited yet to disincentivize certain behaviors. Whoever invented Bitcoin, for example, had to take problems with incentives into account that, at first glance, seem intractable.

Given the way the internet turned out, we should think seriously about how people wind up using new tech in practice, rather than assume everything will just work itself out for the best.

Re: IPFS Support in Brave

#355
post #148

Earlier quoted context omitted.

I'm not terribly familiar with all the features that Multi-Account Containers offer. Does SessionBox for Chrome not meet your needs for some specific reason?

There is an extension for everything, that’s not the point. Firefox ships it as standard and supports it as such.

There's a similar thing shipped in Chrome now called Tab Groups, you just have to enable it behind chrome://flags.

In my view it's nowhere near as nice as it is on Firefox, with site isolation (Facebook, Google, Twitter, reddit), temporary containers, and a myriad of other add-ons that improve managing them (keyboard shortcuts and transition rules are the two I use the most).

Re: IPFS Support in Brave

#356
"Hey, check out this cool image of a van Gogh painting I found. It's at ipfs://bafybeiemxf5abjwjbikoz4mc3a3dla6ual3jsgpdr4cjr3oz3evfyavhwq/wiki/Vincent_van_Gogh.html"

I think they need to work on making these urls human readable.

Re: IPFS Support in Brave

#357
post #154

Earlier quoted context omitted.

For me, somewhat embarrassingly, the one killer feature is the "Send to Device" feature from firefox on iOS. Being able to send links to browser for later reviewing is super useful. Not sure why Edge or other browsers don't implement

This is a killer feature for me too. Works great between all my devices across Linux, Android, and iOS. If I see an interesting article I just ship it off to my desktop to read later instead of keeping the tab open for days on my phone.

I use getpocket for saving links to read, which is cross platform, including the web.

Re: IPFS Support in Brave

#358
post #222

Earlier quoted context omitted.

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/

Thanks!

Re: IPFS Support in Brave

#359

I know little about this protocol. It seems to make things better like client privacy, server versioning and censorship of good actors. As usual, nobody bothered to worry about problems it worsens. Do we want more anonymity and less censorship for bad actors? Good and bad may be subjective, but nearly everyone looks at that issue pragmatically in some instances (to pick an unlikely example: some demented billionaire…

I was thinking the same: Who is responsible to deal with my GDPR removal request?

Re: IPFS Support in Brave

#360

Massive. I have a project that assumed ipfs:// would eventually exist natively within a mainstream(-ish) browser, and I'm very pleased to discover that after updating to 1.19.x it all just works. Excited for the forthcoming DNSLink support too, even if it's just a bridge to something even better. Best of luck to everyone who wants the web to stay bundled inside of the corporate state.

I wrote this somewhere below as well but I'm honestly confused. It seems like I can load ipfs:// links just fine on my firefox. Is there something I'm missing? Edit: you guys are right. it seems i have installed the add-on some time ago and forgot about it.

do you have metamask installed?
Post reply on HN