Michiel de Jong

I think there are three sides to OCM that we could develop as separate GNAP extensions: * client instance discovery (the AS initiates the registration of a new client instance,...

The first two would also be quite valuable on their own for Fediverse and Solid probably. The third one would also be quite valuable on its own in classic OAuth...

Maybe we can adopt server-to-server signatures like https://www.w3.org/wiki/ActivityPub/Primer/Authentication_Authorization and https://github.com/cs3org/OCM-API/pull/92 and then use that instead of pure GNAP. Or maybe GNAP allows it?

Done, see https://github.com/cs3org/OCM-API/pull/98#issuecomment-2325971606

Thinking about the following changes: * addition of secure websockets protocol * deprecation of insecure websockets protocol * start rejecting clients that don't send `ath` (see #151) We can categorise...

Working on this in https://github.com/solid-contrib/solidservers.org/pull/9

OK i can add Transfer-Encoding on HEAD, to get full points on this test. But the http spec says 'MAY omit' and the solid spec doesn't overwrite that, so it's...

See #112 for my proposed way of handling this.

Sure, but they're not currently required by the spec, right? We could open an issue on https://github.com/solid/solid-spec about it, then discuss if pod servers should be required to implement them...

This also implies that clientId is an IRI which means it doesn't easily fit into routes like https://github.com/pdsinterop/solid-nextcloud/blob/7162a2c30be90aeb9c1d636eae19f60bcfc751d7/solid/appinfo/routes.php#L13-L15