> Your server will be secure because it's obscure. But it's still very likely to become a target for autistic geniuses.
Ah, delving into the abyss of ancient servers, are we? Well, if there's one thing that tickles the fancy of the 'Atypical Geniuses Club,' it's a relic from the digital crypt. Count us in, presently inspecting the code armed with nothing but floppy disks and a dial-up connection!
Another question I have is: "If governments have nothing to hide (apparently we don’t so they shouldn’t, no ? They said to me they are my equal and truthful protectors), shouldn’t they be legally obligated to warn users when their data/info have been requested by any entity ?"
I think the Lockdown Mode will disable 2G only starting with iOS 17.
The press release [1] doesn't mention 2G directly but only "safer wireless connectivity defaults" but FastCo [2] is more direct "with iOS 17, Apple is not only beefing up Lockdown Mode (by blocking the iPhone from connecting to 2G cellular networks and from auto-joining insecure wireless networks) but bringing Lockdown Mode to the Apple Watch".
It is considered CSS [1], which makes sense to me as this relates to styling. What has never made sense in my mind is to have completely unstyled pages rendered with microscopic fonts on smartphones. Doing so for old sites that, at the beginning of the mobile revolution, assumed on their CSS sheets 1024px wide screens is reasonable (though still debatable). Not so for CSS-free pages, whether they were authored in 1991 or in 2023.
I'm sorry if I got carried away, I wasn't replying to you in this last part :) For the record, I would also make this exception, though it would be neat to be able to select those without even the meta viewport tag.
No problem, really. Thanks for the correction. This is indeed css. I must have automatically associated meta tags to non css data only. And I totally agree with you concerning the microscopic font and the meta tag.
I don't understand why it has to be added to every single page. Is there a reason this is not implemented as a default browser behaviour for devices where it matters (i.e. mobile phones)?