Things #musl libc will never do (broad but not comprehensive):

- Nag you to update.
- Phone home to check it if should nag you to update.
- Tell you a CVE can't be fixed without updating to the latest version.
- Try to force you to switch from glibc to musl.
- Get other software you depend on dependent on musl.
- Rant against "wokeness" or "DEI".
- Integrate "AI" into your libc.
- Give you up.
- Let you down.

Addendum to "things #musl libc will never do":

- Request your age, date of birth, or proof of identity or attempt to report it to applications.

@musl gonna be funny if musl's illegal to use in california :3
@pikhq I mean, that's #California's problem, not that of @musl

@pikhq @musl But it could be even somewhat scary if musl is illegal to be distributed in California…

(IDK, I didn't read the laws.)

@musl what about running around and deserting me?
@dysfun See: "not comprehensive" 😂

@dysfun @musl

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS BY RUNNING AROUND AND NONDESERTING.

😓

@soc @dysfun @musl well, every single piece of software is!

  • Show me a poeve of software, #FLOSS or #CCSS doesn't matter, that doesn't have this clause?

And no, "#CallForPricing" and #NDA'd #MILINTEL / #Aerospace stuff like #VxWorks doesn't count!

@dysfun @musl
If it is not forbidden, then it is permitted.
@dysfun @musl
May also make you cry and/or tell a lie
@dysfun @musl well, all computer programs run...
and libc has a file remove function, meaning it can delete itself, meaning it can desert you...
@musl
- introduce a macro that lets us detect musl in ways other than /proc and parsing elf symbol tables
@musl

- merge patches sent to the mailing list
- set up a reasonable git forge and issue tracker
- fix the CMSG_NXTHDR warning
@musl Got rickrolled in the most big brain way possible :D
@musl But you've made me cry, on occasion
@musl re last 2 points: will it run around there and desert me?
musl libc (@[email protected])

@dysfun See: "not comprehensive" 😂

Treehouse Mastodon
@musl i should fork musl libc and as a shitpost make the fork:

- have every call run an update check first to see if that specific function has changed since the latest update
- by doing uncached http for each call
- ensure everything that can be madr vulnerable is vulnerable unless you build from master
- try to nag the user to get rid of any glibc-using software found in e.g. flatpaks
- rant against wokeness and dei in the readme (as a transfem lesbian enby this would probably be the hardest one to actually do without hating myself but this list wouldnt be complete without it)
- prompt 5 LLMs prior to any syscall with the question '$LLMNAME is this real'
- give the users up
- let the users down
MissConstrue (@[email protected])

Attached: 1 image Sometimes y’all, there is the perfect meme. #witchy #infosec #darkarts #updates #funny

mefi.social