I work in Trust and Safety (not at Meta). We've never 'randomly' shut down an account and any action involving deactivation or deletion goes through thorough human review with no exceptions.
The lack of respect for the end-user is squarely a Meta problem, not an industry problem.
This is now the 5th comment saying the same thing, so I'll respond. I'm aware of these and they were terrible. In a just world, they would get as much if not more media attention.
The difference is the public nature of the execution. That is what makes it more similar to, say, Colombia or Venezuela _to me._ Within the context of 'magical realism', it is the perspective and mass dissemination of the violence that heightens that feeling.
Going back to the original topic, there is a reason that most of 100 Years of Solitude's pivotal moments happen around the staging of public executions (and not so much the off-screen violence, of which there is some but it's not focal).
On Sunday, I was talking a Mexican friend about how politicians get killed in our countries (Colombia, Venezuela, Mexico). Just in June, presidential hopeful Miguel Uribe was shot and killed in Bogota. In the head, in front of a crowd.
I remember being grateful about how that doesn't really happen in the US (Trump being the most recent, but he survived). I guess I was wrong... and, in that case, Garcia Marquez might agree with you.
The most direct, non-marketing, non-aesthetic summary is that this model trades off a few points on 'fundamental benchmarks' (GPQA, MATH/AIME, MMLU) in exchange for being a 'more steerable' (less refusals) scaffold for downstream tuning.
Within that framing, I think it's easier to see where and how the model fits into the larger ecosystem. But, of course, the best benchmark will always be just using the model.
From what I've heard of the working environment, it's borderline impossible to be employed there without at least _seeing_ what was going on to your colleagues. I mean, I remember reading about sexual harassment there in 2018, at which point it had _already_ been going on for a while.
>You "know" all that, but do you actually __know__ all that.
Companies that underpay fullstack web developers usually don't actually care if their engineers __know__ all that, either. They just want the cheapest, fastest, CRUD app they can demo and ship out ASAP. As a result, these employers fail to recognize (and reward!) the fullstack web developers who do actually __know__ the full stack.
At my last job there was a rockstar web developer engineer who could easily double their compensation by moving to a larger company instead of a startup. My advocacy for them to get a raise or promotion was cast as 'the engineer is complaining again."
What? These are perfectly valid questions to be asking and do not inherently stop you from researching what you're working on.
I know some scientists that define their research direction by asking these questions first before pursuing an idea. Many great inventions like optogenetics or expansion microscopy came from this investigative strategy. It can help keep your resources and energy in check.
It's definitely an experience design tradeoff. It's nearly impossible to organically find livestream content on YouTube outside of 1) copyrighted TV shows or 2) 24/7 music streams.
https://www.nature.com/articles/s41598-018-38096-z