So use Mastodon. Problem solved. Twitter is toxic. You can't fix Twitter without fixing the whole culture.
Getting rid of Elon (in some hypothetical universe where you could do that) & restoring the site's design back to what it used to be isn't going to change the toxic culture. Twitter only selectively enforces their own rules and it's been that way since Jack Dorsey was in charge.
(Here's an example: I can think of a few tweets where people are ganging up on someone and those are still there to this day. Their rules are very clearly 'no harassment and no dogpiling' and they've always been that way. Do you think they give a damn to enforce their own rules? Only when Elon's right-wing buddies are being attacked, then they bother.)
Restoring the site's design back to what it used to be isn't going to magically fix the toxic culture (people sniping, dogpiling, attacking others etc). Better if we just set the whole thing on fire and start from scratch, build something new - oh wait, we have that. It's called Mastodon. The learning curve isn't that bad. But that would be learning something new. That would be actively doing something other than complaining.
Why would you want to back to a place where a billionaire or a corporation collects all your personal data? If you like that sort of thing, go to Threads, Bluesky, Post, etc. Nobody's stopping you.
The Klingon boy band made the final cut, thankfully. However, they shot two versions of the Klingons, led by Bruce Horak as the Klingon captain. The second was opera. Ultimately, the opera take felt too close to the other singing. Luckily, the Klingon boy band won.
I hope you mean "sentience".
Correction: Uhura*
That's a lot of words just to say "we know nothing".
.world is *a* firefish instance. not the main firefish instance (which is .social).
so when I said, "it's not the same person running it" - the flagship instance, if you will, is .social. many of the main people coding it are on .social (afaik). .world is just another instance.
that was i meant, if i need to clarify : the main main people coding-wise are not the same. the flagship instance (which is not .world) is not run by the same people as the mastodon flagship instance.
"the flagship instance" (if you will) of Mastodon is mastodon.social. not run by the same people who run firefish.social. they are not the same thing, run by the same people.
that's what I was getting at. i guess I only make sense to myself.
Just to clear something up, CalcKey is now known as Firefish(.social) and that's run by a completely different person.
First musical episode of Trek ever...ever...ever... *hears echo*
it works if you comment.
like this - now it shows up in your notifs.
there's no actual tagging function, though.
I completely understand what was said - that is not the problem. I'm well aware.
The problem is that I misread the issue I linked to.
My comment has since been edited.
*crickets* Nope. Not wrong.
You could've ended that sentence with another word and it would still be accurate.
And that's all I'm sayin'.
Just a suggestion, you might want to insert the word "allegedly" somewhere in there because Meta is refuting that assertion.
"To be clear: ‘No one on the Threads engineering team is a former Twitter employee — that’s just not a thing" - Andy Stone, Meta's communications director
edit: yes I know that doesn't preclude the possibility of Meta hiring former Twitter employees and not making them part of the Threads team.
Short answer: No.
tl;dr answer: There's no tagging function in place unless you manually tag them using markdown, and that still wouldn't notify them. That would be a bandaid solution at best.
I still use it with a couple of friends on a private server.