@cwebber The #ActivityPub spec's problem is not in that simplistic phrase "users are represented as actors here".
The problem is that there is NO technical description of the whole domain model layer: relation between Actors (e.g. Person) and Users of servers. Current version will be interpreted as having one-to-one relation between the two _different_ kinds of entities, and that _is_ incorrect
As for the counter issues; Each instance should know whenever it's count is out of sync and offer the possibility to update directly from the origin.
Maybe there is a need to finance a network of hub servers to provide all instances with fast up-to-date indexes?
Even with legitimate and logical reasons behind the mismatching #synchronization, that is not a situation that will help this platform succeed.
There seem to be problems with showing full threads.(?)
I cannot see the reply I reply to here now from my @LeeteqXV user.
Often if I open a reply and expect to get access to the full thread, I can only see some of its replies. When I back out, find the timeline of the user that posted the initial toot, find and open that toot, only then can I see the whole thread. #Mastodon #Bug ?
In order to foster F-Droid support of Beta releases, I posted my vision of the target process to the relevant F-Droid's change ticket, see: https://gitlab.com/fdroid/fdroidserver/issues/161#note_37431690