lime

this reads like a teenager wrote it

The Incredible Machine! the original Rube Goldberg game. me and my friends played the shit out of it in the 90s. a few years ago i decided to give it a google and i found out that not only were there an expansion i hadn't heard of, there were five other games in the series.

i don't know about "cross" :P it's a bit-for-bit reimplementation of Elite 2. i loved that game as a kid and pioneer is a great version of it.

yeah one thing we couldn't fix before losing interest was eventual consistency and authority. files would sort of flicker in and out while state was being propagated. i dread to think what kind of bandwidth use that thing would have when sharing large files.

buildings with upward-facing spotlights, especially single-family homes with façade lights. it's like nobody cares about light pollution.

it was nothing official, just a toy file sharing thing using the chord dht algorithm. it consisted of a single binary that you fed with a directory and the IP of an extant member, and it would sync everything on the network into that directory.

no edge cases handled, so the 90% remained.

sure, do that. and good luck with this, i did something similar for a project once and as usual its those last 5% that are going to cost you 90% of the time.

i've seen something like this before, where the kernel holds the file handle open for the process so that it thinks the file is still there. i think it's related to how the program closes the file but i don't remember the details. restarting qbittorent will most likely fix it.

your reaction makes me more confident that this may turn into something interesting :)

i take it then that files must have some ownership information associated with them, to distinguish the author from a relay node? or is that just a private key.

i'm interested in the dynamic linking, what mechanism is used to stop situations like left-pad or the pypi incident where a file is removed replaced with a malicious alternative?

if I'm reading this right, it's a bit like ipfs+dht. is this a content-addressable system?

anyway, you should probably have demos of

• large files (like a Linux disk image), to demonstrate consistency in transfer.
• Video stream, to demonstrate performance and low latency.
• multiple files shared with many peers at once, to demonstrate scalability
• sharing with low bandwidth and high latency, to demonstrate possible mobile use cases.

thoughts:

• the logo is very close to wireguard's.
• if the data is stored on peers, that means there must always be people with free storage online for it to work? how much storage is needed? is that data in plaintext? could a bad actor push illegal content to peers without them knowing?

also, please convert the whitepaper to a format that is actually readable. rtf? really?

the amount of dust under that throne...