Some of the best stuff in the world looks like it’s 20 years past a prime that isn’t, because they’re truly good eternal.
I write English / Escribo en Español.
Vidya / videojuegos. Internet. Cats / Gatos. Pizza. Nap / Siesta.
This user’s posts under CC-BY-NC-SA license. Ask me if you need a different permission.
Some of the best stuff in the world looks like it’s 20 years past a prime that isn’t, because they’re truly good eternal.
IDK how easy it still is these days.
[
, tbh. ] install xnest
Yeah definitively sounds like even more support for Rust and/or Python in this sense.
Languages
C.
Frameworks
C.
That said, Python and Rust are great for setting up “starting up” / “small task” apps and growing up from there.
Next up!
ICANN approves use of .awesome-selfhosted
domain for your network
a curse upon these distros
It’s not the distros, it’s Flathub who provides those warnings.
Think about it, do you really want to have X11 going forward the next decades?
If the alternative is a new system that literally does nothing? Sure!
Want to present a menu for windows? Wayland: “lol, do it yourself”.
Want to position a window? Wayland: “lol, do it yourself”.
Want to remember that a window has a position? Wayland: “lol, do it yourself”.
Want to add a global keyboard shortcut? Wayland: “AAAAHAHAHAHAHAHAHHAHAHAHAHAHAHA!”
X11 may be old and whatever you want, but it works and it’s battle-tested. Wayland can’t even launch a full desktop session in my machine, which is even less than the failure Pulseaudio was back in its day and that’s saying something. And even if it did somehow launch, I probably would not be able to use anything serious like a media player or multiple workspaces on it.
February this year, and the iGPU of my machine (Intel 915 driver).
I mean yes, how exactly would you want the web to work?
Text and images and hyperlinks; maybe audio and video if you’re lucky and you can prove you can be trusted. No such thing as scripting, or if it’s allowed, only in a limited manner with no such thing as “eval” and obfuscation and no ability to add or delete nodes from the DOM (or if it’s allowed, those nodes must reflect under View Source / CTRL+U). No such things as loading a javascript audioplayer that tries to mix 123456 weird sources, just link me the .m3u direct to the audio stream’s .mp3 file, or even better an .opus.
Definitively no DRM.
If any such thing as GPU access is provided it should be to deposit data, not to run code.
It’s not dead there either, although I’d make the argument that X11 as a project is “mature” or “finalized”, it doesn’t really need hyperactive development like the tiktok children are used to.
(There are very good arguments that a new software stack was needed, but I’d expect the result to at least do something; ATM Wayland is little more than literally a “everyone else do my work for me” project)
I ask for some method that prevents the file to even be copied through a disk clone
Oh that’s quite simple! Just don’t have the files on the first disk in the first place. Make them a remote mount from a server, for example via sshfs, webdav, etc. Heck, even ftp if it comes down to it. That way, even though you can clone the disks, you can not get to the files if you don’t also have the full authentication requirements for the remote server (such as a password).
At a conceptual level, you can’t do anything via root
to prevent someone who clones the disk from… well, cloning the disk. Having physical access to a disk is a much higher level of access than even root, so if what you are looking for is for your content to not be cloned, you need to fortify physical access to the device.
alias run0=sudo
(not really; I’d rather not introduce an alias or any sort of symbolic behaviour that would teach me to expect that systemd crap is available on a system. The less you rely on it, the better)
lol, Wayland can’t even start a desktop session on my machine, whereas X11 has worked without issues since 2009 (the last time I ever had to edit xorg.conf).
Sure sounds like X11 is the one who’s “dead” around here!
To be fair, the fact that browsers are allowed to do so much that this warning has to be shown is more an indictment on the current state of browsers (which at this point are almost like installing VMWare and a virtual machine on your computer!) than on something something Firefox or something something Flatpak.
Yeah I’ve heard about punycode. Personally, I’m well against it because it puts down non-MURRICAN English domain names as second-class citizens on the internet. If I have a website about Copiapó, a perfectly legal town, there’s no good reason why the domain name should not be copiapó.cl
rather than copiap-xcwhngoingohi4oleleiyho42yt4ptg4ht4.cl
, making it look “suspect” and “malware-y”.
There were quite some complains back in the time about Firefox choosing not to “flag” internationalized names as potentially dangerous, and pretty much all those complaints that I know of likely came from English speakers who simply can’t understand other countries in the world even can have different alphabets.
And don’t get me started on TLS certificates in local networks…
I hate this and the fact that modern platforms seem to require TLS even if you’re serving localhost, so much.
I’ve taken to using .here
(or .aqui
, “here” in Español, much harder to match outside) as alternatives until something better comes up.
Ideally I’d use .aquí
, correctly with the diacritic, but DNS doesn’t seem to support even the basics of Unicode in 2024.
64-bit IPv5
64-bit IP would be IPv8, not IPv5.
Nice try, fed.