Alex

.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.

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.