---
# System prepended metadata

title: SolidOS Team Meeting

---

# SolidOS Team Meeting

* Date: 05.10.2023 18:00 (UTC+2)
* Call: [https://meet.jit.si/solid-operating-system](https://meet.jit.si/solid-operating-system)
* [Previous meeting link]()
* [Next meeting link]()
* Chat: [https://gitter.im/solidos/solidos](https://gitter.im/solidos/solidos)
* Repository: [https://github.com/solidos/solidos](https://github.com/solidos/solidos)
* Meetings home: [https://solidos.solidcommunity.net/public/SolidOS%20team%20meetings/](https://solidos.solidcommunity.net/public/SolidOS%20team%20meetings/)
----

## Present attendees

* Alain, Jeff, Noel, Aad, Angelo, Jon, Sharon, Rahul, Matthias, Rui

### Scribes

* Angelo
* Aad

---

## Topics

### Round Table

#### Sharon

- Working on tests, have some questions for Alain (discussed in technical)
- Worked on chat pane.  Wants to see demo of Alain and then discuss.

#### Aad

- Checking with Matthias how to deploy Pods via docker
- Exploring fault tolerant ways


#### Angelo

- Nothing specific on SolidOS or PodOS this week

#### Jeff

- Moving all his components to Web Components
- One set based on SolidUI and one based on Mashlib
- Using the spec for web components handmade :)
- Angelo uses Stencil, but it compiles to web components so it should be compatible with handmade.
- Future
  - Will compare Stencil Angelo is using to what Jeff is constructing
  - Angelo: in theory these should cooperate transparently (but we'll see)
  - Jeff: agree we will find a way

#### Alain

- Working on singing messages: https://github.com/SolidOS/solid-ui/issues/546
- Issue is still open.  Waiting for input from Tim.
- Patch submitted, want to test with PodOS too (Angelo can do this)

#### Noel

- [Opened a PR](https://github.com/linkeddata/rdflib.js/pull/620) with some VScode settings to make it easier to run tests.  Have to decide what we want to include for VScode
  - Angelo: prefers to not have IDE specific settings in Git, but agrees it might help for onboarding.
- Tinkering with Nextcloud. The [Solid extension](https://github.com/pdsinterop/solid-nextcloud) does not support updating documents using SPARQL, which should be fine because the spec doesn't make it a requirement. Instead, it mentions text/n3 patches which are supported in Nextcloud. However, this seems [inconsistent with ESS](https://github.com/solid-contrib/solid-crud-tests/issues/60) where text/n3 patches are not supported.
    - Jeff: NSS supports both at this point.
- N3 vs SparQL in the spec need to discuss further. What does Rdflib.js do? Would it work with the Nextcloud extension? 

#### Jon

- Talked to Timea about documentation
- Jons ideas are more for Solid as a whole than SolidOS specific
- Working on a document: getting started with Solid, building apps, ...
- https://github.com/solid-contrib/getting-started


#### Rahul

- Trying to get sample data for new implementation
- Containers are not HATEOS compliant

#### Rui

- Exploring subdomain vs path users for group pods with [CSS](https://github.com/CommunitySolidServer/CommunitySolidServer).

#### Matthias

- Trying to dockerize SolidOS with Aad.
    - Alain: Can send his version of Docker setup
    - Angelo can also have a look

### Main topics

### Technical topics

#### Alain demo chat-proof

Chat message with signatures.  Works as smoothly as before.  Invalid signatures exist when key changes :thumbsup: .  Unsigned messages also supported.

cdsa fixed length version key.

Keys can be stored in the PoD.  Aad suggests we can make a resource to represent the combinatin of public and private key.

#### Sharon questions for Alain

Sharon presents her code for questions on how the key is created.

Sharon is asking about [some code that seems to create an empty key](https://github.com/SolidOS/solid-ui/blob/89f16fa3eace3704dbb183e58fe365e4676e6116/src/utils/cryptoKeyHelpers.ts#L66..L71) if it doesn't exist (but it shouldn't be empty, it should contain some data).

Sharon suggests some code changes to simplify the flow.  Alain explains where the key is generated which may help with that.

Is there a way to store the keys in a way that users cannot alter them?
- The users must have access to the keys some way.  We can only hinder accidental removal.
- Jeff suggests to store the reference to the write-protected key.
- Adding other keys could be nice, but hindering deletion would be nice.
- This is a first step and we can extend in the future.
- Sharon suggests we add a message to the container resource that contains the public and the private key.

Ontology was created for this and can have improvements.  security ontology and cert ontoolgy are used today.  We will look around for ontologies that describe public and private keys and that connect these together and should ask Tim or others if he knows of some.

---

This template is based on the [W3C meeting template](https://github.com/solid/specification/blob/main/meetings/template.md)

[Code of conduct](https://github.com/solid/process/blob/main/code-of-conduct.md)