That's a wrap! Another successful #ThreadGroup Members Meeting has come to a close! Thank you to all who joined and participated in the sessions this past week. See you in Stockholm in October 2025!

To learn more about #ThreadGroupMembership, visit https://www.threadgroup.org/thread-group#Membershipbenefits

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

All right, they finally fixed the #thread! Back to checking out my threads...

Don't think #thread going to last... they still got issues... #socialmedia

Is #thread feeling under the weather again? Seems like #socialmedia let us down once more.

France-Algérie, vers une rupture des relations diplomatiques ?

#thread ↓

Day 1 of the #ThreadGroup Member Meeting in Denver was a success! Thank you to our guest speaker, Jason Page from CableLabs and Eric Hines from Inovelli for joining us and sharing your perspectives on #Thread and the #IoT industry.

Alles „nur Sammelleidenschaft“ - nicht strafrechtlich relevant - "gedanklich abgehakt"?

Im Prozess zum Brandanschlag von #Solingen am 25.03.2024 führte die Vernehmung eines Polizisten gestern ein weiteres Mal vor Augen: Die Ermittlungen wurden ohne engagiertes Aufklärungswissen geführt.
#Thread

Sono Piero (@pstrada.bsky.social)
#Meta #privacy #IA #WhatsApp

https://bsky.app/profile/pstrada.bsky.social/post/3lmtrw5afh223

> Non è triste. Cioè lo è, ma è anche molto illuminante. (Mi correggi il #thread per favore, @garantepiracy.it ?) Pensaci bene: se non hai un account Meta, non hai motivo di opporti ad alcunché. Giusto? NO. Varrebbe solo per i contenuti che tu pubblicheresti da loro. Peccato che: