I don’t know about the file metaphor, but idea of a stream of bytes is timeless and essential. If you have that, you might as well call it a file. “Library items” (what, books?) are practically the same thing. In a filing cabinet or on a shelf, it doesn’t matter.

Realizing that EarthFS should use files (rather than “entries”) was a big step forward in its development. Credit to my friend Dan for his facial micro-expression (best term ever, lol) getting me on the right path.

So, MongoDB with a file URL? (Hint: that’s you could implement the MVP of this, and if you use a URL you can even reference user files they don’t store locally)

And file permissions are dead? Because nobody has kids that use the same desktop they do?

This is (from a technical standpoint) the silliest goddamn thing I’ve ever heard.

From a product standpoint, you could probably pitch and get a few M. Why the fuck not.

Yeah, this particularly vehement dismissal pissed me off too. Even if it’s not me or the LTP guy, I hope someone can prove him wrong.

I’ve said that content addressing could be done in 30 lines of Python, but for some reason I’ve been working on it for two years, and I know this guy has been working on his project for a long time too.

Incidentally, I’ve given up on file permissions in EarthFS too. There are user permissions but they are repo-wide.