lime

mozilla takes donations, but they don't fund Firefox development with that money. that's usually what people have against it.

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.

tariffs

my dude, just seeing the text is too much effort.

me, watching a friend play a game (that i play) for the first time

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?

i mean, that is the difference between interpreted and compiled.

if the container doesn't work though, that means it is broken and should be fixed. the point of them is literally to be plug-n-play. that would be like distributing a go binary with a segfault in main.

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?

that's posturing if anything. if you're an experienced developer it takes fully 10 minutes with either system. and if you're not interested in modifying it, just use a container image.

the only case where i would agree with you is when i have to modify LD_LIBRARY_PATH to get things to run...

such a strange interpretation. i've been working in go for over 10 years now, and i love it. but the notion that you can "just find the same program but built in a different language" doesn't make sense at all.

like, if you're annoyed with pandoc being written in haskell and clogging up your system dependencies, you can't just "find another pandoc". there's nothing like it. same thing with curl, or xonsh, or thingsboard.

such a weird take.