Michael

@rosano To name another idea:

It's possible to define groups in Solid and give them access to a resource.

I am planning to use this mechanism to share the nutritional preferences from this app with a group. In the scenario that all of my friends use this app, I could request access to their preferences. When they decide to come over, or if we're planning to meet somewhere, then we'll have a lot more clarity on where to go or what to prepare.

My recipe planner also lets you filter a database of food recipes, by adding people's food preferences. If it's set up properly for everyone who's going to attend that meal, you just go to the homepage and it'll be pre filtered.

This saves a lot of time and frustration in common situations like:

1. You want to start a diet but telling everyone about it and what it entails takes time and increases friction.
2. If you're trying to less sugar.
3. If you don't like a certain ingredient.

Here is the post in which I shared some screenshots of my app https://techhub.social/@m5x5/116404776179740250

@rosano

1. You're welcome!
2. Yes exactly the scenario @colby is describing. In fact I also built a little web app at https://feedback.api.mpeters.dev but I haven't released the npm package yet, and I only used Solid during testing.
3. From what I remember, when I set it up a year ago I used your instructions on your flowerpot repo. When I learnt about remoteStorage last year I actually spent a lot of time on the websites you built, it's been very helpful and enjoyable, thank you!