Code of Conduct: https://github.com/solid/process/blob/main/code-of-conduct.md - Website: https://solidproject.org/ - Repos: https://github.com/solid/
Aug 11 2021 20:52
@RubenVerborgh banned @mikeadams1
Jan 04 2021 20:23
@RubenVerborgh banned @WebCivics_twitter
Jan 04 2021 20:18
@RubenVerborgh banned @SailingDigital_twitter
May 27 2019 06:08
User @Mitzi-Laszlo unbanned @in1t3r
May 23 2019 06:49
@Mitzi-Laszlo banned @in1t3r
May 16 2019 09:49
@Mitzi-Laszlo banned @mediaprophet
Feb 01 2019 22:04
User @melvincarvalho unbanned @namedgraph_twitter
Feb 01 2019 21:49
@melvincarvalho banned @namedgraph_twitter
Is there an app you recommend that can demonstrate Solid? I find Liqichat quite amazing, but not sure if there is a better one
Also I've got a question - Does the programming model of Solid app allow it to be embedded in a non-domain'ed environment, such as localhost? Most of the users of my project does not own a domain. They self-host a number of traditional apps on their own device. Not sure how Solid fit in this paradigm.
Additional, is Solid's concept comparable to ActivePub based Fediverse, such as Mastodon or PeerTube?
@all - I am creating a list of Solid open source repos for solidproject.org - if you know of any repos other than github.com/solid/*, please let me know. This could be commercial organizations as long as the code is open source.
These should be team repos, not individual app projects
Is there some documentation or examples someone could point me to of organization-owned pods? Having some difficulty understanding a more enterprise-centric Solid setup.
Probably the most basic question I have is less about Solid and more about how an organization sets up and manages a WebID? Then how it would go about delegating rights to a Pod for employees or partners.
@KamiQuasi We are modeling an organization as a Digital Twin of itself with its own webid and pod, and org structure below that. https://graphmetrix.com/trinpod
@KamiQuasi - it sort of depends on what kind of site you want - would each employee have their own pod, or just containers within the company pod? Either way you'll want to use vcard:Group structures to create lists of employees and partners and then you can use those lists to permission parts of the pod.
@gibsonf1 - does graphmetrix have any open source repose available?
@jeff-zucker associates would definitely have their own pods. I've got so many ideas for usage internally for Solid, so I'm trying to figure out the corporate management of things a little before I try to communicate the ideas. Then I'll work on some of the apps.
@KamiQuasi - I'm glad to bat around ideas, this area of how organizations use Solid is also of great interest to @timbl
Full transparency, I work for Red Hat, so I'm not without some amount of bias for marketable solutions to bring back to the company, but always want to default to open first.
It would be superb to have Red Hat using Solid in any way it can. Let us know how we can help!
I have smaller organizations on my mind (and heart) too. Local Parent-Teacher Org for my children's school, private swim and tennis club, and local little leagues that I volunteer for could very easily leverage Solid for their membership and business activity.
Thinking from a starting point of CSS, I guess I didn't understand how one would set up an organization using that?
Those are great usages too.
Well, to start small, you could create two users on your local CSS, one an organization and one a member. On the organizations pod, create a container and permission it for access by the member. Thereafter the member should be able to read/write or whatever you've given them permission for. You can then expand that by making more members and making a vcard:Group of them and assigning permissions to the group.
You can have public-facing pages with public-read and then member pages only they and the organization can read.
It it just expected that an organization has a single point of contact via an email address? I'm trying to figure out that angle, because that seems less enterprise-y. I don't know what the alternative would be, because somebody obviously has to create the WebID for the org, but then it seems like a password has to be tossed around to manage it.
You can have a single WebID for the organization and only give that password to one person. Then your editors get WebIDs of their own and the main account gives them control over various sub-parts of the whole site. So only one person logs in as the main WebID but uses it to assign rights to other authorized WebIDs. Make sense?
You can assign other WebIDs to have Control+Write rights which means they can pretty much do anything in that portion of the site they have that right to.
Not too different from only having one person with root perms
Makes sense. I figured that is how it probably worked. The governance aspect of it for that root user is what always gives me pause. The whole, "What if they leave the org?" aspect.
As long as they don't leave mad :-). You could get one org WebID and use it to assign rights to everything to a manager WebID. That way, even if the manager left, your main webid could revoke their rights and establish a new manager
@gibsonf1 - thanks - how about if you submit a PR to the repositories page when you get it populate?
If you could answer the question “Why Solid?” in a single phrase, what would you answer? Happy wednesday! 🌞
My phrase: "Digital Enfranchisement". I want it for myself, and I want it for others.
Compile, manage and reuse your data - regardless of where it is stored
that's a good one, Tom. sufficient for twitter but maybe a bit complex ;-)
Love all. Trust a few. Do wrong to none.
@/all I want bring to everyone's attention here involved in the Solid project that India has come out with a new draft Data Privacy Law known as Digital Personal Data Protection Bill, 2022https://www.meity.gov.in/content/digital-personal-data-protection-bill-2022. This replaces the very contentious Personal Data Protection Bill 2018 which was scrapped after widespread criticism, but, retains many of the contentious clauses. This Bill will have a direct impact on the service providers and end-users of the Solid project. Along with this Bill the relevant Ministry has started a process of "public" consultation—first item at https://www.meity.gov.in/data-protection-framework . India will be largest market in the world and would likely have an extremely large cohort of Solid uses. Therefore, I would urge folks at Solid and Inrupt to seriously consider responding to this consultation!
Hi All. [FYI] I created an issue solid/specification#487 regarding addressing legal compliance, security, privacy, etc., which includes a link to my article where I explore the gaps between Solid and GDPR, known problems being applicable, and some ideas on moving ahead. Please let me know if you have suggestions, feedback, criticisms. I'm not typically online on Gitter, but I will attempt to check messages here once a day. Thanks.
Hi everyone! Interested in reading about the pros and cons of NSS vs CSS (I’m sure a debate as old as time, but somewhat new to me). Any interesting ideas on where to start? 🤓
I’m particularly interested in having a domain in a WebID. Something like danielbakas.com#me for myself or semantyk.com#us for Semantyk (our project)
Thanks a lot! 🥳🙏🏽
P.S. Posted this at the forum for anyone interested in the specifics of what I’m looking into right now regarding deploying a Solid Server on Google App Engine 😋 Thread
@danielbakas basically CSS largely supersedes NSS
NSS is still maintained, but from what I understand it a lot of people are trying to migrate to the more modern codebase of CSS.
Awesome! I did end up choosing CSS for now 😋 Thanks @ThisIsMissEm
There is a W3C Solid Community Group Special Topic Call on Use Cases on 2022-12-14: solid/specification#488 . All welcome.