Recent searches
Search options
For the last several months I've been working on making a federated app.
I just finished migrating it to use the latest iteration of our new #leafprotocol data format on top of the #willowprotocol and so far it's going really well.
In this post I share some of the concepts and rational behind the Leaf Protocol:
https://zicklag.katharos.group/blog/introducing-leaf-protocol/
@zicklag "One of the problems with this is that your server only knows about things that have been sent to one of its inboxes."
This is untrue. Any AP server can request data from any other server to stay in synch. Literally every AP object comes with an URL to fetch its full information.
@evan The fact remains that things like counts and, more importantly, post replies are not viewed identically across multiple homeservers, due to the event driven nature.
There is also the fact that you don't see any post by default if you don't follow somebody and they aren't on your server. This is particularly noticeable with single-user ActivityPub instances:
https://jvns.ca/blog/2023/08/11/some-notes-on-mastodon/#downsides-to-being-on-a-single-person-server
@zicklag That's an implementation problem; the counts are available from the remote server.
I highly recommend reading my upcoming book "ActivityPub: Programming for Social Web" from O'Reilly Media, coming out later this month. You can read a free pre-release version here:
https://www.oreilly.com/library/view/activitypub/9781098162733/
@evan when you say the counts are available from the "remote server," do you mean the server on which the original post is located?
@joshshaked the `replies` collection holds all the replies to the post, except those that weren't sent to the OP. `Collection` type objects have a `totalItems` property.