Our great sponsors
-
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
multi-account-containers
Firefox Multi-Account Containers lets you keep parts of your online life separated into color-coded tabs that preserve your privacy. Cookies are separated by container, allowing you to use the web with multiple identities or accounts simultaneously.
-
-
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
> The gateway could potentially also lie about the content it is serving you. In the future, Brave plans to verify content retrieved through gateways by using its CID.
Does anyone know why this was omitted? Verifying a hash should be quite simple. Was it done for performance, so the browser can fetch part of a CID-tagged bundle and display it immediately, without having to download the whole bundle?
> Both requests you make and content you serve are observable by network peers.
That is a deceptive way to say, "if you click the 'Enable IPFS' button then your computer will continually publish your browsing history to the world." And they make it too easy to enable. It's just a button below the address bar [0]. And the button has a deceptive name, "Enable IPFS". The browser can use IPFS through a gateway, so IPFS is already enabled.
Why would they choose such deception? If Brave was made by Google/FB, then the reason would be simple perverse incentives: the team members get paid more when more people use the product, even if it harms those people. Does Brave have degenerate company culture like Google & FB?
There are many important projects to improve privacy and reduce tracking and monitoring of user behavior on the network: DNS over HTTPS, TLS Encrypted SNI, blocking third-party cookies, proxy services (incorrectly called VPNs), anti-fingerprinting work in browsers, and mobile privacy features. Is there any work on making IPFS resistant to tracking? Right now, IPFS seems like a step backward for privacy.
> By default, Brave will load the URI being requested via a public HTTP gateway
> If IPFS is not yet configured, the user will have the IPFS page loaded through the gateway https://dweb.link. [0]
Fortunately, Brave shows the gateway URL in the browser address bar. This lets users know which company is tracking them. For Brave users (dweb.link users), this is Protocol Labs https://protocol.ai .
Protocol Labs is a VC-funded company in California. Since they're VC-funded, they will inevitably renege on all promises to users and commence monetizing their users' data. I predict that they will sell all logs to Acxiom/IPG [1] or to CloudFlare (after it enters the selling-user-data business).
[0] https://github.com/brave/brave-browser/issues/10220
[1] https://en.wikipedia.org/wiki/The_Interpublic_Group_of_Compa...
Anyone would like to try IPFS in Browser, you can use the IPFS Companion(https://github.com/ipfs-shipyard/ipfs-companion) and IPFS-Desktop(https://github.com/ipfs-shipyard/ipfs-desktop). IPFS Companion supports many mainstream browsers.
I agree. As someone who works with numerous customer environments this extension is critical for my productivity. Having a different profile (ie Chrome style) is nowhere close.
If the container re-ordering patch[0] would be implemented it would be perfect, but it seems to be stuck in limbo.
If Brave implemented this and did it right (with sorting & reordering) I would consider switching.
[0] https://github.com/mozilla/multi-account-containers/pull/160...
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`
[0] https://pinata.cloud/
[1] https://infura.io
[2] https://blog.cloudflare.com/distributed-web-gateway/
[3] https://github.com/ipfs-shipyard/ipfs-deploy
> IPFS, Hypercore or some other protocol available to the mainstream, whether that be in Firefox or by some other means
TIL about hypercore! Looks like an interesting concept based on append-only logs. It reminds me of this work being done at VMware: https://github.com/vmware/node-replication
There are several new and exciting decentralized web protocols. I am working on a tool to publish to all of them. Right now it publishes to IPFS and Hypercore, and will eventually serve signed plaintext so content can be shared to Scuttlebutt and Aether networks.
For example, this site is published using https://github.com/hyphacoop/api.distributed.press and it can be accessed over HTTP, IPFS, and Hypercore.
https://staging.compost.digital
[2] https://github.com/ipfs/go-ipfs/pull/7802
Basically, someone could copy paywalled content and distribute them on IPFS ?
https://github.com/victorb/ipfscrape