Sebastian Lasse

@hongminhee @fedify

about above;
We just finished the first Social CG Dev meeting after the summer break [thus not the real first Tuesday this month] …

There will be some even new properties in the Data Portability Draft.
I summed up the new C2S spec drafts here:
https://digitalcourage.social/@sl007/117189119258003701

And then there is a Special Community Call for next Tuesday :
https://www.w3.org/events/meetings/4b3419c9-0d4c-460f-8a32-b575acd87b6c/

Esteemed #Fediverse –

the #ActivityPub #ClientToServer API is magic.
For menschys we are currently implementing the new specs.
There are multiple drafts already, e.g.

Auth
https://swicg.github.io/activitypub-api/basicprofile
with according
Metadata https://client.dev/
and example in https://github.com/swicg/activitypub-api

Seek
https://swicg.github.io/activitypub-api/seekitem

Autocomplete
https://swicg.github.io/activitypub-api/autocomplete

Server Sent Events
https://swicg.github.io/activitypub-api/sse

#fedidev #oauth #seek #autocomplete #c2s

/ @clemensg

@hongminhee @fedify

Hey there,
this is about the new #ActivityPub C2S specs. introducing new properties.

In https://swicg.github.io/activitypub-api/basicprofile#discovery – the according example https://swicg.github.io/activitypub-api/examples/oauth/index.html expects the properties to be either in the /.well-known/oauth-authorization-server or in the Actor.

How can I support them in Actors created by fedify, e.g. in an ActorDispatcher ?
Maybe they should be defined in the default context …
#fedify #oauth