@adisonverlice nodds in agreement that #VPN doesn't "#vibe" as in having * huge red flags*…

• I'm not a fan of @mullvadnet either but at least they obviously do that they can to minimize having customer data at hand in the first place.

Personally, I'd rather shove some tamper-proof box inside a rack cabinet that has all the secret keys on a non-persistent #RAMdisk so as soon as anyone "fucks with it" it'll send an alert and reboot, loosing the keys in the process.

What I'm still missing is a custom #recovery that can actually do any useful stuff (especially full #backup).

My device has recovery as a #ramdisk in vendor_boot, and there are some prebuilt vendor_boot images with #twrp around, which I don't want to use directly because there's also an init-boot ramdisk in there that needs patching for root with #magisk ... and as far as I understood now, these ramdisks are userland only, using the shared #kernel from the boot partition, so it's unlikely a recovery built for #HyperOS1 (#Android 14, #Linux 5) will work with #HyperOS2 (Android 15, Linux 6).

What I *did* try nevertheless was modifying my vendor_boot using Magisk's #magiskboot utility, replacing ONLY the recovery ramdisk. It resulted in #bootloop trying to boot the normal system, so there seems to be something I still don't understand (I *thought* this ramdisk would only ever be loaded when booting to recovery).

For now, I'll live with the useless stock #Xiaomi recovery. Attempting to do my own build of twrp or orangefox really is too much hassle

@HoustonDog and yes, I remember those #WinPE #hacks with rramdisk.sys to make #Windows run from #RAMdisk.

• In fact, @OS1337 literally does that when booting by loading itself into #RAM...
  

The idea of using #ROM chips is to have something long-lasting that is designed to be read-only without mechanical parts and not trivial to fiddle with compared to #USB #flashdrives.

So yes, my mission goals for @OS1337 hasn't changed in that I want it to be a #useable #SSH #terminal on a #1440kB #FDD image and having the option to expand from there on...

• A #Ramdisk-only #Linux that allows one to easily connect to stuff and mount one's /home/ directory is a way to go - espechally when said drive is a fully-encrypted #Network-based #BlockStorage...

At the very least I want @OS1337 to support #dropbear as #SSH #client so one can use it as a amnesiaic, anti-forensics #RAMdisk - only SSH-#Terminal to connect to other machines.

Like a reinterpretation of classic terminals like the #VT520 series from DEC...

@xeraa @fuchsiii @puniko @linux_mclinuxface Case in point, #SSPL is an #AssholeLicense even more than #AGPLv3 because it's sole purpose is to commit #AssetDenial against #commercial users & #hosters.

It's worse than #GPLv3 because that one is lunacy in terms of #IP and espechally #Patents because it's solely ideologically motivated, but yeah...

IMHO everything under SSPL is #UnfreeSoftware in that it's #license terms are worse than a #SourceAvailable license as used by #Tarsnap because they are at least honest about the why...

I really hope not just #GAFAMs like #Amazon with #aws forked the pre-#Enshittification versions under #BSD and start publishing and maintaining these.

#Redis, like #Elastic and #MongoDB have chosen to kick everyone in the groin out of pettyness against commercial hosters, and I hope @Mastodon & @MastodonEngineering as well as @Gargron work hard to replace Redis with a real #FLOSS alternative like #RabbitMQ or even hetter, allow disabling a caching-DB in lieu of helping setup a #Ramdisk with a #PostgreSQL cache-DB on it.

@landley I'll propably have to gut functions out of toybox to get it where I want it to be, but then again the "#CORE" Version of OS/1337 will be very much barebones....

Just the essentials to get #Dropbear #Client to be able to #SSH into stuff, be able to make a #ramdisk and #wget / tiny-#curl everything else (i.e. a system image one could dd onto a HDD/SSD)...

Kinda like an old #netinstall #Floppy...

Ideally configureable to the point that I could also swap #dbclient for dropbear as #Server

@malin
Yeah, and #Chrome still uses #HDD #cache too, and a not-user-friendly way to change it. I did manage to though, and now happily lives on my #RAMdisk Makes a noticeable difference to
#performance !

@whitekiba I mean I don't look for computational efficiency....

OFC modern crypto needs a lot of processing power...

But I'd even consider doing a #ramdisk and making a script that #wget's #dropbear as a working hack...

Even if that makes it a sort-of "#netlive" [ #netinstaller meets #live #linux] workaround...

@PeterCxy @sigmasternchen yes and no:

Yes in that it'll require people to desolder stuff first.

No in that it's benefit is negigible considering that this attack vector will only apply to state-sponsored attackers and console hacking, so if someone has physical access to the PCB you're already f**ked.

Also you may want to instead use #encryption over #tmpfs if you want to use a #RAMdisk ...