Armando :rick: on Nostr: Each implementation of #ActivityPub does this a little differently but given how ...
Each implementation of #ActivityPub does this a little differently but given how federation works, I think the right approach is:
- On the timeline, don't display the number of `replies`, `likes`, or `shares`. Those are all wrong, anyway.
- When you click on the item to view details display the cached version while in the background you pull the `Object` and all `replies` from the originating server. There should be some threshold to make sure you're not pulling it again when you just did it 500 ms ago. Maybe no more than once per hour?
- Once you have the updated version from the remote server, update the UI.
#fediverse #mastodon #iceshrimp
- On the timeline, don't display the number of `replies`, `likes`, or `shares`. Those are all wrong, anyway.
- When you click on the item to view details display the cached version while in the background you pull the `Object` and all `replies` from the originating server. There should be some threshold to make sure you're not pulling it again when you just did it 500 ms ago. Maybe no more than once per hour?
- Once you have the updated version from the remote server, update the UI.
#fediverse #mastodon #iceshrimp