How does this differ from just, say, giving someone an HTML dump of a static site? I don't quite understand what this protocol offers.
How exactly is it peer-to-peer if it's essentially an offline, transfer via hardware?
The Sneakerweb
11–20 of 26 posts
Re: The Sneakerweb
#12[dead]
Re: The Sneakerweb
#13How does this differ from just, say, giving someone an HTML dump of a static site? I don't quite understand what this protocol offers. How exactly is it peer-to-peer if it's essentially an offline, transfer via hardware?
From what I can tell, you can basically take your USB drive of "websites" to your friend, and sync it with their local folder of "websites", and now you both have the most up to date versions of your combined group of "websites". (if your usb has Website A version 1 and Website B version 2, and you sync with someone who has Website A version 2 and Website C version 1, you'd both end up with Website A V2, Website B V2 and Website C V1)
The application also apparently has protections in place so you can't just create an updated version of someone else's website and distribute it the same way to impersonate them
Re: The Sneakerweb
#14How does this differ from just, say, giving someone an HTML dump of a static site? I don't quite understand what this protocol offers. How exactly is it peer-to-peer if it's essentially an offline, transfer via hardware?
From what I can tell, you can basically take your USB drive of "websites" to your friend, and sync it with their local folder of "websites", and now you both have the most up to date versions of your combined group of "websites". (if your usb has Website A version 1 and Website B version 2, and you sync with someone who has Website A version 2 and Website C version 1, you'd both end up with Website A V2, Website B V2…
I belive it also goes into the larger Wormblossom Willow project where there will be an online component, so that you can distribute stuff either online or via USB, building a sensorship-resistant protocol that works both online and offline.
Re: The Sneakerweb
#15How does this differ from just, say, giving someone an HTML dump of a static site? I don't quite understand what this protocol offers. How exactly is it peer-to-peer if it's essentially an offline, transfer via hardware?
From what I can tell, you can basically take your USB drive of "websites" to your friend, and sync it with their local folder of "websites", and now you both have the most up to date versions of your combined group of "websites". (if your usb has Website A version 1 and Website B version 2, and you sync with someone who has Website A version 2 and Website C version 1, you'd both end up with Website A V2, Website B V2…
Kind of like Usenet, but with web crap.
Re: The Sneakerweb
#16I thought this was going to be related to: https://en.wikipedia.org/wiki/Sneakernet
It is. Just with web tacked on to make it worse.
Re: The Sneakerweb
#17Nice, modern day samizdat. Looks simple enough to use. I wonder if there’s a Linux distro that includes tools like this. It’s not a bad idea.
No packages yet: https://repology.org/projects/?search=sneakerweb
Re: The Sneakerweb
#18Seems like a mobile app is needed for this. My phone has tons of storage that is unused and always with me.
Re: The Sneakerweb
#19It would be cool to add this as a tool in copyparty! I have had a few friends come over and copy files from my home server they want to use.
Re: The Sneakerweb
#20my cellphone has been named “sneakernet” for years. it’s a throwback to a time when it was faster to walk a zip disk across campus than it was to send it.
And if you use your cellphone as a USB mass storage device, it still is!