131–140 of 464 posts
Earlier quoted context omitted.
Uhm, no? https://vivaldi.com/source/
Only part of their source is available. > Of the three layers, only the UI layer is closed-source. ... The Vivaldi UI is truly what makes the browser unique. As such, it is our most valuable asset in terms of code. https://vivaldi.com/blog/vivaldi-browser-open-source/
I don’t know anything about IPFS and would like to know more. When I visit an HTTPS URL I see content and some authenticity (of the server, at least) tied with the transport mechanism. IPFS provides the content and a distributed transport. Does the protocol include authentication of the author? Is it up to the content author to include their own signature protocol outside of IPFS? [If you post an ipfs:// link claimin…
My understanding is that the integrity of the contents is assured due to the identifier being a hash of the content. From there I don't think it's really needed for a whole protocol to verify the author. Couldn't something as simple as a gpg signature be sufficient? If they signed the hash and gave it to you then it would be good
(‘hecturchi’s response hints at how IPFS achieves this, I think.)
Earlier quoted context omitted.
It is not particularly surprising considering that the founder of Brave was fired as Mozilla's CEO and replaced by the current one specifically because of politics.
> because of politics. Even more specifically because of his anti-LGBT politics.
His views do not impart themselves onto Brave of course, but I will stay with Firefox.
Earlier quoted context omitted.
It does :) Download Brave and navigate to the following URL for a quick demo: ipfs://bafybeiemxf5abjwjbikoz4mc3a3dla6ual3jsgpdr4cjr3oz3evfyavhwq/wiki/Vincent_van_Gogh.html
In my experience IPFS is only fast when you're using it through something like Cloudflare's IPFS proxy (which is basically a caching proxy). I haven't found IPFS to be actually usable any time I've tried running a node myself. Especially pinning anything beyond the most trivial of examples. Hoping to be proven wrong though.
For a start, newer versions of IPFS work much better, but the network still had a significant amount of older nodes making the experience worse for everyone. Luckily, this is changing as of late, it seems.
IPFS shines when it can take advantage of content proximity (i.e. in your LAN, in your node etc.) or when there are few providers for the content within reach, at which point it just works regardless of connectivity to the outside world.
In a general scenario, comparing IPFS-delivery speed with a CDN-backed website is not very fair. Might be slower but offers much more versatility.
It is not the first time that I have looked at IPFS and I still have a hard time understanding how the ecosystem is going to work. From my understanding, the file hash is basically the file URL, such that any change to the file content is a change to the file url as well. For hosting something like Wikipedia, how would one create pages that link to one another? And if indexes need to be created on top of the content,…
You can then link to files within the folder using relative links.
I guess this avoids having to have IPNS entries for every file?
Mozilla promised us Tor integration, IPFS integration and more private browsing by default. Brave delivered it all.
It is easier for Brave to deliver new features when the biggest work is done by Chrome team.
Do you think Mozilla will ever switch to chromium? It is the linux of the web - would be nice if they could finally focus and stop dressing up their dead horse.
Any plan to at least allow using other crypto platforms like coinbase?
Does IPFS actually work?
Earlier quoted context omitted.
>and that is better since it is easy to have an IPFS node running locally since it is quite efficient. No, it isn't.
Seconding this. Unless something's changed, my experience with the default Go daemon they provide was shock at how much resources it consumed in the background. It was something like 12% CPU usage while doing nothing at all for hours on end - I wasn't even accessing any ipfs content.
(Though on a Linux system I also modified the low water setting up to 1000 peers and the high water setting to 2000 peers)