In the past two weeks I haven't been working on ActivityPub, but slowly increasing the number of coverity scan defects in my scrobbling C application.

It's positively disheartening the amount of care one needs to put into C development to minimize the security risks of memory mishandling.

When the application is highly asynchronous, everything becomes harder.

When you're using other libraries that have restrictions about being used from different threads, everything starts exploding in random unpredictable ways and force having to sync memory management.