No problema.

Hicimos llorar y retirarse al tal “Messías”, we made him cry and retire. Dos veces. Lo humillamos y lo hicimos un meme. Podemos hacerlo de nuevo. Yes we can.

Mentira. Aposté Chile 0-4 Argentina en la oficina.

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.

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)

La suscripción por el canal de la cuneta cuesta cero, wink wink.

Y sólo por si acaso, ten algún Software Libre como fallback. Hay varias alternativas a los productos servicios de Adobe.

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.

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.

crypto based

well, there goes my interest.

64-bit IPv5

64-bit IP would be IPv8, not IPv5.

Not a big deal. We’re projected to run out of years by 2000 and then the world will end.

No tengo ni que ir al artículo para adivinar:

¿Moreira chupando pico(rocos) y lamiendo pescados minus…culos?

I felt dirty!

“Senpai, route me like one of your French ISPs”

128 bits basically gives one ip4 address space to each square meter of earth.

That sounds like terminal stage capitalism to me. Why would we want every tree in the Amazons to be cybergorized with its own IP? I don’t know Rick, 64 kbits bits ought to be enough for everybody, and I’m already risking it.

IPv6 is unfortunately not six bytes, no. For some weird, ass-backwards reason.

Boy do we like it!

That’s what they thought for IPv4… and for 2-year digits… and for…

1.1.1.1? :p

SQL uses it but yeah, not programming language :p.

I was on mobile so I didn’t have a .XCompose available to type ≠.

That’s how it starts. Mozilla itself is maybe not hindered on its mission, but the people who depend on them are: the extension was blocked, and there is no official way that I know of to add third-party extension repositories to Mozilla. And sure, the more important part of the problem is you cede just one bit, but the authoritarians won’t stop. They know now Mozilla will spread their legs so they’ll ask more and more, and Mozilla will for sure choose to bend over for them than to act for the people they were supposed to be fighting for.

The fun thing is that, C++ being C++, this is actually an std::overflow_error…