251–260 of 464 posts
Mozilla promised us Tor integration, IPFS integration and more private browsing by default. Brave delivered it all.
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
Earlier quoted context omitted.
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.
From what I remembered Firefox whitelisted ipfs:// links a long time ago, but you needed an extension (add-on) for it fully work. https://bugzilla.mozilla.org/show_bug.cgi?id=1354807
https://bugs.chromium.org/p/chromium/issues/detail?id=722567
They've also whitelisted ipfs:// links since August.
Earlier quoted context omitted.
I suspect so, but don't know the details of FPI in Firefox. We don't permit cookies and storage access by third-parties, while also blocking known bad-actors entirely. We also "farble" APIs to create noise for those who do have access. If there are any specific scenarios or questions you have in mind, I'd be happy to discuss further.
Would Brave's parallel profiles allow me to be signed in to 2 different AWS accounts? I've tried this in Multi-Account Containers for Firefox and SessionBox in Chrome, and they're both pretty buggy, e.g. the console's username menu indicates I'm in account "A", but I'm seeing resources listed from account "B", or EC2 will work fine but clicking over to ECS prompt me to sign in again.
Earlier quoted context omitted.
I suspect so, but don't know the details of FPI in Firefox. We don't permit cookies and storage access by third-parties, while also blocking known bad-actors entirely. We also "farble" APIs to create noise for those who do have access. If there are any specific scenarios or questions you have in mind, I'd be happy to discuss further.
> We also "farble" APIs to create noise for those who do have access Does this effectively do the same as the 'Canvasblocker' extension does for Firefox?
See also the Beaker peer-to-peer web browser. I love how much simpler it is to host websites, from the browser - the real read/write web!! I'm not affiliated with them in any way. https://beakerbrowser.com/ https://docs.beakerbrowser.com/faq#what-does-beaker-do-bette...
Opera used to have this capability (internal web server, read/write web) until it was gutted and turned into another chromium skin after V.12
Earlier quoted context omitted.
The type of people who are into decentralizing the internet are also usually against a single company (google) controlling the rendering engine of most users. If you're talking about typical user of the average web browser, they care about IPFS as much as they care about the rendering engine - i.e. not at all.
I am that person. I moved away from Brave because its still chrome/chromium based. I am also not confident in their "blockchain" advertising model and don't trust they are actually any less private with my data than chrome/chromium. It would be cool to see IPFS integrated and enabled by default on all browsers. I doubt Google would ever take the leap, but maybe Mozilla would. I also have doubt that Microsoft would bu…
I would love to hear more about your privacy concerns; we have excised quite a bit from Chromium. You can read about those changes [on GitHub](https://github.com/brave/brave-browser/wiki/Deviations-from-...). We also audit our network activity to make sure nothing ever slips out. You can read about our [desktop](https://brave.com/brave-tops-browser-first-run-network-traff...) and [iOS](https://brave.com/ios-browser-first-run/) audits on our blog.
Perhaps more of interest would be an independent, third-party review and comparison. Trinity College's School of Computer Science and Statistics did a comparative review of Chrome, Brave, Edge, Firefox, Yandex, and Safari. They found that Brave was the "most private" in terms of phoning home. You can [read their review online](https://www.scss.tcd.ie/Doug.Leith/pubs/browser_privacy.pdf).
Always happy to discuss any specific concerns you may have.
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.
https://github.com/brave/brave-browser/issues/2457
https://github.com/brave/brave-browser/issues/5761 (duplicate)