Trying #Solid pods right now. Failing. Signed up at #Inrupt's #PodSpaces. Somehow can't use it to login into Liqid Chat, doesn't give me a pod URL. Tried signing up at inrupt.net instead. "Registration closed" once you sent the form... Got a pod at solidweb.org instead. "Unauthorized" when trying to log in with it. solidcommunity.net shows errors on its register page...

Finally managed to log into the PodPro app with Inrupt's PodSpaces.

I guess some apps aren't super well maintained?

Managed to log into Media Kraken. Had to pass the following Pod provider URL: https://login.inrupt.com.

There's almost zero explanation, anywhere, it's quite hard to start exploring this solution.

Inrupt Identity Provider

Inrupt Identity Provider

@pawamoy You hit straight onto two of the biggest challenges as a Solid app developer:

- Breaking changes leading to apps breaking.
- Solid servers having terrible UX.

#SolidProject

@VincentTunru I see, thanks, that's unfortunate 😅

@pawamoy There's been a number of breaking changes to specs and apps and pods haven't kept up.

As it is, the current Solid protocol spec is an input into a new standardisation process: https://www.w3.org/groups/wg/lws/

Solid is still maturing...

Linked Web Storage Working Group

The mission of the Linked Web Storage Working Group is to enable the development of web applications where data storage, entity authentication, access control, and application provider are all loosely coupled, as opposed to the web of today where these are typically all tightly coupled and changing one requires changing all, sometimes at the price of all past data. This will be achieved by identifying a set of relevant <a href="https://github.com/w3c/lws-ucs">use-cases</a>, and standardizing a <a href="https://github.com/w3c/lws-protocol">protocol</a> between applications, on the one hand, and identity and storage servers, on the other hand.

W3C
@jg10 thanks! I'll see if I can find a place where I can suggest a few docs updates to #solidproject 🙂