Michiel de Jong

Talking strictly about the open Interledger, let's try to come up with some numbers of how impossible it would be to maintain perfect routing info: say there are 20 nodes,...

:+1: not sure if i understand the relation with idempotency, but i like how you phrased it with ‘not willing to commit to a response’, implying that best-effort responses are...

> I would consider any response to have an element of "best effort" So I think what you are saying is the server could choose to reply '200 OK' even...

@csarven as discussed on Gitter, > I just take it as a given that [the spec does not prescribe strong consistency] Please add a note about that in the documentation...

> If all inner operations are successful, 200. If not sure or expecting potential delays or conflicts... 202 is fine. If by 'successful' you mean 'successful and final', then that's...

> 200 entails that the request went through as a whole - atomic requirements are met. No, because eventual consistency is now allowed. See https://github.com/solid/specification/issues/91#issuecomment-539548997

Your WebID needs to be at your pod, even if your IDP is somewhere else. This is because when people browse to your WebID, they should see your foaf profile....

Right, true. So if I get it right now, as a Solid user you consume the following services: * a personal or shared domain name registration (whether your own domain...

Great that you bring this up! This is the work of the test suite panel, of which you are a member, and the reports are currently at https://github.com/solid/test-suite#table We are...

And just a side note (we can discuss this further within the test suite panel), although the specification-tests and the harness that runs them are both making good progress, there...