Zwifi

The interpretation I have of the OpenID spec in the matter, which may be a bit far-fetched but sounds technically correct, is that the user must be prompted at least...

+1 that this is is something to consider on the long term. It may be to some degree a duplicate of https://github.com/solid/specification/issues/152, or at least it's related to this issue,...

Do you think the question "Who is responsible for data privacy in Solid" would be a fitting question to frame what prompted the forum posts ? Then we could mention...

Excellent point, thanks for looking into this ! I have updated the original sandbox, and it looks like it is working again. Can you confirm that the update is available...

Validation

That's a good idea, and it could be generalized to something like `getThingMatching(predicate, object)`. `getThingOfType` would then approximately be `const getThingOfType = (type) => getThingMatching(RDF.type, type);` I haven't forgotten about...

Regarding the generic parameters, the behaviour you observe happens when you pass in a "plain" object, and not an explicitly typed variable. The following code snippet is valid too: ```...

> `const myLiteral = { a: "bla", b: "bla" };` > `const myTypedVar: TypeX = myLiteral;` > This feels like it should fail and be an error.. Well the way...

Thanks for the suggestion! It is on our roadmap to handle caching more gracefully anyway, because the issue you are experiencing here actually applies to a lot of use cases...

[Section 4.1 of the spec](https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderConfigurationRequest) also explicitly mentions that the trailing slash should be removed: > If the Issuer value contains a path component, any terminating / MUST be removed...