That's how we ended up with the old universe. It started out with dinosaurs and dungeons and we ended up with menial office jobs.
smpl
Random? I must be the only one left who believes in a deterministic universe ruled by cause and effect... and lizard people - big big lizard people on Mars.
At least what they ended up doing was not some crypto ponzi scheme.
Written from Librewolf, because I've had enough.
I just want to archive content, but if one would want such a thing I think the format to go for is WARC. As far as I understand it record the network requests, but I'm not sure as I've got no experience with the format at all. That way it would be possible to keep the original javascript intact and with a little manipulation of network requests to replay the original site.
It saves the rendered page. It also has a built-in rough DOM editor so that you can edit the document before saving. The way I have it set up it up is to remove all javascript from pages.
It's beautiful!
I archive with the WebScrapBook extension to htz which is also a zip based format. I open it with firefox's built in method to open jar files like this: jar:file://${file}!/index.html
The fact that it is a zip based format makes it futureproof. I could as well unzip it and open it with any browser. You could probably open the maff files the same way, but I don't think it is standardized to have an index.html file like htz.
AFAIK WARC is the only standard way of archiving webpages.
My guess would also be that most enterprises prefer Ada over Rust, because Rust lack standardisation. Sometimes you need to do unsafe things though and your billion dollar rocket explode.
guess
The Six Million Dollar Mon?
If the mail is sent unencrypted the admin can read it. What I have is a script that encrypt incoming e-mail with the users key, so that they are stored encrypted on the harddrive. That at least protect against an intruder reading past e-mails. I use a Perl script written by Mike Cardwell for that.
Another service you might like to have for your users is WKD/WKS, so that senders clients can automatically fetch the public key for your users.
It's easy to overlook with the omnipresent internet, but self-hosting doesn't require internet. You could host for your fellow students on the local network. If that's also against the Wifi rules you can either ignore that stupid rule or set up your own god damn wifi with hostapd on your machine and let students connect directly to it. It's probably best to use a machine dedicated to the task for security reasons as you wouldn't want curious students to accidentally erase your homework. I wouldn't use containers or VMs for any of this, I'd just use bare metal like in the good ol' days. You could also, without having to worry, give people shell accounts because it's a closed network. The options are endless without all the worries of hosting on the internet.
It'll be easier than running uncracked games. It's difficult to say how well your games will run in general.