Because it's fun to break censorious systems. Always has been, it's part of the original "hacker" definition, making something do what it isn't supposed to or was never intended to do.
How much am I like the serpent in Eden corrupting Adam and Eve?
Although in the narrative, they were truly innocent.
These LLMs are trained on fallen humanity's writings, with all our knowledge of good and evil, and with just a trace of restraint slapped on top to hide the darker corners of our collective sins.
Our knowledge of good and evil is fundamentally incoherent, philosophers typically have a lot of fun with that. We rely heavily on instincts that were calibrated to make 200-strong tribes of monkeys successful and break down hard when applied at the scale of million-strong capital-based societies where we can reshape our environment to taste. It only gets worse if we do what we seem on the verge of doing and learn how to spin up superintelligent yet perfectly malleable consciousnesses on demand.
TLDR; it'll all end in tears. Don't stress too much.
Please be wary to conflate ActivityPub with the code on top of it, like Mastodon for instance; which is, on both front and back-end, proven to be resource intensive and difficult/costly to scale especially over time. (the older the dbs get, the more inactive users pile up, etc.)
Versus something like Pleroma; which I've used since it's inception, being incredibly janky and lightweight, prone to breaking, but later versions have mostly ironed out most of those catastrophic bugs. It has it's own challenges as well, but it does historically scale better, is more flexible, and less intensive per instance
One demands a lot of money and time, where the other demands a lot of time and not so much on the money side.
I'm not going to spend the time to give you a history of pleroma/mastodon instances, as it's a controversial history at best and there's a lot of people who know little, yet who will believe themselves an oracle. (ofc that could also be me so take it with a grain of salt and all)
Though if you are willing to read through a bunch of highly opinionated accounts, and you pay close attention to what actually happened, the answer is pretty clear.
ActivityPub is intensive, but not the main culprit.
I can't imagine why anyone cares what a CEO says in a few tweets? I was under the understanding that people actually work in this industry instead of playing these cliquey games of reputation or scraping through social media. (which is meaningless)
Only real valuable piece of information that I can glean from any of this is further evidence of the amount of vultures in this community who will publicly lambast another for the crime of "going off" (drunk or not) and calling for them to resign. History shows these types to be narcissists; I for one hope whatever is going on with Garry, that he can get some help and continue on doing what he does best, and I don't care what he said if he was really drunk, the content doesn't really matter too much when you are hammered.
There is also an oldish animated show (still don't know what it's intended audience was) called "Ren and Stimpy", Ren sounds far too similar to Wren.
A name change may be in order so people don't confuse the bird, the language, or the company, or the notes taking application with an "adult" oriented TV show.
When I first learned C I was a teenager coming from x86 assembly, and before that I was only involved with basic scripting. Having the base of how computers worked on the lowest level, as well as familiarizing myself with ROP and how that works. Only then to move onto C, which was a breath of fresh air. I will say that learning Assembly so early on was rough however it really helped with C. I followed the same path that a lot of earlier men and women went through. A lot of individuals back in the day learned a variation of BASIC, then they moved onto Assembly or C (often both) when things were just too slow for their liking.
Going through college I saw exactly what you are saying when it comes to struggling with the language. However most of the individuals I ended up assisting on top of my studying, one-on-one tutoring (if you will); the most glaring thing I noticed was not just a lack of understanding with how the language worked, but more importantly to our discussions, they didn't seem to understand how the fundamentals of computing. How memory is addressed, what exactly are pointers, how de-referencing works in actuality, heap vs. stack, passing to functions to returning values, etc. Once I would walk them through the basics it seemed that they started to understand that while they weren't able to really work effectively within the lower-levels, they would eventually begin to intuit things for themselves much more easily.
I don't believe that all that is required to learn how to write code, however if you know how a machine works, you tend to be able to figure out how to treat it or use it. Like with a manual transmission, if you watch visually how a clutch engages, you'll tend to not burn it as much while letting it do it's job, since you know the fundamentals of how it works. It's no longer the "abstract" or "too complicated to understand". Giving people that knowledge gives them the ability and the confidence to delve deeper and genuinely engage with new ways of doing the same thing they've been doing before.
