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

IPFS Support in Brave

brave.com

Post reply on HN
Print view View original

201–210 of 464 posts

Re: IPFS Support in Brave

#201

Post by sebmellen »

miguelmota wrote: post #197

I recommend Pinata [0] for IPFS pinning if you do not want to host your own IPFS node. I'm not sure when they'll start charging but it's been free since they launched and I believe Infura [1] also has free pinning. Cloudflare [2] is a good alternative gateway to use. For deployment I use this deploy tool [3] which makes it as simple as `ipd -p pinata my-app` to host a static frontend. [0] https://pinata.cloud/ [1] ht…

Piñata is great and I'm a happy user, but one note: Piñata is not free above 1GB. You can see their pricing page here: https://pinata.cloud/pricing.

Re: IPFS Support in Brave

#202

Post by pojntfx »

Awesome! I just hope that some institution (looking at you, EU) forces Apple to finally allow third-party browser engines on iOS, so that IPFS support is available on that platform (w/o a gateway).

Re: IPFS Support in Brave

#203

Post by sebmellen »

christiansakai wrote: post #161

I feel like the golden age of front end is just coming to ripe. Ethereum smart contract toolchain is written in JavaScript, browser wallet like Metamask is the defacto way to interact with user's wallet without having to send any sensitive information (private key) to the server, and now with IPFS as well! Dare I dream that an entire frontend assets (compiled html, js, css) is hosted on IPFS, making a truly decentral…

This is already the case with Uniswap: https://uniswap.org/blog/ipfs-uniswap-interface/.

Let's see if the underlying economic models can mature to be viable in the "real world," or at least the digital real world. BAT, for example, made Brave possible, but the tokenomics are bad and basically no one uses it.

That said, it is an exciting time, for sure! JavaScript sure has grown from humble beginnings.

Re: IPFS Support in Brave

#204

Post by not_really »

pojntfx wrote: post #202

Awesome! I just hope that some institution (looking at you, EU) forces Apple to finally allow third-party browser engines on iOS, so that IPFS support is available on that platform (w/o a gateway).

That would be amazing, but unfortunately I'd estimate that hell will freeze over before that happens.

Re: IPFS Support in Brave

#205

Post by kickscondor »

adkadskhj wrote: post #60

Can anyone compare Brave to Beaker Browser? I've long been interested in Dat vs IPFS, so i'm curious how their browser counterparts behave. I suppose right off the bat, Brave is a "normal" browser - so it just supports +1 protocol. That's really cool.

Beaker also supports regular web links - but Brave also supports Tor websites.

However, Beaker has its own extended web API and tooling. You can fork websites, edit them - and you can script this functionality. (For example, I have a wiki software in Beaker that will handle all the forking and editing behind the scenes - using Javascript to make it happen.)

You could say that Brave is a read-only HTML browser with wide support for decentralization protocols. While Beaker is a read-write HTML browser with its own protocol. And they both use the regular web as well.

Re: IPFS Support in Brave

#206

Post by al_chemist »

aarpmcgee wrote: post #192
jjordan wrote: post #174

Earlier quoted context omitted.

It's a statement in support of suppressing speech, and it's needlessly political. Mozilla leadership has mostly rested on their laurels (read: Google money) while Firefox consistently slid in market share. I've been a loyal FF user for 17 years, and this was the final straw. In the process of switching to Brave.

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 just the temporary silencing or permanent removal of bad actors from social media platforms."

Blocking, silencing and removal does suppress speech.

Re: IPFS Support in Brave

#207

Post by onelovetwo »

justsee wrote: post #64
joshuakelly wrote: post #29

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.

It really is great to see challenger browsers pushing the web forward like this. Along with IPFS it's nice to see Tor integration, low-level content blocking, a privacy-respecting Zoom alternative ( https://together.brave.com/ ) and integrated MetaMask for Web3. Brave still has a small userbase (~24 million), but hopefully it creates the space / incentives for Firefox and others to play catch-up so we see a lot of th…

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

Re: IPFS Support in Brave

#209

Post by onelovetwo »

simmanian wrote: post #195
joshuakelly wrote: post #29

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.

when you type this in your address bar what do you see? ipfs://bafybeiemxf5abjwjbikoz4mc3a3dla6ual3jsgpdr4cjr3oz3evfyavhwq/wiki/Vincent_van_Gogh.html

Re: IPFS Support in Brave

#210

Post by BrendanEich »

neiman wrote: post #181

Do they always refer to the same gateway, dweb.link? Is there a way to change this gateway? Otherwise all of ipfs will end up going through dweb.link, and that's how you centralized a decentralized technology.

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).
Post reply on HN