Thomas Touhey @thomas@touhey.org
Individu de 21 ans, amateur d'informatique. Curieux et désorganisé.
- Pronouns
- Il, lui, he, him
- Languages
- fr (90%), en (60%)
- Location
- Brunoy, France
- Website
- https://thomas.touhey.fr/
"Welcome to page 666, the official Vi fan club. You know, because vi-vi-vi is six-six-six."
Thank you @adamk678 for introducing me to Stylish my mastodon is now Splatoon themed and I'm happy 
(Disclaimer: I've only ever played Splatoon once in my life but I love the aesthetics of it :joy: )
Eventually I'll make my own theme with wider columns too but for now I'm happy with just a more colourful page ♥️
Sorry for repost, figures I'd forget the image the first time 🙄
Statut : pas mort
Humor of end of friday after a looong week How to write a Bash script in Perl style : cat script.sh |sed 's/\n/;/g' > ScriptConverted.sh #Bash2perl cc @greenman
Bonne idée pour le café @aeris.
Oh! What if you could write a post twice, in multiple different languages, and attach the translations together? And you note which language each one is in, and it gets displayed in that language first when people click on it, but then they can also tab and see the other language? :/
in firefox, if you go to about:debugging and click "workers" you can see all the javascripts running in the background on your firefox for the benefit of others
image.png
Et @silicium tourne toujours. o_o
I'd really like to switch to that as my main phone some time, but I don't feel like I'm in control of it yet, and a very important feature is missing yet: SMS encryption in a TextSecure-like way.
The phone runs on KaiOS, although I don't know how to run my own apps on it yet (heck, I didn't even manage to connect it to the WiFi!). Once that's done, I've found the protocol descriptions, so I'll explore the SMS-related APIs and try to make something up.
OBTW I got that Nokia 8110 4G thingy. I'll try it out when I have some time (which I don't until July). 
… okay, I'm quite tired. Actually this is a mistake on Chromium's side: they take the sniffed encoding before the one given by the HTTP Content-Type header, this is not a mistake on the standard's side. >_>
And by the way, in case you didn't know, the fact that the encoding sniffing algorithm uses BOM over the HTTP Content-Type header is used in the wild for going around CSPs.
Just include an external JSON document while putting a UTF-16BE encoded JS code into it and it will be executed with some of the data. Here is a example which works with Chromium (but not Firefox for some reason):
Actually no, I was right, just wrong on the number of bytes:
“An explicit meta tag within the first 1024 bytes of the document”
I've always thought the <meta charset="utf-8"> tag had to be in the first 128 characters/bytes of any HTML document to be taken into account. That's why I always put any ASCII art comment *after* the <html> and first few meta tags including the charset one, not before.
But now I think I might've understood that in the wrong way, and that it only meant I had to use an ASCII-compatible encoding such as ASCII itself, ISO-8859-1 or UTF-8…
Pas sûr qu'ils apprécient à la Mairie de #Villeurbanne. Pour rappel, cette collectivité a acheté Office sans appel d'offre il y a quelques années. L'#April avait suivi le dossier.
Voici le résultat, des documents illisibles ou non remplissables avec #LibreOffice.
Always strange to see this on my TV.
J'ai rattrapé mon nombre de tweets en nombre de toots /o/
Meme de geek:
