Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Sep 16 15:12
    bourgeoa synchronize #297
  • Sep 16 15:12

    bourgeoa on auth-upgrade

    v3.5.6-alpha-d9bd19aa (compare)

  • Sep 16 14:23
    bourgeoa synchronize #65
  • Sep 16 14:23

    bourgeoa on auth-upgrade

    v2.4.11-alpha-d9bd19aa (compare)

  • Sep 16 13:45
    bourgeoa synchronize #420
  • Sep 16 13:45

    bourgeoa on auth-upgrade

    update @inrupt/solid-client-aut… (compare)

  • Sep 16 11:06
    bourgeoa synchronize #297
  • Sep 16 11:06

    bourgeoa on auth-upgrade

    v3.5.6-alpha-2b12f04c (compare)

  • Sep 16 08:59
    bourgeoa synchronize #65
  • Sep 16 08:59

    bourgeoa on auth-upgrade

    v2.4.11-alpha-2b12f04c (compare)

  • Sep 15 10:04
    bourgeoa synchronize #420
  • Sep 15 10:04

    bourgeoa on auth-upgrade

    tweak the way checkbox values a… pushState seems to want a title pushState seems to want a title… and 1 more (compare)

  • Sep 15 10:04
    bourgeoa closed #430
  • Sep 14 19:00
    timbl opened #430
  • Sep 14 18:57

    timbl on authn-fix-pagejump

    pushState seems to want a title… (compare)

  • Sep 14 18:54

    timbl on authn-fix-pagejump

    pushState seems to want a title (compare)

  • Sep 14 06:51
    jaxoncreed synchronize #420
  • Sep 14 06:51

    jaxoncreed on auth-upgrade

    Trigger logout route when you l… Merge branch 'auth-upgrade' of … (compare)

  • Sep 13 15:27
    bourgeoa synchronize #297
  • Sep 13 15:27

    bourgeoa on auth-upgrade

    v3.5.6-alpha-3-98ed3958 (compare)

Jeff Zucker
@jeff-zucker
The user can always change the access permissions. Your app will need to ask the user what permissions they want to grant. That info is stored in the user's profile under trustedApps.
Daniel B.
@DanielBakas
This is so cool
Jeff Zucker
@jeff-zucker
Yes, asking is nice :-)
Daniel B.
@DanielBakas
Thank you so much for answering. This community is amazing
Jeff Zucker
@jeff-zucker
Glad you're a part of it :-)
Daniel B.
@DanielBakas
🥺😭😩🙏🏽

So if I understand correctly:

  1. My application will request the creation of a new "semantyk" folder inside a given user's pod
  2. The user will have the ability to accept or decline this request.
  3. If the user accepts the request, a new folder named "semantyk" will be created inside the "public" folder of the user's pod
  4. My application will be able to read/write to this folder to work and provide the user with the
    application's experience.

Correct?

Jeff Zucker
@jeff-zucker
The user will need to agree not only to the creation of the folder, but also to the rights they wish to grant your app. So they'll need to grant your app read, or append, or read+append, or write
Daniel B.
@DanielBakas
This needs to be shared with everybody. This is the way the world should treat data
Jeff Zucker
@jeff-zucker
Yep
Daniel B.
@DanielBakas
You guys are inspiring and generous. Thank you so much Jeff
Jeff Zucker
@jeff-zucker
Glad to help.
Daniel B.
@DanielBakas
🌱
vinnl
@vinnl:matrix.org
[m]
I don't think that permission model is described in the spec, and only NSS (inrupt.net and solidcommunity.net) implements it as far as I'm aware. Generally, my current strategy is indeed to just create a folder at the root of the user's Pod. Should cause least problems with e.g. other folders (like /public/ or /private/) not existing. That said, I tend to work on apps that only store data for the user themselves, i.e. that they're not sharing with others.
Daniel B.
@DanielBakas
This is a great answer too. Thanks @vinnl:matrix.org!
What do you guys think? Should our applications' folders be located at the root directory of our users' pods, or inside their "public", "private", etc. folder?
Alain Bourgeois
@bourgeoa
I there is absolutely no rule.
Jeff Zucker
@jeff-zucker
It should be located somewhere an app can find it by following its nose from the user's profile.
Alain Bourgeois
@bourgeoa
But personally I don't like any app to write directly in my user root folder. It more to keep it clean and have a one level of folder with ACL I can managed touching root the least possible.
Jeff Zucker
@jeff-zucker
^^Me too.
Nick Form
@nickform:matrix.org
[m]

In the blog post linked below, Ruben Verborgh discusses something called "footprints" as a solution for the problem of where apps should store new data. I think there was a similar blog post by Tim Berners-Lee that discussed this but both are a couple of years old now and I'm not sure whether the idea went any further. May be useful background though.

https://ruben.verborgh.org/blog/2019/06/17/shaping-linked-data-apps/

Daniel B.
@DanielBakas
Is there a standard though? Or does every application developer decide where to store their applications' data inside each user's pod?
Jeff Zucker
@jeff-zucker
AFAIK, no, there is no standard on this. What I would like to see is ability to have a triple in my profile that tells apps the root folder for app data. The spec shouldn't specify a location, just a method for the user to specify a location.
OTOH, since everything can be read/write the distinction between "my data" and
"data acceessible to apps" may be meaningless or an anti-pattern
Daniel B.
@DanielBakas
But application folders could still show in the users' tree and be intrusive or invasive. Should we promote the creation of a standard for this?
Maybe just one folder in the root directory called "AppData" or smth
Where all our application data could reside :D
Jeff Zucker
@jeff-zucker
You can read through the specs, join in the discussions on them in the issues and PRs off of that or join the spec chat. Not much in the spec is related to "location".
Daniel B.
@DanielBakas
Great! I'll take a look. Thanks Jeff!
vinnl
@vinnl:matrix.org
[m]
As far as I've heard footprints are what people are thinking the solution is going to be. But they're not here yet. Practical choice in terms of getting something out the door now is just picking a location and going with it, IMO.
Jeff Zucker
@jeff-zucker
Generally things should be seen as semantic relationships, not as file/folder locations. I agree with @vinnl:matrix.org ^^
Daniel B.
@DanielBakas
Perfect! Thanks guys!
Fred Gibson
@gibsonf1
Actually @DanielBakas You could start the idea with your app and create first AppData and then a sub-container under that
maybe it will catch on
Daniel B.
@DanielBakas
Thanks Fred! I wanted to know what the community thought first, maybe we can do something together to tackle this problem and therefore establish a precedent for specification :D
This way new developers will know where to place their apps inside pods
:D
Mark Foster
@mikcaweb
Is anyone working on any SDKs around Native Apps for Solid? Something like React Native, Flutter or others. https://expo.io/ looks interesting. Any thoughts?
vinnl
@vinnl:matrix.org
[m]

@mikcaweb (Mark Foster) I think @jaxoncreed's Liqid Chat app uses Expo: https://github.com/o-development/ochat-client/

It appears to have a couple of weird issues like scrolling being in the wrong direction on some platforms though.

LievenVDP
@LievenVDP
We are currently about to kick off development on an application which will use SOLID heavily. The application will have search and matching functionality and thus we will need to keep certain data cached on our end to perform these actions. I would like a way where i could register a url with a pod provider and the provider would call that url when access gets revoked (so i can clear the stored data we used for searching on our end), sort of like a simple webhook. The alternative is that i would have to test for connections every x time which seems like alot of overhead for such a simple thing. The other thing we would really love to see is a way to trigger pod registration through our application with an api or something where the service would then send the info back to us . We want all our users to use the pods but our fear is that without a seamless integration the use of SOLID would scare away alot of potential users.
We would be interested in helping develop these features Is there animo for these features (to us these seem like basic features most commercial implementations would need) and who would i need to talk to about this further? Are the pod providers using the open source code from the node-solid-server or are their seperate codebases going on?
vinnl
@vinnl:matrix.org
[m]

Hi @LievenVDP (LievenVDP), there's definitely lots of demand for the post-registration-redirect. For both things, it's probably best to bring it up for the specification, since otherwise app developers can't assume people's Solid servers will support it: https://gitter.im/solid/specification

Besides NSS, there's a more actively maintained (but not yet as feature complete) server implementation at https://github.com/solid/community-server

Other than that, inrupt.com uses Inrupt's proprietary server implementation. I think trinpod.us also has their own proprietary server implementation. And there's a PHP implementation and Nextcloud plugin at https://pdsinterop.org/.

(Hence, the importance of standardisation :) )

LievenVDP
@LievenVDP
hi @vinnl:matrix.org thanks for the info, ill move my question the specification channel then ;)
Mark Foster
@mikcaweb
@Vinnl Thanks I will reach out to @jaxoncreed
Daniel B.
@DanielBakas
Hi everyone! Couple of questions. Should our Solid applications consider multi-factor authentication or maybe just alternative forms of authentication? If so, where would all the data come from? Are there ways to create pods for users from our applications if they don't provide one?
vinnl
@vinnl:matrix.org
[m]
Multi-factor authentication is primarily a question for the user's Pod Provider, i.e. if I open an app and connect to my Pod at solidcommunity.net, then the screen at solidcommunity.net could ask me to authenticate using a second factor, or using an alternative form of authentication. As for creating a Pod from an app, see LievenVDP's question above - it's not possible yet, but you're not the first person looking for that :)
Daniel B.
@DanielBakas
Oh cool! Thanks @vinnl:matrix.org :D
It's a matter of time then (hopefully)
Daniel B.
@DanielBakas

Hi guys! Question here about shared resources. I'm interested in developing an app for the exploration of stories and narratives. We, as humans, share these stories. They don't belong to anyone in particular.

  • Where should these stories and narratives be stored (in whose's pod)?
    And
  • How could they be made available for everyone to own them collectively?

I think it would be very beautiful if we all owned the narratives we share :D

vinnl
@vinnl:matrix.org
[m]

That's up to your app to decide - where you think users would want them to be stored.

But I think you might want to talk to the Understory people, who I think have pretty similar ideas; See https://www.understory.coop/ and https://understory.garden/. (/cc @travis)

Daniel B.
@DanielBakas
Awesome!! Thanks for the reference @vinnl:matrix.org :D