Der #39c3 hat wieder viele gute Talks zum Thema Gesellschaft und Antifaschismus hervorgebracht. Ich möchte hier einige Empfehlungen sammeln:

"selbstverständlich antifaschistisch" - family & friends Hamburg
Eltern von Betroffenen sprechen über die massive Repression gegen Antifas mit Fokus auf den Budapest Komplex
https://media.ccc.de/v/39c3-selbstverstandlich-antifaschistisch-aktuelle-informationen-zu-den-verfahren-im-budapest-komplex-von-family-friends-hamburg

#Thread 🧵

Der #39c3 hat wieder viele gute Talks zum Thema Gesellschaft und Antifaschismus hervorgebracht. Ich möchte hier einige Empfehlungen sammeln:

"selbstverständlich antifaschistisch" - family & friends Hamburg
Eltern von Betroffenen sprechen über die massive Repression gegen Antifas mit Fokus auf den Budapest Komplex
https://media.ccc.de/v/39c3-selbstverstandlich-antifaschistisch-aktuelle-informationen-zu-den-verfahren-im-budapest-komplex-von-family-friends-hamburg

#Thread 🧵

Nouveaux services, mise à jour de services existants, nouvelles versions de logiciels…

Grâce à votre solidarité, nos actions impactent, chaque mois, près de 2 millions de personnes.

Petit #thread récapitulatif de ce que vos dons ont permis à Framasoft de réaliser cette année ! ⬇️

Nouveaux services, mise à jour de services existants, nouvelles versions de logiciels…

Grâce à votre solidarité, nos actions impactent, chaque mois, près de 2 millions de personnes.

Petit #thread récapitulatif de ce que vos dons ont permis à Framasoft de réaliser cette année ! ⬇️

I am currently working on the #Russmedia decision of the European Court of Justice.

The decision is said to unravel the European platform regulation, especially the rules about content liabilities. I have several issues with how the decision is framed and criticized. And I'd love to hear your thoughts.
#Thread

I am currently working on the #Russmedia decision of the European Court of Justice.

The decision is said to unravel the European platform regulation, especially the rules about content liabilities. I have several issues with how the decision is framed and criticized. And I'd love to hear your thoughts.
#Thread

@f_moncomble hey mais c'est trop bien cet utilitaire, bravo ! Et merci à @SarahPersil au passage car c'est dans le fil d'une discussion sur son Masto que j'ai découvert le #MastoThreader

Au passage, je continue, seul avec mon bâton de pèlerin, à militer pour l'usage du mot VertiPouet pour parler des threads sur Mastodon. Juste parce que je trouve ça beau.

#MastoHelp #VertiPouet #Thread

Everything has gone to...

In January 2023, @pluralistic used the term "enshittification" on his blog, pluralistic.net, to describe the deterioration process of the TikTok network.

Enshittification consists of four stages:

1. Platforms are good for users

2. Platforms abuse users to be good for business customers

3. Platforms abuse business customers to keep all the profit

4. Platforms die

🧵

#thread

#socialmedia #platforms #fediverse #activitypub #google #amazon #microsoft #enshittification

Everything has gone to...

In January 2023, @pluralistic used the term "enshittification" on his blog, pluralistic.net, to describe the deterioration process of the TikTok network.

Enshittification consists of four stages:

1. Platforms are good for users

2. Platforms abuse users to be good for business customers

3. Platforms abuse business customers to keep all the profit

4. Platforms die

🧵

#thread

#socialmedia #platforms #fediverse #activitypub #google #amazon #microsoft #enshittification

RE: https://mastodon.tn/@khaled/115560769334445428

Khaled and his family, surviving in #Gaza

#Thread

WiFi and #Thread/ #Zigbee networks use overlapping ~2.4Ghz frequencies, and interfere with each other.

I've learned it the hard way. My old gadgets kept losing WiFi connection, so I bought the biggest baddest WiFi router. It made everything way worse!

The router kept picking an "unused" WiFi channel 1, which was the same freq as Thread channel 11 that my HomeKit hub picked for its network. Stronger WiFi kept collapsing my Thread network, and knocked even more devices offline.

WiFi and #Thread/ #Zigbee networks use overlapping ~2.4Ghz frequencies, and interfere with each other.

I've learned it the hard way. My old gadgets kept losing WiFi connection, so I bought the biggest baddest WiFi router. It made everything way worse!

The router kept picking an "unused" WiFi channel 1, which was the same freq as Thread channel 11 that my HomeKit hub picked for its network. Stronger WiFi kept collapsing my Thread network, and knocked even more devices offline.

Was passiert mit den Menschen, die in den USA von den ICE Agents gekidnappt werden? Ein #Thread 🧵 .

Aktuell, Stand Anfang Oktober, werden 59.000 Menschen in Abschiebelagern festgehalten. Sie wurden ohne Gerichtsverfahren, teils bei Behördenterminen, teils auf offener Straße von vermummten ICE Agents gekidnappt. Aus den Lagern gibt es Berichte von Gewalt, Unterernährung und Verweigerung medizinischer Versorgung.

https://www.vera.org/news/more-people-are-in-immigration-detention-than-ever-before

#Muncipales2026 3/3 Pensez-y et parlez-en quand iels parleront de sévérité contre les délinquants, sécurité, exemplarité, justice pas assez sévères.
@Looping Je te laisse conclure ce #thread avec #Toulon.

Do you have a beloved photograph you'd like me to turn into handmade art? Are you a big fan of a particular landscape, animal, person, fictional character, building, etc, that you'd like me to make you a picture of?

I've got you covered!
#thread
#pleaseBoost

Was nicht alle wissen: Das Hochhalten von Büchern im Internet ist sehr oft verkaufsfördernder als eine positive Besprechung in klassischen Medien.

Vergesst den Einwand, dass eure Reichweite nicht groß genug ist. Vielleicht sieht eine Person mit vielen Follower*innen das Buch genau bei euch, wird so darauf aufmerksam, liest es, empfiehlt es. So geht Internet-Magie.

#Lesen#Gemeinschaftskraft#Thread

Was nicht alle wissen: Das Hochhalten von Büchern im Internet ist sehr oft verkaufsfördernder als eine positive Besprechung in klassischen Medien.

Vergesst den Einwand, dass eure Reichweite nicht groß genug ist. Vielleicht sieht eine Person mit vielen Follower*innen das Buch genau bei euch, wird so darauf aufmerksam, liest es, empfiehlt es. So geht Internet-Magie.

#Lesen#Gemeinschaftskraft#Thread

The #homeautomation protocol is named #Thread, perhaps that is a typo as #Threat is more apt and accurate. If you roll your own device you might very well experience the full force of their blood thirsty lawyers.

What the actual F.

I need help. First the question: On #FreeBSD, with all ports built with #LibreSSL, can I somehow use the #clang #thread #sanitizer on a binary actually using LibreSSL and get sane output?

What I now observe debugging #swad:

- A version built with #OpenSSL (from base) doesn't crash. At least I tried very hard, really stressing it with #jmeter, to no avail. Built with LibreSSL, it does crash.
- Less relevant: the OpenSSL version also performs slightly better, but needs almost twice the RAM
- The thread sanitizer finds nothing to complain when built with OpenSSL
- It complains a lot with LibreSSL, but the reports look "fishy", e.g. it seems to intercept some OpenSSL API functions (like SHA384_Final)
- It even complains when running with a single-thread event loop.
- I use a single SSL_CTX per listening socket, creating SSL objects from it per connection ... also with multithreading; according to a few sources, this should be supported and safe.
- I can't imagine doing that on a *single* thread could break with LibreSSL, I mean, this would make SSL_CTX pretty much pointless
- I *could* imagine sharing the SSL_CTX with multiple threads to create their SSL objects from *might* not be safe with LibreSSL, but no idea how to verify as long as the thread sanitizer gives me "delusional" output 😳

I finally eliminated the need for a dedicated #thread controlling the pam helper #process in #swad. 🥳

The building block that was still missing from #poser was a way to await some async I/O task performed on the main thread from a worker thread. So I added a class to allow exactly that. The naive implementation just signals the main thread to carry out the requested task and then waits on a #semaphore for completion, which of course blocks the worker thread.

Turns out we can actually do better, reaching similar functionality like e.g. #async / #await in C#: Release the worker thread to do other jobs while waiting. The key to this is user context switching support like offered by #POSIX-1.2001 #getcontext and friends. Unfortunately it was deprecated in POSIX-1.2008 without an obvious replacement (the docs basically say "use threads", which doesn't work for my scenario), but still lots of systems provide it, e.g. #FreeBSD, #NetBSD, #Linux (with #glibc) ...

The posercore lib now offers both implementations, prefering to use user context switching if available. It comes at a price: Every thread job now needs its private stack space (I allocated 64kiB there for now), and of course the switching takes some time as well, but that's very likely better than leaving a task idle waiting. And there's a restriction, resuming must still happen on the same thread that called the "await", so if this thread is currently busy, we have to wait a little bit longer. I still think it's a very nice solution. 😎

In any case, the code for the PAM credential checker module looks much cleaner now (the await "magic" happens on line 174):
https://github.com/Zirias/swad/blob/57eefe93cdad0df55ebede4bd877d22e7be1a7f8/src/bin/swad/cred/pamchecker.c

#C #coding