@SharonStrats assuming you are following these instructions:
then it is odd that your
bin/solid-test is not marked as executable. Perhaps you are in a Windows environment?
The instructions for
openssl and creating a self-signed certificate are a little later in the docs above:
openssl req -outform PEM -keyform PEM -new -x509 -sha256 -newkey rsa:2048 -nodes -keyout ../privkey.pem -days 365 -out ../fullchain.pem
@Vinnl_gitlab Thanks for the feedback. I added some explanatory text to https://smartdown.solid.community/public/smartdown/#/public/SolidLDFlex.markdown:
Smartdown is a Markdown-compatible language for authoring interactive documents. It resembles Jupyter, but has a version-compatible source format, and requires no server to remain interactive. Good for experimenting with, integrating and discussing other technology.
Solid complements Smartdown nicely, by providing a place and an authentication scheme to enable controlled access (read and write) to this data.
FWIW, without decentralized linked data, email, chat rooms, comments, and even pages are basically not much different than what people used in the 1980s, we might as well be using dial-up BBSs (the 2019 level tech is behind the scenes working against the consumer). Git (like usenet before it collapsed) is a bit different because it is decentralized and works on a graph , but the interfaces to use it are very technical and it's prone to cause problems.
Git is effective because it requires rigour to use, which serves as a filter. But in this case it is being used, like the other forms, to produce transitory prose rather than articulated and finely reusable information.
There might be a discussion about what a solution and simplest implementation would look like that isn't copying BBS style media, that fully uses hypertext and decentralized, social linked data to allow people to finely subscribe to active topics, groups and people so that they can find information they need, discuss ideas, and participate in development without needing to use many different channels. Especially people who can't participate full-time in this specific project. That tool today is called google, but it uses guessificial intelligence and treats individuals as blobs.
The main thing I would propose is including easy, active and precise linking information as part of the communication system. An approach I have worked on before is a "spotter" which runs alongside the communication tool, and proposes links which can be accepted or shaped by community members as a participatory activity, so there are two levels, proposed and accepted, along with an information structure and curation system that is perfectly suited to linked data. I would pair this with a literate programming approach, which is again very suited to Solid since so much of the interaction is based in the browser.
Dokieli is fantastic, but from what I know prose-document focused. A few projects are implementing linked data components, which allow choosing other pods or information sources, and that would be a basis of distributed project development. Original human text is important, of course, but can be a problem when it's overwhelming. There should be every opportunity and incentive to include dynamic well defined views. I'm doing this with components embedded in markdown (mdx), and smartdown has an implementation based on this approach as well. The embedded approach can help solve the polish issue, since people can embed components and focus on their own style.
One immediate outcome is the regular This Week in Solid bulletins could be largely automated, with curated queries from different sources. Embedding task tags across repos would allow a very fine overview of ongoing activities.