Recent searches
Search options
@evan Hi - I'm trying to get `ap` working with my server, so implementing FEP-d8c2 for login. Shouldn't the client Application at https://github.com/evanp/ap/blob/main/docs/client.jsonld have an inbox property? I realise an inbox may not make a lot of sense for a client but it's a MUST property in the ActivityStreams spec and the library I'm using throws an error when I try to load your Application JSON-LD. Or if you think it's OK to skip the inbox property for the client, would that be worth you adding to the FEP?
@OpinionatedGeek No, `inbox` is not a MUST property in the Activity Streams 2.0 spec.
`inbox` and `outbox` are a MUST for actor objects, but this client is not an actor.
https://www.w3.org/TR/activitypub/#actor-objects
What library are you using?
@evan Ah, OK - apologies for my misunderstanding. (I read 'The Activity Vocabulary provides the normative definition of five specific types of Actors: `Application `| `Group` | `Organization` | `Person` | `Service`.' and thought an `Application` was always an actor. I'm trying to understand it all, honest!)
I'm using the Rust `activitystreams` library: https://crates.io/crates/activitystreams/0.7.0-alpha.25
@OpinionatedGeek neat. How is it?
@evan It's very good! It aims to deserialize any valid ActivityPub JSON, and raise an error with any invalid ActivityPub JSON, and it does a good job of it. I'm guessing I'm using it wrong in this particular case.
@OpinionatedGeek yes, it's pretty common to load objects in AP that aren't actors, so there should be a way to do that.
If it's requiring an `inbox` property just because the object has `type` `Application`, that's probably a bug. If that's the case, I can add a dummy to work around it.
@evan Thanks but I wouldn't do it if it's just affecting me - I can certainly work around it, now that I know I'm misunderstanding what's going on.