Soatok DreamseekerA story in 3 parts
#AI #slop #recruiterspam #enshittification #databreach #mercor
Luisf@soatok lol
lmao
Dźwiedziu
Ariel Millennium Thornton@dzwiedziu @soatok I prefer a simpler and more portable way to lol:
`yes 'xD ' | tr -d '\n'`
MiSt@soatok I haven't gotten the 3rd one yet...
but they were "impressed" by my "cobol skills" because I did the first few days of AoC in gnucobol a while back for the lolz and uploaded the result on github.
yeah I did not answer at all. what a shady organization. "unsubscribing" from their "newsletters" does not work either...
but they were "impressed" by my "cobol skills" because I did the first few days of AoC in gnucobol a while back for the lolz and uploaded the result on github.
yeah I did not answer at all. what a shady organization. "unsubscribing" from their "newsletters" does not work either...
AlexProw 💪
@soatok Reply email: You've met with a terrible fate haven't you? 
KadsepföschI'm undecided what "We took prompt action …" means in this context. XD
Did they act quickly or di they fire up their LLM again?
Dogiedog64"Why do you keep saying no to more slop? That clearly means you want more slop!" type shit. I feel that at some point you just gotta tell them, in no uncertain terms, to fuck off.
Arcanoraptor@soatok Oh liteLLM
Really hoping it’s a wake up call for the Python world on supply chain risk. Sure, it was just the AI bros this time, but could’ve been a lot worse. The ecosystem needs to do better
I mean, I know it won’t and everyone will just keep doing `pip install <pretty sure this is the package name>` until some other dependency gets supply chained in 6 months and they get got… but one can hope