Conversation
Notices
-
So an outbox is like a feed, but do you post to your own actor outbox or the servers actor outbox? Does the server have to read user outboxes and deliver them to the server outbox maybe? Does any of that matter for a single user instance?
-
@roboneko well the outboxes have specific endpoints to post to right? I guess I'm just trying to figure out if a user posts to their own outbox how it ends up in the server outbox or if you post to the server outbox how does it end up in your own (assuming there is an actual separate data structure for each outbox). You could index everything in one big bucket and just handle all outbox api responses with a single internal endpoint I suppose. I haven't dug through how it is done in mastodon or pleroma yet, and I'm working in lmdb so I expect there to be some differences in how the data is structured for storage, but I'm just thinking about it at the api level right now trying to better understand how it is intended.
If I understand correctly the server outbox is something like the local feed listing all posts from users on the instance and the individual outbox is all posts from an individual user. I guess in reality you don't really need to have a separate server outbox as far as storage goes. I am using time to index data so I can iterate over the outboxes (I am probably going the route of single user but may want to support multiusers) and create a meta outbox that includes all posts from all outboxes within a timeframe (easy since I'm using timestamps as keys).
-
@thatguyoverthere
> Does the server have to read user outboxes and deliver them to the server outbox maybe?
internally? that would be a bit silly. it's just an external API
your posts appear in your outbox so in that sense you post to it I guess. but really it's just an API to grab a timeline for your profile