Me: Computer, please install this program

Computer: No

Me: what

Computer: that program is dangerous

Me: why is it dangerous? It's a text editor.

Computer: Exactly! It can write FILES! To your HARD DRIVE! Do you understand how INSANELY DANGEROUS that is? Files! Just anywhere! Brrrrr. Don't thank me, I'm just doing my job. Keeping you safe.

Me: download it anyway, please. I want to edit files.

Computer: I'm reporting you for this. You are a menace to society. Files. For shame.


Me: What should I be doing instead of files?

Computer: Glad you asked! It's 2020. You should be spinning up a Kubernetes of Dockers on your public cloud each of which is a Github which send JSON messages over HTTP3 to the microservice host on your Virtualbox private cloud which is running a whole bunch more Dockers each of which is a Node.js which is pulling dependencies from

Me: files seemed a bit simpler than that


Context: attempting to install Timimi on Chromium Edge

Spoiler: Edge DOES NOT LIKE DOWNLOAD, and thinks I am probably a cyber-criminal doing cyber-crime.

I just... I just want to be able to save a web page that I've loaded from my local filesystem. Because it's mine, see, because I loaded it from my home directory.

Computer says BIG NOPE.

I don't think today's web browser developers have ever seen an actual file system.

Maybe using 'DNS name' as the unit of security compartmentalisation for the Web isn't such a sensible idea when pocket home computers can be terabytes of data.

@natecull They also assume all users need to be protected from themselves and should only install stuff from their curated app store.


i don't know how easy it is to do on windows but....

personally i always just run #tiddlywiki on nodejs now
(which basically treats the tiddlywiki as a web interface and manages the files 'server side')

in practice it functions nearly the same, the only part of the tiddlywiki that isn't customisable via its own data files is boot.js

@natecull oh dear, sane & easy tiddlywiki persistence 😑

@moonman @natecull I used to work with Jeff Darcy, who was a big believer in files. Actually, his position was a little more sophisticated: he thought that the rush to beyond-POSIX paradigms was throwing the baby with the bathwater. The problem is of course the one of performance and scalability. So, his thesis was that there wasn't anything unattaibale about a scalable and distributed POSIX filesystem, just everyone who hacked in the area wasn't smart enough and persistent enough to complete the task. Jeff's vehicle of choice was Gluster, primarily because it allowed to substitute key parts of the implementation using a VFS-like stacking. Realizing that existing Gluster sucked balls, Jeff set out to write his system as a new Gluster core, called "NSR" for New Style Replication. This continued for a bit until we bought Ceph. Seeing the sign on the wall, Jeff took his toys to Facebook. So far, the reliable, distributed, and performant POSIX filesystem remains a "pick 2 out of 3" kind of thing.

@pro @moonman

I think I could learn to love a filesystem replacement which was something like JSON objects (though it would probably need extensions for binary blobs). But it would be neat if we could have extremely tiny 'files', and files which had dictionary structure, and the whole things could be recursively nested.

@natecull have you seen that systemd wants to get rid of /etc/passwd and /etc/shadow because it's "too inefficient" to have systemd and two files on your computer

@ben @natecull
"So, for the simple act of logging in, three mechanisms are required (systemd, /etc/shadow, /etc/passwd). This is inefficient"

"all information will be placed in a cryptographically signed JSON record for each user"

What even is critical thinking

@ben @natecull I feel like this would be a clever design if there hadn’t been 30 years Linux development based on the old paradigm. Like does Systemd think it’s Apple and can just shift everyone to a new FS every release cycle??

@NightRose @natecull the proposed system is only more efficient (assuming each file on the system in addition to systemd adds a constant amount of "inefficient") if the system has exactly one user

@ben @natecull true, but I was thinking more of the supposed benefits in terms of the security and portability.

@NightRose @ben

(reading )

Good.... lord.

They're proposing to mangle everyone's user directories?

This is really nasty. How can I avoid getting this crap pushed to my home system? What distribution do I need to switch to to avoid any more future systemd nightmares?

@natecull Every time I think about using k8s my brain is like AAAAH AAAH BUT DOCKER IS SO SIMPLE WHY DID THEY MAKE IT SO COMPLICATED AAAH!!!! and I run screaming :) Also node seems cool except they seem to INSIST on shooting themselves in the foot with every bullet the Perl, Python, and Ruby communities shot themselves in the foot with 20 years ago and got better :)

@feoh oh no! what are the things that Node have done wrong?

@feoh the answer to "why make everything so complicated" is of course, "because Google won't fund any technology that can't handle a billion nodes, and if you're running a billion nodes the complexity pays off after the first million or so"

if you're trying to run one node, the complexity.... maybe doesn't pay off.

@natecull I think 'done wrong' is an oversimplification, but, I mean, look at the entire leftpad() fiasco as a for-instnace. One person de-publishing their work brought large chunks of the node.js ecosystem crashing down around its ears, and then there's the huge issue with malware in the NPM package registry... The list goes on.

@natecull Me: five different companies now have my credit card information


because granting write permission for one folder on your hard drive to a web page located inside that folder definitely totally logically implies granting transitive read permission to all files on your hard drive to all DNS domains everywhere on the Internet, and there is absolutely no way to build software where this does not occur.

@natecull http(3) - why no message broker. Nice handling with async, "less overhead", easier scheduling ....

Sign in to participate in the conversation

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!