IPFS Support in Brave • Hacker News Board

Re: IPFS Support in Brave

#401

Post by pocketgrok » Wed, Jan 20, 2021, 3:11 PM UTC

roenxi wrote: post #351

jraph wrote: post #312

Earlier quoted context omitted.

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

Firefox is still the browser that maintains the challenger engine.

Brave is more like Opera by building in support for a bunch of additional protocols.

Re: IPFS Support in Brave

#402

Post by CyberRabbi » Wed, Jan 20, 2021, 3:25 PM UTC

Draken93 wrote: post #397

imtringued wrote: post #389

Earlier quoted context omitted.

Well, in the case of violence it is quite easy to pass judgement and just lock them up. However, that doesn't mean you shouldn't listen to those terrorists. Even if they only talk bullshit you should at least try to understand why they became terrorists or else you will just declare more and more people as terrorists because it is the easy way out.

Thats exactly what Karl Popper says. We should listen to them, aslong as society is strong enough to defend a tolerant society against intolerance. The question is: When do we reach the point where the defence starts to break? You could argue that that point is reached when terrorists storm the capitol. I don't know if we reached that point already. What I do know: If we wait for too long, we reach a state of no retu…

I’m so glad people like Karl Popper didn’t write the constitution.

Re: IPFS Support in Brave

#403

Post by always_learning » Wed, Jan 20, 2021, 3:29 PM UTC

Once they ship Multi-Account Containers i am switching. Firefox have already annoyed me with the "more than just de-platforming" nonsense

Re: IPFS Support in Brave

#404

Post by apexalpha » Wed, Jan 20, 2021, 3:31 PM UTC

autocorr wrote: post #175

rmm wrote: 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 usually just message myself on WhatsApp.

I also remember a popular extension that could do this, PushBullets

Re: IPFS Support in Brave

#405

Post by ernesth » Wed, Jan 20, 2021, 3:43 PM UTC

daemoens wrote: post #271

max_ wrote: post #107

Earlier quoted context omitted.

The first time I actually leant how to use this I was like wow. It was the only reason why I left chrome for firefox

Chrome got it a couple months back fyi

Really? How do you enable it?

Re: IPFS Support in Brave

#406

Post by zepto » Wed, Jan 20, 2021, 3:57 PM UTC

SulfurHexaFluri wrote: post #301

zepto wrote: post #275

Earlier quoted context omitted.

It was easy for Google to deliver Chrome when the biggest work was done by Safari team... It was easy for Apple to deliver Safari, when biggest work was done by Konqueror team...

The fork from blink was so long ago its pretty much irrelevant now. Google likely spends more dev hours on it than apple does on webkit these days.

True, but not relevant to the point, which is that both Apple and Google built their browsers on top of someone else’s work just as Brave is doing.

It took years of shipping Chrome before Google actually forked Blink.

Re: IPFS Support in Brave

#407

Post by dx87 » Wed, Jan 20, 2021, 3:58 PM UTC

nvr219 wrote: post #105

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

What's that supposed to mean or have to do with this topic at all

It means that Brave is implementing protocols that help circumvent censorship, while the CEO of Mozilla is saying that current censorship doesn't go far enough.

Re: IPFS Support in Brave

#408

Post by ayewo » Wed, Jan 20, 2021, 4:06 PM UTC

always_learning wrote: post #403

Once they ship Multi-Account Containers i am switching. Firefox have already annoyed me with the "more than just de-platforming" nonsense

This is the first time I’m hearing about this blog post: https://blog.mozilla.org/blog/2021/01/08/we-need-more-than-d...

I use Firefox but don’t receive their newsletter, follow their social accounts or any kind of communication, and I’m guessing this is true for a lot of FF users, so I’m wondering how you learned of it?

Did Mozilla try to shove their brand of politics down your throat in-browser? Via the new tab or a similar mechanism?

If not, I don’t think its enough—at least for me—to jump ship.

Stackoverflow did the same by injecting the immediate past CEO’s brand of politics into the side bar. Even with push back from the community, they didn’t stop or apologize.

In spite of their actions, people still derive value from the large cache of answers that is their Q&A product to get work done. Lots of people will keep going back to use their product, even if they disagree politically.

Re: IPFS Support in Brave

#409

Post by contravariant » Wed, Jan 20, 2021, 4:08 PM UTC

Why do they insist it's a URI when URIs and URLs use the same syntax and the provided URI actually defines a means to retrieve the content? The censorship aspect is a red herring as both URLs and URIs carry the same meaning and only require the host to be a registered name, regardless of what registry this is (i.e. DNS is not a requirement), and in fact doesn't have to be a literal host.

Re: IPFS Support in Brave

#410

Post by Guidii » Wed, Jan 20, 2021, 4:30 PM UTC

zepto wrote: post #275

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 was easy for Google to deliver Chrome when the biggest work was done by Safari team... It was easy for Apple to deliver Safari, when biggest work was done by Konqueror team...

Google had contributed significantly to WebKit before the fork.

https://blog.bitergia.com/2013/02/06/report-on-the-activity-...