181–190 of 249 posts
Earlier quoted context omitted.
Are you talking implementing IPFS on the browser level? Is there public code yet?
See https://github.com/ipfs/ipfs.js It's coming along, not fully functional yet but you can watch its progress (or contribute code :D ) at https://github.com/ipfs/node-ipfs
--- When neocitieslogo.svg is added to my IPFS node, it gets a new name: QmXGTaGWTT1uUtfSb2sBAvArMEVLK4rQEcQg5bv7wwdzwU. That name is actually a cryptographic hash, which has been computed from the contents of that file. That hash is guaranteed by cryptography to always only represent the contents of that file. ---
And opened a reddit/eli5 question, just to understand "if we can use a hash to identify content uniquely?" here: https://redd.it/3k8g51
Can anybody elaborate and lighten me up a bit?
I just couldn't digest all, after I read this entence in the description: --- When neocitieslogo.svg is added to my IPFS node, it gets a new name: QmXGTaGWTT1uUtfSb2sBAvArMEVLK4rQEcQg5bv7wwdzwU. That name is actually a cryptographic hash, which has been computed from the contents of that file. That hash is guaranteed by cryptography to always only represent the contents of that file. --- And opened a reddit/eli5 ques…
Kidding aside, the answers given on Reddit 20 minutes before your question was posted here suffice.
Just to point out -- hypertext systems prior to the web almost universally expected permanent stable addresses (and this was, for instance, required by the various Xanadu specs). Enquire (Tim Berners-Lee's immediate predecessor to the Web) had permanent stable addresses, too. The web didn't have permanent stable addresses because the web was a hack, intended as a way to explain Enquire to people who didn't have a bac…
> (Let the entire existence of the Web, with its myriad flaws, be a lesson to you: your crappiest demo may well become the thing you're known for twenty-five years later, so make sure your crappiest demo doesn't suck as bad as the Web does.) The web is amazing, and you are using it right now. It has flaws, but so does anything that achieves success at the level the Web has. How many technologies have a direct impact…
I just couldn't digest all, after I read this entence in the description: --- When neocitieslogo.svg is added to my IPFS node, it gets a new name: QmXGTaGWTT1uUtfSb2sBAvArMEVLK4rQEcQg5bv7wwdzwU. That name is actually a cryptographic hash, which has been computed from the contents of that file. That hash is guaranteed by cryptography to always only represent the contents of that file. --- And opened a reddit/eli5 ques…
There is a function that will guarantee to give you a unique 'hash' for every input value, and that is the identity function. Be sure to use a differently subscripted function for every input size though, as the fixed-length property must be satisfied. Kidding aside, the answers given on Reddit 20 minutes before your question was posted here suffice.
This reminds me of a feature I sorely miss on my blog (and almost every other blog I visit!) which is for the blogging engine to automatically take a snap-shop of webpages you link to and let users read the cached version at will. If I link to a page and it goes down, or the content changes, it in a way changes the content of my blog too - in an unwanted way that is!
A plugin that makes archive.org and archive.today save a snapshot would be ace. I would give (measly, sorry) 20$ if someone goes to crowdfund this as wordpress plugin.
https://www.reddit.com/r/alphaandbetausers/comments/3j702x/c...
This sounded like many of the bitcoin projects, specially filecoin and upon reading further I came to know it is by the same guys. Similar projects have been in development for past few years such as https://github.com/feross/webtorrent and zeronet This has same problems as the bitcoin infrastructure though: 1. It is unscalable. A page built on IPFS receiving huge inflow of comments would generate many diffs quickly…
As for your first point, you should really first learn more about how IPFS handles content addressing. If you look at section 3.5 the paper[1], you see that a IPFS object consists of a free-form data field, and an arbitrary amount of links to other IPFS objects. This is a very flexible format that allows for caching. You talk about a page with comments. You could (this is an example) create three 'models': a Page, a…
The thing from bitcoin is 51% attack where majority of nodes collude to provide the wrong data(they might not be malicious but just serving old version of a data). This can only be prevented by time-stamping in slow scenarios.
In case of neocities, a central server is giving you a hash that the nodes would provide you the data for, but without a central management how does IPFS associate correct file to the correct hash?
If it only works for a centralised scenario then it is similar to the http://peercdn.com project where instead of a server supplying content, your previous visitor browser cache is supplying the content through p2p webrtc and you save server bandwidth.
This reminds me of a feature I sorely miss on my blog (and almost every other blog I visit!) which is for the blogging engine to automatically take a snap-shop of webpages you link to and let users read the cached version at will. If I link to a page and it goes down, or the content changes, it in a way changes the content of my blog too - in an unwanted way that is!
This! I already thought about starting a project for a local browser proxy that builds an index of => $snapshotHash as I go. Maybe mixin readability and metadata like referrals. I find it quite belittling how browser vendors treat their history features in terms of archival.
Earlier quoted context omitted.
> Facebook's design is inherently centralized Not really. There's no reason you couldn't implement Facebook's core functionality with personal servers containing a profile at each node and a pub/sub (or even just pull) system connecting each node with its friends.
Actually, this is exactly what I'm looking for. I want to be able to control my photos and other content, and share that with family and friends. All data is encrypted and my server can be hosted anywhere (just as simple as setting up a WordPress instance). My own "news feed" are a combination of all of the other nodes I'm subscribed to. My problem with Disapora is that they push the "sign up to someone else's pod" r…
Earlier quoted context omitted.
> (Let the entire existence of the Web, with its myriad flaws, be a lesson to you: your crappiest demo may well become the thing you're known for twenty-five years later, so make sure your crappiest demo doesn't suck as bad as the Web does.) The web is amazing, and you are using it right now. It has flaws, but so does anything that achieves success at the level the Web has. How many technologies have a direct impact…
HTML/HTTP was an improvement over earlier concepts of bidirectional, centralized, reliable hypertext precisely because the links were one directional, hierarchy-free and unstable, and could be put anywhere. The servers belonging to distinct entities weren't coupled. The pages belonging to one entity weren't coupled. It ripped out a lot of politics and baked-in design decisions and let loose creative anarchy.
I still think Xanadu et al are interesting, but it's instructive to try to understand what the real trade-offs are, the most obvious one being one of shipping speed.