Claire

> So, it sounds like I can't search users or content on a basic ActivityPub server from the search bar of a mastodon instance or ones that are not on...

> Spent three hours trying to figure out why my Follow request couldn't be accepted by my homegrown service, turns out it's because the ActivityPub spec (4.1 Actor Objects) says...

Tried to add a few more specific error messages in #21617 to help with debugging

#8427 implements it, Gargron [was against it at the time](https://github.com/tootsuite/mastodon/pull/8427#issuecomment-415969018) and I don't think that has changed.

Followers can be on remote instances, so “Followers-only” isn't a subset of your proposed “Instance Only”.

You mean “Instance Only” would make your post visible to your instance *and* your remote followers? This could work but it's not obvious. Also, there would be value in instance-only...

I don't think notifying users of the **blocked** instance is wise in general. However, notifying affected users on the local instance probably makes sense, yes, although I'm not too sure...

Unfortunately, all identifiers, for accounts and statuses, include the username. So whichever solution we end up choosing, we'll have to deal with either of those issues: - old links and...

The issue isn't really about creating a new identifier, but migrating identifiers. Let me delve into this a bit deeper: in Mastodon, users basically have two “public” identifiers: - the...

@jeroenpraat depends on how we end up doing it. A safe way to do it would be to use username-independent identifiers for **new** accounts and statuses. Of course, that would...