IPFS Support in Brave • Hacker News Board

Re: IPFS Support in Brave

#411

Post by toyg » Wed, Jan 20, 2021, 4:33 PM UTC

xevrem wrote: post #373

input_sh wrote: post #355

Earlier quoted context omitted.

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

tab groups are not equivalent to containers. its more like Vivaldi's tab stacks or FF's Tree Tabs. With groups there are no inherent additional security mechanisms in place to prevent cross-group contamination/access. i.e., two different tab groups can access the same site data. containers however are completely isolated from each other. i.e., two different containers have completely different sets of site data.

> no inherent additional security mechanisms in place to prevent cross-group contamination/access

Are you saying the biggest advertiser on the planet likely doesn't want to add functionality that could potentially hinder tracking for advertising purposes...?

I am shocked, shocked and appalled. /s

Re: IPFS Support in Brave

#412

Post by the-dude » Wed, Jan 20, 2021, 4:42 PM UTC

aloisdg wrote: post #365

feross wrote: post #170

Earlier quoted context omitted.

Also, they integrate my WebTorrent project ( https://webtorrent.io ) so that .torrent files and magnet: links just work out-of-the-box. https://support.brave.com/hc/en-us/articles/360035025231-Wha...

Opera used to support torrents out of the box back in 2006. Good old days.

Not only was Opera released for Linux, they even released it for FreeBSD.

Re: IPFS Support in Brave

#413

Post by mikewhy » Wed, Jan 20, 2021, 4:58 PM UTC

mikece wrote: post #69

jonathansampson wrote: post #66

Earlier quoted context omitted.

Not a 1-to-1 parity at this time, but Brave offers parallel profiles. You can have one running personal interests, while the other has professional interests. Each profile is able to host a unique session for Facebook, etc. Brave already prohibits cookie and data bleed-over from one domain to another.

That creates a new window per Profile as opposed to just one window with a bunch of tabs, all conceivably in using their own Container, right?

How do you juggle multiple facebook / google / anything accounts in that sort of system?

Re: IPFS Support in Brave

#414

Post by 3395810 » Wed, Jan 20, 2021, 5:05 PM UTC

jonathansampson wrote: post #262

shuringai wrote: post #229

Earlier quoted context omitted.

and in return, brave replaces your urls with their affilate links. no thanks i'll took the hassle to open tor browser on an ipfs client

You're referring to a bug from June of 2020, which was patched within a couple days of discovery, IIRC. An issue which had no privacy or security impact. Details in our blog on the subject: https://brave.com/referral-codes-in-suggested-sites/ . Happy to answer any questions you may have.

It doesn't sound like a bug. It sounds like a feature that was removed when people noticed.

Re: IPFS Support in Brave

#415

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

Guidii wrote: post #410

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

Google had contributed significantly to WebKit before the fork. https://blog.bitergia.com/2013/02/06/report-on-the-activity-...

Are you suggesting that are things that Brave should be submitting pull requests for? If so, what?

Re: IPFS Support in Brave

#416

Post by babypuncher » Wed, Jan 20, 2021, 6:02 PM UTC

realdense wrote: post #190

waynesonfire wrote: post #177

Earlier quoted context omitted.

why would mozilla pay to add a fad technology or take on the tech debt?

Some of us believe that the client-server model has led us to the current situation, ruled by internet giants. A future where people are less reliant on giants is within our reach, the biggest hurdle is making it available to the masses. Hopefully uptake by non-mainstream browsers like Brave will increase the exposure, attract developers, increase the network and get us closer to having IPFS, Hypercore or some other…

The biggest hurdle is convincing the masses that your way is better than the current way.

I don't think that is ever going to happen.

Re: IPFS Support in Brave

#417

Post by morlockabove » Wed, Jan 20, 2021, 7:00 PM UTC

uniqueid wrote: post #354

kortilla wrote: post #347

Earlier quoted context omitted.

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

A lot of it is cynisism about people complaining about bad actors. The sorts of people who would build an anti-censorship tool are likely to be motivated, at least partly, be disdain for the censors of the day.

'Oh, now you want thoughtful dialogue, and a discussion. And then, when the reins of power are installed and your ilk have taken them, you'll be sneering as you kick me out.' - Something like that is a relatively common sentiment. Assuage this sentiment, and you might succeed.

Re: IPFS Support in Brave

#418

Post by pseudalopex » Wed, Jan 20, 2021, 7:42 PM UTC

lern_too_spel wrote: post #295

pseudalopex wrote: post #280

Earlier quoted context omitted.

Maybe they use Windows or Linux.

Chrome's "Recent Tabs" works like this across platforms. It is a feature I miss in Firefox. They have both recently put existing tabs in the omnibox suggestions, which is a huge quality of life improvement.

Firefox calls it synced tabs.

Re: IPFS Support in Brave

#419

Post by nklmilojevic » Wed, Jan 20, 2021, 7:54 PM UTC

BrendanEich wrote: post #165

paride5745 wrote: post #137

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.

What about full iOS sync? That is the one thing that keeps me from switching to it fully (history sync in particular). Thanks!

Re: IPFS Support in Brave

#420

Post by kubanczyk » Wed, Jan 20, 2021, 8:29 PM UTC

rzzzt wrote: post #93

kubanczyk wrote: post #53

Earlier quoted context omitted.

I'd like to take a look at say ~10 self-hosted sites. How can I get to them? Honest question.

Start with personal pages listed at https://userlist.beakerbrowser.com/ and go from there.

One more question... How am I supposed to come up with that list? I was googling extensively and skimmed through both Beaker's docs and Hyper FAQ. They are friendly towards creators, but I didn't see a word about exploring self-published stuff.