Notices by F4GRX Sébastien (f4grx@chaos.social)

@dansup @kalisz79

"such a trusted and established developer like myself"

Is everything okay? are you drowning in your own pride yet? with all due respect, fuck off. this is disgusting behaviour and the best possible way to kill any trust you gathered before.

@tinydoctor @molly0xfff do not blockchain

@juliegiovacchini @ploum personne ne t'oblige a utiliser ton nom je suppose.

@juliegiovacchini @nartagnan @ploum etudie bien ce "enfin je crois". Je suis pas la pour te dire quoi faire, jai mis moi meme beaucoup de temps a supprimer mon twitter inactif, mais finalement je me suis dit que les gens *qui comptent* savent ou je suis et se feront pas avoir, et les autres n'ont aucune importance. J'ai un peu le meme caractère que Ploum donc ca m'a pas top pose de problemes. Il faut y réfléchir calmement.

@juliegiovacchini @ploum m'avait explique que l'usurpation d'identite n'a aucune importance. En tout cas moins que de grossir les stats d'utilisateurs.

@bortzmeyer l'IA dit merci.

@lanodan @chjara @niconiconi if it's not real it cant hurt you.

@aral @cemedia Because I dont understand the tone of this article. I'm not a native english speaker. it makes my head spin. it looks written like the onion. I dont know if I should continue reposting it.

Looks like this IS a satire site. I am not sure it's a great idea that such tragic matters are treated in a satirical way.

I am really uneasy with this article so I just asked sincerely your opinion.

@cemedia why did you retoot that @aral ? I genuinely dont understand.

@Jain @linus also, typical LCD failure mode here.

Tired: X (formerly twitter)

Wired: dark maga headquarters.

@mr_daemon @ryanc i've seen this in linux somewhere, iirc.

@bortzmeyer au lieu de s'intéresser au post effondrement faudrait s'intéresser a l'éviter deja. ces gens me saoulent.

@ryanc i need your clothes, your boots, and your motorbike.

@elena @KamalaHarrisWin I'm not a specialist but IIRC a chador and a burka are EXTREMELY NOT the same thing.

@chjara @lanodan I believe the limit was macro symbol names that mandated O_CREAT, and the creat() followed the trend.

one byte saved was a good thing, memory was scarce and teletypes were slow.

Thats the reason for ls,rm,mv,cp, etc.

@chjara They failed yes https://www.francetvinfo.fr/les-jeux-olympiques/triathlon/triathlon-aux-jo-de-paris-2024-deux-triathletes-portugais-malades-apres-leur-participation-aux-epreuves-dans-la-seine_6716223.html

@dangoodin @ryanc reminds me when we cracked all the 512 bit TICalc firmware signing keys several years ago. I still have a laser engraved calc cover with prime factors on it. Took a month for a dozen of private keys for a dedicated crew of happy hackers contributing BOINC time. That did not even cost $70.

@dansup i am not familiar with the code base, true, and devil is usually in the details I know, but I am familiar with long term compatibility of evolving products.

A stable versioned api is good. I think most of the work should be on client apps, right? Client apps can test for new versions of APIs and gracefully fall back on previous versions? This sounds like a valid design pattern even if I'm not actually familiar with the implementation details...

@dansup as a de facto central dev authority they can just 1-code properly to avoid breakage of 3rd party apps because of the new features , and 2-just publish an update notice and everyone will follow.

I want to avoid false reasons based on potential technical incompetence.