This forum should be central to Solid community, and not Gitter


I think the idea that those on the forum would work from a frozen version of what is a very fluid solid spec, and that there be little feedback or iteration, or need to adapt to spec changes, which are especially needed in the case of shapes for interoperability, is problematic.


sorry, I don’t think think sarcasm, ‘them and us’ and assumptions will help improve the communication…


Ok, thanks, I edited it…hopefully better now


yep, and I think you have a valid point! how do you handle shapes at the moment?


I’m not coding now, sadly, but I hope to get back to it sometime. What I had in mind are shapes for chat apps so that hopefully someone can make one that can interop with other chat apps and maybe use that really cool Say editor :slight_smile:

So this is a good example of possibly improving the synergy between different parts of the community. Maybe some shapes for interop could be put out there, with the understanding that they will change, so that devs here can start to incorporate them and anticipate changes. Without expecting the shapes to be perfect or final on the first iteration.

Improving synergy between different parts of the community

I think bridging is the best answer, but it could take many forms, broadly:

  1. Human (active cross-posters, etc.)
  2. Modification of content (annotation, linking, etc)
  3. External service (summarizing, topic identification/monitoring, etc.)
  4. Full-blown knowledge base with automatic/assisted concept extraction

This is actually an important general problem IMO.


The aforementioned discourse2gitter plugin looks like a good low-effort option to me, for starters.

It would serve to notify core members of all ongoing forum activity.


I’m not saying don’t try it, I think it’s a good idea but I think we would have more chance with buy in from more of those closely involved in and particularly directing development of Solid. I can’t understand how Inrupt can put itself in a position of de facto owning the development of Solid and much of its ecosystem, also the main communally resources (such as the forum, and gitter moderation) without being much more transparent, or engaging with the community when we ask about certain things. I asked to discuss this separately from this particular question but that was met by silence, and I think this is a pattern which is a significant causal factor in what we trying to fix in this topic.

Cross posting/bridge will help raise awareness. Having the people who are involved in development, and particularly the big hitters hanging out here and engaging with questions about the direction of Solid and answering when people ask questions that the community cannot, is necessary for the forum to get established. I think we probably lose people when questions are not answered about strategy, plans, and security or privacy concerns. Not just those who ask, but those who see this.

We’ve see it again in this thread. In my view it undermines their credibility, and affects respect, commitment and morale in the community. In that respect I think it’s an anti pattern.

That may sound strong. The reason I feel strongly is because I believe in the goals of empowering people, restoring privacy and autonomy, and building the open, accessible, democratised internet for everyone, and I’m concerned that the issues raised here jeopardise our ability to improve those things with Solid.


The goal should be long term to get both forum and chat onto solid-based equivalents, of course. I to a certain extent have made my peace with gitter in that I have written code to keep a solid archive of chats I follow including solid/chat. I did this because I was worried about a few things about gitter – that it was not standard, that could disappear with all the community knowledge with it.
Anyone else could do the same. Also we could look at ways of just syncing parts of pods, like those chat archives. I guess @happybeing you could take a copy of everything on SAFE or IPFS for that matter.

(Of course a nice tool would be one which extracts a long thread from gitter and reformats it as a forum post… but that would need root on both sides to be able to map different user’s comments and simulate their posts on the forum. Or it could do a sort of quote the original poster’s names for it like matrix-gitter bot does.)


Yes, really long-term. Imho dogfooding Solid for its own toolset is a nice-to-have at best and should be really low-priority. I created this thread (and others before that) to indicate way more urgent issues for the Solid initiative:

  • People don’t get Solid, and it is still not clearly positioned.

  • Tools and communications are fragmented, making it easy to miss ongoing activity.

    • Three landing pages for Solid (,, If you ask me should be the main entrypoint to Solid. The MIT site should redirect to it, and should be differently positioned (as it tackles the commercial side of things). Inrupt cannot be central (again wholly imho).
    • Nineteen (!) github repositories for Panel discussions. Why aren’t these taking place on this discussion forum? (Note that Discourse has github integration plugin, so you can still have work documents there).
    • Gitter has the core team interacting
    • This forum has some community member discussion
  • Solid is not actively reaching out, onboarding, building community, and hence has a high barrier to entry

    • A bunch of articles promise revolutionary change (exciting!) but landing pages offer little info, spec is mostly empty, etc.

Since I started monitoring Solid over a year ago I have seen numerous people getting confused, disinterested or getting a ‘Solid, meh’ impression. And in this thread I got the impression that among invested community members there is a lot of frustration not being addressed.

It could well be that there is a well-founded strategy behind this. Might also be that commercial activities take precedence. Whatever it is, to me it seems worthwhile to discuss more openly, and tackle the issues (or provide pointers if that already happened).

Edit: I am delighted to find more solid information on so that’s moving in the right direction.


I think aside from Inrupt’s commercial focus, which is as to be expected since its a market funded startup, the problems have to do with spec issues. Since Solid connects the desktop with the web, the spec necessarily has all kinds of intricacies and corner cases. I think this is being addressed but the number of spec issues (imho) came as a surprise. Also, the concepts of user level programming (as explained in and ) which also are pretty revolutionary, are added to the mix at the same time. Maybe some sort of iterative spec-design-implement-spec process with a more focused group is needed. I thought the panels were a great idea but they seem to require a commitment that is beyond what part-timers can deliver, and a lot of spec issues span different panels.

Also I think Solid needs a white paper, a yellow paper, and a beige paper.