@teknomunk@pwm Readable inbox is likely a part of client-to-server API. I also didn't implement it, but I do have plans for supporting other parts of client-to-server spec (posting to outbox at least).
@teknomunk 100%. Though, I think I was looking at an actor the other day and the inbox URL in the actor object was the instances shared inbox URL, so I think you can do that as well
@pwm The ActivityPub spec wants you to have the actor inbox be a collection of all incoming activities:
https://www.w3.org/TR/activitypub/#inbox > The inbox is discovered through the inbox property of an actor's profile. The inbox MUST be an OrderedCollection.
> The inbox stream contains all activities received by the actor.
I have no plans to make Apogee compliant with this. I suppose that you could check to see if activities have been accepted by checking this collection, but that sounds like unnecessary network traffic when the server is supposed to give you a 2xx status code when it accepts an activity.
@pwm Indeed. I don't keep any of the information around that would be required to populate that collection, and I don't intend to change that. The only place the activities show up is in a log file that is already getting rotated based on size.