I happily announce, that #PodOS will get funding from @nlnet https://nlnet.nl/project/PodOS/

This gives me the great opportunity to add new features to the data browser, provide new elements for you to build custom low-code apps and dashboards and interwine PodOS with specialized apps and the rest of the #Solid ecosystem.

NLnet; PodOS

@angelo
Congratulations! Good to see there's still life in Solid.
@angelo Are you going to support SAI in PodOS, or have compatibility with @activitypods ?
@yala @activitypods are there any servers yet that support SAI? What do you have in mind with regard to activity pods that you would like to see added to PodOS?
@angelo
Let me see. For now I'm trying to get a holistic ecosystem overview to see how interoperable components could work together.
@activitypods
@yala @activitypods as I understand it activity pods is not fully solid compliant. As soon as they are it should work with PodOS out of the box. But there still might be additional features that might be worth implementing in PodOS. As I see it there is currently no hosted activity pod server I could quickly try? Or am I missing something?

@angelo @yala @activitypods
The main issue we are working on is solid oidc support.
You can check out https://mypod.store however the server is not well-maintained and more of a playground, you might suffer down-time.

Another thing: Unlinke other implementations, we don't have a file-based architecture (we use a SPARQL db, also using @nextgraph soon). As a consequence you can't choose the name of the URI when creating resources which other implementations let you do. No "slash-semantic".

MyPod.store

MyPod.store

@laurin @yala @activitypods @nextgraph the backend storage should not matter for the solid protocol, you don't need a file based storage. But Solid protocol is based on containers and documents, if you want to be compliant you need to support that, see e.g. https://solidproject.org/TR/protocol#server-post-container
Solid Protocol

@laurin @yala @activitypods @nextgraph do you have a test suite or documentation about what parts of the solid spec are fulfilled?

@angelo @yala @activitypods @nextgraph

Indeed, I need to revise my statement a bit. I thought there had been a decision taken on that (also LWS seems to go that pathway). There is an open issue and a pathway to create mappings from http URIs to NextGraph URIs. We don't have a test suite but that's planned for APods v3 :)

Tagging @srosset

@laurin @yala @activitypods @nextgraph @srosset ah I only got (halfway) aware of that discussion recently. Curious to see what the working group comes up with. For now I will stick with what Solid specified so far
@angelo @laurin @yala @nextgraph We document our standards support in this page https://docs.activitypods.org/architecture/application-interoperability/ and the following pages of the "Pods architecture" documentation
Application interoperability

Docs