"Geniuses"

Fixing that level of corruption/brain washing is now going to hurt bad.

All that to find a path to true or false.

I don't think this is a mistake, but something malicous clearly thought through.

But as I said, in my personal case, I have to account for my stress intolerance which is significant, which does not help narrowing down those type of issues. Then, I am probably not one of the right guys to figure out that, but I'll do tests here and there to see if I can get some pertinent info.

I suggest you do the same than me anyway: shutdown all apps, and disconnect your network cable.

For instance, I am self-hosted, that without DNS. The email designers were carefull to make the email system work without DNS, that with email addresses with IP literals: mailbox@[x.x.x.x] and mailbox@[ipv6:...] (and I guess once ipv4 is really gone, the ipv6: prefix will be dropped).

This is stronger thas SPF, since as soon as a IP literals in the envelope and the various "from" headers does not match the actually IP from the sending SMTP server, the email is dropped, not even going in spam.

If I send such email to gmail for instance... I get a 'missing a DNS PTR' record, go to hell. How, convenient, to send an email there, you must have bought a DNS domain, knowing perfectly that most registrars nowadays are gated by the web engines of the whatng cartel... which gogol, then gmail does belong to... how convenient, the crime is almost perfect, I don't put that on the account of incompetence, this is beyond that, we are in the realm of toxic malice.

I do presume now they know what they are doing, killing all small tech, or self-hosting is in their agenda of dominant internet corporation.

We have to eat the bullet, there is only one way out: restore noscript/basic HTML interop in "security" infrastructures (can still have a non-mandatory web app on top). And it will probably require super strong _technical_ regulations and expect the 'whatng cartel' to fight hard, because they won't like critical web sites not being web apps then forced to run on their massively complex web engines...

Don't forget, a few years back, most, if not all, online services were able to run on 1D or 2D (simple table) HTML documents.

I say that because I play some timing tight action games natively on elf(glibc)/linux. Let's take an example with one of the toughest: Silksong.

I was trying to beat lost lace, her timings were too tight and nearly at each try I was locked in some hardly humanly dodge-able pattern combination. I knew all of her patterns by heart after zillions of tries.

Then, I started to have strong suspicions: I closed all background apps, disconnected the network and try again... did beat her, first try, super ez, like she was transparent to me and slow, I could "read" her and react in time easily.

I am running a Zen2, 12 cores at ~4GHz... and native x11 with xorg, sooo... the main culprit seems to lie in game engine programming and then would not completely tied to wayland programming (don't worry, I am coding my own wayland compositor, so, I am going to move to wayland, well actually designing a 'binary layout' for a wayland compositor to be accurate).

I am now in a Silksong steel soul run, and you bet I'll keep this experience in mind, because when I watch video streams of other people fighting some bosses, I can cleary "read" their moves like it is "slower" and which seems much less "aggressive", but once I fight them on my system, nope, I get a much harder time at reading the boss patterns. The "closing all apps and disconnecting the network cable" did not change a thing here, because I am currently fighting "ez' bosses then I always manages to get rid of them before I get really used to their patterns again... we will see with later and harder bosses.

But this could be another [obvious] culprit: stress. I know I am very, VERY, sensitive to stress: it disrupts severely my mind and worse with very little of it. In other words, I would have "brain fog" while fighting a boss because of stress, and the time I did beat lost lace in one shot ez: I was "testing" something without the stress instead of actually trying to beat her... a abysmal difference.

mailbox@[x.x.x.x] and mailbox@[ipv6:...] (and probably without "ipv6" prefix once ipv4 is gone).

This is stronger than SPF since the second the IP of the sending SMTP server does not match the IP in the "from" headers and the envelope, the email is dropped, not even going into spam.

For instance, currently, if I send an email to a gmail slave, their parsers will ask for... a DNS PTR record, Oo "Geniuses" at work, or conveniently breaking all interop with small tech?

For instance, I am self-hosted and I don't pay for DNS since now, most registrars are gated by whatng cartel web engines.

Then, I have an email address with an IP literal (mailbox@[x.x.x.x] and mailbox@[ipv6:...]), this is stronger than SPF since the second the SMTP server IP does not match the IP literals from the email address, in the envelope and the headers, the email is dropped (not event spam).

Currently, the "geniuses" at gogol ask for a DNS PTR record when I tried to send an email to somebody on gmail. My ISP does provide a reverse DNS service... gated by whatng cartel web engines unfortunately.

All this is so much convenient: destruction of all small alternatives... yeah... how convenient...

Until govs and regulators understand they have to go technical to calm down those corporations, things will get worse and we will end up with compuserv and AOS all over again.

(I guess I am good for some dusting and thermal pasting)

That will avoid to be locked into a specific compiler (look at the cancer of gcc "extensions" and linux) and have to deal with compiler generated 'backdoors'.

In other words, on modern CPUs, the fact that such compilers (cproc/qbe is only one alternative, probably near "real-life") are orders of magnitude smaller, are _not_ written in one of the worst computer languages ever (c++), mean that gcc (and clang) is a problem for open source. That's why the people need _lean_ open source now.

Moving gcc to c++ was probably one of the worst mistakes in open source, ever. Basically the only reason I can see for this disaster would be to force gcc devs to deal with this brain damaged computer language to force gcc to have a 'real-life' support of it. Because some critical, for some users, software is c++ written (and that was a mistake in the first place).

That said, the real end game here, is a "wolrdwide standard CPU ISA" with very performant implementations, assembly written software (without abuse of a macro-preprocessor), probably with a set of very high languages interpreters written themselves in assembly. Currently, RISC-V is taking shape, slowly because the "market" is already "saturated" and state of the art production lines are hogged by IP locked ISAs (and mistakes _will_ be made which is going to slow it down even further). In this kind of realm, even ISO will have a hard time generating cycles of computer language syntax planned obsolescence.

Prefer, tinycc, cproc, scc, assembly.

First thing first, restore web sites in a solid security network infrastructure. Namely, noscript/basic HTML.