Notices by rqsd (rq@borg.social), page 4

Setting up a new service :HyperNeko:
Having to maintain it :haggard:

Tired: the Linux kernel
Hired: the Linux colonel

Instance names as last names on fedi

@lanodan@queer.hacktivis.me My condolences

https://en.wikipedia.org/wiki/Internet_Explorer_for_UNIX since some people doubt me

Debugging is a CTF in which nobody knows the solution to start with

Content warning indicates I won't like the post.
I open the post.
I don't like the post.

I keep being surprised by this outcome. :akko_derp:

When somebody you haven't interacted with much remembers you exist and goes through your profile and likes a bunch of stuff

Inside me, there are two wolves

one producing banger post after banger post without stopping
and one garnering pity likes

@chjara@akko.wtf wasm in the Linux kernel when

@chjara@akko.wtf I usually use "that's stupid horseshit" as my go-to

@mia@void.rehab ed

Tired: pronouns
Hired: dangling pointers that cause a segmentation fault in anybody who tries to reference you in their head

https://datatracker.ietf.org/doc/rfc8764/

Apple's DNS Long-Lived Queries Protocol

Draft history:

- 00 in 2005
- 01 in 2006
- [long-lived silence]
- 03 in 2019

That's way too long-lived!

Documentation

but it ships as a CHM file

@chjara@akko.wtf The Open Group, holders of the UNIX® registered trademark
The Free Group, computing copyleft communists
The Net Group, angrily evangelizing IPv6

*This is now the big LSAPI thread; mute replies if you don't want me to liveblog reading this spec*
A valid license handle is always returned by this function whether valid license resources are granted or not. This handle must always be released with LSFreeHandle() when the application has completed execution.I'm not sure how I feel about this, honestly. On one hand, it makes it easier to just always clean up everything, but on the other hand, I feel like you would bail and return early anyway. I wonder if this has some non-obvious practical use...

Oh God, this has weird complexities. Apparently LSRelease() only releases per license unit resources and the license handle and associated context is released separately with LSFreeHandle(). I guess it makes sense if you need to keep track of every license individually (e.g. a CAL) and mid-operation one of the CALs expires...

The spec would've greatly benefitted from some kind of diagram that gives an overview of when in the lifecycle of a program's execution which functions are roughly expected to be called in what order...

(A) The default umber of units commensurate with the license granted.ha ha found a typo