I was going to get involved in the development but after 4 months they still haven't merged the PR which makes it easier to onboard new developers (and also makes it easier to spin up new or update existing environments) so I've reconsidered where to spend my time. Which is a shame because when I saw kbin was built on Symfony in PHP I had very high hopes for it. I think the onslaught of new users completely overwhelmed the developer to where maintaining the instance took priority over developing it, which in the end makes it more likely to die off instead. /rant
What you're describing is the same problem we have with email. Anyone who owns a domain or can register an account on an existing service can send spam to anyone or everyone. The solutions for email spam are likely the same solutions for any federated service. No need to reinvent the wheel or go through all of the same trial-and-error pains necessary to find a similar solution.
Email has opt-in block lists trained by submissions from trusted users, server reputation, Bayesian spam filters, and possibly some others.
This article is factual yet also rage-bait. Suspending accounts is something he's doing now. Contacting employers of people working at car companies and investment firms is something he did five years ago. The article does not say he is contacting the employer of accounts he is suspending now; they leave you to infer that by placing both facts in the same headline but separate paragraphs.
React is incredibly popular because so many companies use it. They are banking on Facebook's continued support and development, and an assumption that if Facebook is doing it then it must be right. Being rich does not automatically make one right. Having worked at a company that forced React on its developers against their wishes I can unequivocally say it's bad.
In any system the right action should be the default action. Query parameters should be parameterized by default, variables in HTML templates should be contextually escaped by default, and so forth. "Don't make me think". React is the complete opposite of that: It requires you to constantly think about the render loop (aka "Component Function"), it hides the fact there is an object behind the scenes containing the component state, the documentation is littered with "don't worry about this feature until after you have a performance problem, then come back here for the solution", it's very neat and tidy for tiny example projects but does not scale well as the project grows.
Compare that with a system like Vue or Lit, which is much more intuitive, does the right thing by default, and is easier for existing HTML/CSS/JS developers to grok at a glance.
That is the primary argument my company used to justify forcing React. Do you know how many people we hired for their React experience? One. Everyone else was primarily backend or only had passing experience in React (not subject matter expert / does not know best practices). Meanwhile the rest of the team struggles to work in it (the frontend has become siloed) and very little of it follows best practice.
The reactivity of Svelte leaves a lot to be desired. The only difference between a computed property and a mutable property is let x = and $: x =, both of which are declared in the same top-level scope and doesn't provide much to distinguish them. The lack of reactivity on arrays and objects is a major foot-gun by default. The number of places they say "this looks weird, but don't worry it'll soon become second nature" in the docs shows that they acknowledge it's bad design to create code that is misleading or goes against the grain/standard for what behavior developers should expect (makes it confusing to work with and then use anything else, or vice versa).
The #await template directive is interesting; I'm not sure I agree it should be handled in the template instead of the script but if combined it would remove some boilerplate loading = true/false and error = 'message' variables from script scope.
Are there any kbin instances which are up to date with the source code?
I know Ernest is working on getting ready to update kbin.social but are there any other instances which are faster with the bug fixes and updates?
Proof that bots are manipulating content
See THIS POST...
Elon Musk Silences Critics By Deactivating Accounts And Reaching Out To Their Employers (finance.yahoo.com)
Kev Quirk, one of the admins of Fosstodon (a Mastodon instance), destroys Meta in an email exchange. (fosstodon.org)
The exchange is about Meta's upcoming ActivityPub-enabled network Threads. Meta is calling for a meeting, his response is priceless!