Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jan 27 22:52
    bourgeoa opened #333
  • Jan 27 22:51
    dependabot[bot] edited #331
  • Jan 27 22:51
    dependabot[bot] edited #330
  • Jan 27 22:51

    bourgeoa on move-logic

    update dependencies (compare)

  • Jan 27 22:51
    dependabot[bot] synchronize #331
  • Jan 27 22:51
    dependabot[bot] edited #331
  • Jan 27 22:51

    dependabot[bot] on npm_and_yarn

    Bump follow-redirects from 1.14… (compare)

  • Jan 27 22:51
    dependabot[bot] edited #331
  • Jan 27 22:50
    dependabot[bot] synchronize #330
  • Jan 27 22:50
    dependabot[bot] edited #330
  • Jan 27 22:50

    dependabot[bot] on npm_and_yarn

    Bump marked from 4.0.8 to 4.0.1… (compare)

  • Jan 27 22:50
    dependabot[bot] edited #330
  • Jan 27 22:50
    dependabot[bot] edited #331
  • Jan 27 22:50
    dependabot[bot] edited #330
  • Jan 27 22:49

    bourgeoa on main

    moved LiveStore rdflib with LiveStore version a… update dependencies and 4 more (compare)

  • Jan 27 22:49
    bourgeoa closed #332
  • Jan 27 21:17

    bourgeoa on v2.4.14

    (compare)

  • Jan 27 21:01

    bourgeoa on main

    update dependencies 2.4.13-bbf45639 2.4.13-bbf45639-1 and 3 more (compare)

  • Jan 27 21:01
    bourgeoa closed #69
  • Jan 27 21:01
    bourgeoa opened #69
vinnl
@vinnl:matrix.org
[m]
(I'll be going to be in a sec though, so might be a while before I reply.)
Daniel B.
@DanielBakas
Ok great. Thanks!!
Jeff Zucker
@jeff-zucker
See, I told ya Vincent would know :-)
Daniel B.
@DanielBakas
Haha right! Thanks Jeff!
Daniel B.
@DanielBakas
Hi everyone (again 😅) Is it safe to delete all folders inside my pod? I want to clean my pod but I don't want to delete any important files 😳
Jeff Zucker
@jeff-zucker
Don't delete anything in the pod root or podroot/settings or podroot/inbox or podroot/profile that you didn't create and you should be okay
Daniel B.
@DanielBakas
image.png
Any of these?
Jeff Zucker
@jeff-zucker
Oh sorry
My answer was very bad
I assumed you were using solidcommunitynet. I have no idea what is unsafe to delete in inrupt.com.
Daniel B.
@DanielBakas
Haha no worries. I'm just getting to know the project and the pods. All your answers help!
Thanks!
This interface should be more familiar
image.png
Jeff Zucker
@jeff-zucker
My guess is that you are safe deleting from /public/ and should proceed VERY cautiously with everything else
It is not just the interface that differs, those are two completely different servers with completely different implentations
Daniel B.
@DanielBakas
:O
But can the Node.js libraries access both using the same methods?
Or are they different altogether?
Jeff Zucker
@jeff-zucker
Inrupt.com = ESS (Inrupt Enterprise Server) ... solidcommunity.net = NSS (Node solid server)
What do you mean by the Node.js libraries?
These ones (from the tutorial) :D
Jeff Zucker
@jeff-zucker
but you're using them in a browser , not in nodejs, right?
Daniel B.
@DanielBakas
Oh! You're right. The photo I sent is from PodBrowser by inrupt. I sent those just to show what folders my inrupt pod had and to ask wether I could delete any.
But I am also developing my first web app using Node.js and the solid libraries from the tutorial
There's one method called "getSolidDataset" that retrieves a dataset inside a pod and it receives a URL
In the tutorial they use ".../profile/card"
And that's where I got confused on what folders (like profile) I should be modifying and which ones I should leave untouched :D
(That's how it all connects haha)
Captura de Pantalla 2021-07-10 a la(s) 6.45.45 p.m..png
Jeff Zucker
@jeff-zucker
Well, in any case here's the situation with servers : the Solid specifications are not finalized. For most parts of it that are finalized , either server should follow the specs so can be accessed with the same clients. But for parts that are up in the air, they could differ. For example ESS uses a very different access control system than NSS. As far as what files are on the server - that is not and will never be covered in a specification because Solid doesn't care if you store things as files or a db or anything else. That means that the specific files on the server are always implementation specific and will differ from one server to the other.
Daniel B.
@DanielBakas
I see
Okok cool
Does it matter where each user stores their data in their pods then? (regardless of the server the pod is in)?
Jeff Zucker
@jeff-zucker
But for most purposes solid-client should behave the same on either servere
Daniel B.
@DanielBakas
Okok cool. When I say where I just wanna say I mean "in what folders inside their pods"*
Jeff Zucker
@jeff-zucker
And the same with other clients
Well, you can store anything anywhere you like. But some apps will want to store things in their own places. That is handled in your settings type-registry that says type of data X (e.g. a bookmark) is stored in folder Y. Apps should read that registry to find where to look for stuff. If it's your own stuff that you are serving with your own apps, put it anywhere you like.
Daniel B.
@DanielBakas
Wuuuuu thanks so much. So, if I understand correctly, if my application is called "Semantyk" I could create a folder inside each user's pod by that name (semantyk) where all relevant information that my application consumes is located?
Jeff Zucker
@jeff-zucker
Yes, for most purposes, that would be polite.
At least for stuff that is only accessed by your app
Daniel B.
@DanielBakas
Awesome!
One more and I'll get on with the work. Should this "semantyk" folder be inside "public", "private" or the root directory?
Jeff Zucker
@jeff-zucker
If your app access common resources like inbox or profile, those would be outside your app-specific folder
Daniel B.
@DanielBakas
Right!
Jeff Zucker
@jeff-zucker
Well you can't count on there being directories with those names, so just make sure that wherever you put it, you make a pointer to it in the type index. Your app will need write permissions to the folder you want to store stuff in, so public may be a better option
Daniel B.
@DanielBakas
Awesome. Best put it in the root directory
Jeff Zucker
@jeff-zucker
Personally , I'd rather not have my root directory crowded