deadlyllama
Joined 10 years ago
Joined 10 years ago
Vultr, DigitalOcean, Linode, ... are long established VPS players.
I'm cheap and buy VPSes off deals on lowendtalk.com. e.g. my backups are on a VPS with 3TB disk, 2GB RAM, 1 vCPU, USD7/mo. I suspect your USD80/mo budget would stretch to something amazing, by comparison.
I was thinking of the server end of an ffmpeg-over-ip system bringing up a FUSE filesystem backed by something similar to your VFS-served-by-the-client. Combine that either with argument rewriting, or chrooting into the FUSE filesystem.
As another commenter said, where's plan 9 when you need it? If you go the FUSE route there are existing 9P implementations for both server and FUSE client you can use.
Had you thought about using FUSE on the server side, rather than patching ffmpeg? Like a reverse sshfs? That avoids patching the ffmpeg binary, which allows usage of wierd and wonderful ffmpeg binaries with other people's patches.
I'd be interested in seeing how well it works with SBC GPUs - many have hardware decoding and encoding, and their vendors love to fork ffmpeg.
Pre Gmail I was on Exim. Now I'm on Postfix. I used the 123qwe.com tutorial as a starting point.
The real problems are (1) family members just want Gmail and (2) I have to maintain an email system.
They had a fairly smart UI for following links. They would appear as footnotes and IIRC you could just hit reply, type the footnote number, and then send.
And yes, as others have said, instead we got the modern web, with (for example) web based word processors requiring orders of magnitude more compute power than a desktop of the early Java era.
Over two decades ago I was programming a Foxboro PLC in their SALL language, which was compiled down to C. Variables and control structures! And you could hack the C if you wanted your state transitions to go faster.