ctOSLooks at the centralized points and peer discovery in Dat and IPFS.
void09yeah i actually read part of that :)
ctOSRead the rest. Look at the previously published article for info about uncensorable domains.
void09The Dat project also has a single-vendor dependency for DNS resolution as the project defaults to using Google DNS over HTTPS by default. - why ? :
ctOSvoid09: they want to use DNS over TLS instead of the regular unencrypted decentralized DNS architecture.
void09IPFS and Dat share a number of underlying similarities but address different problems. Both deduplicate content-addressed pieces of data and have a mechanism for searching for peers who have a specific piece of data. Both have implementations which work in modern Web browsers, as well as command line tools.
void09ipfs would need an extra application layer to do versioning and maybe .diff sync between peers, or just let it redownload the full file maybe.
void09but i still don't get one thing
void09the same files between two dat repositories/sites, cannot be cross-shared, right?
void09the same file*
void09you can't directlY enumerate an ipfs' peer pieces/files, right?
void09@aral that was from the article ctOS wrote https://www.ctrl.blog/entry/dweb-readiness-runet
ctOSvoid09: to be fair, only Dat really works on the web and only in one browser. IPFS jams everything from every source into one origin. It strips away almost all security layers of modern browser. ZeroNet has the same problems yet they encourages users to do PGP encryption within one shared origin. It's madness.
void09it's a feature, not a bug :P
void09designed to eliminate useless fragmentation of sources for data
void09what I thinik it lacks, and pretty much any p2p programs lacks this (correct me if i'm wrong), is some sort of peer sorting by a metric such as routing distance, or geographical proximity
void09especially useful in large swarms
void09I find myself in Europe, downloading from hosts in brazil, on a torrent with hundreds of seeds :\
ctOSIt’s quite useless for an application resembling the web with individual websites maintaining their own security contexts.
void09ok so the danger here being, anyone can see that your ip used/hosts a certain reouces on ipfs, right ?
ctOSvoid09: no. a webapp, say a chat app running on IPFS, share the same origin (localhost:8080) as any random other web page you read in your browser.
ctOSSo any random webpage can read your chats.
ctOSSecurity contexts on the web are [to varying degrees] isolated by origin/domain.
void09I never thought of that.. is it really possible with the current ipfs?
void09ok well, what can I say then. don't use it for chats :P