well, the problem here obviously is that threads is not fully federated. and therefore if that is a concern you need to treat your thread account as not federated too. federation only works if everyone that you want to reach is in it.

▲

JimDabell 3 days ago | parent [-]

> the problem here obviously is that threads is not fully federated.

It is federated for the people that want it. It’s a setting.

> you need to treat your thread account as not federated too.

But it’s federated for some people and not for others, so there isn’t a single behaviour I can take that consistently works.

	▲	jedahan 3 days ago \| parent [-]
		I am having trouble imagining the failure mode you are trying to avoid. It sounds like threads implementation of federation is broken. What effects does toggling that federation setting on or off do? Like if someone is following “duplicate” accounts of yours and therefore would see double posts, that person can unfollow one. Still double work for you that kind of sucks. Scuttlebutt had some work done on publicly declaring two identities as the same, I wonder what that would look like for posts. Like a post-id or simple equality comparison or hash could work server side or client side.