SolidOS / SolidOS/solid-ui

Chat thread with signed messages

Open
#546 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
153
Forks
46
Avg merge
1d 8h
Merged PRs (30d)
7

Description

Tasks :

  • manage pod keys

    • ontologies
    • create keys :
      Schnorr alg and secp256k1 elliptic curves ( key is 64 bytes length). more recent tan ECDSA on same elliptic curve and shorter keys
    • Keys URI location and content:
      • publicKey parentSettings/profile/keys/publicKey.ttl
        triple => :me solid:publicKey keyString # keystring is 64 char hex string
      • privateKey parentSettings/settings/keys/privateKey.ttl /settings/ is discovered from WebID preference file
        triple => :me solid:privateKey keyString # keystring is 64 char hex string
      • parentSetting is used for both Keys URI location
    • secure keys with READ only on key resources and acl:default Read on key container
    • repair publicKey keeping private key
    • add key type description ? SS256 + SHA256 ? where ? JWT or JWS ?
    • a WebID could have multiple key/keyPairs. Through using different key URIs
  • chat logic

    • proof on default object message (id, date created, content, maker)
      replacedBy, deleted and threads are not included. These should link to new signed things
      This is not actually the case for deleted
    • add thread logic. Thread members property.
  • chat channel

  • sign and verify object message. Cover Threads

    • simple message
    • edit message : replacedBy => sign new msg + verify same maker
    • deleted message => verify the triple with a second signature or create a new thing.
      and verify same maker. There is actually an optional parameter
    • links to new messages. Not needed
  • UI

    • UI signed message with verify = false
    • UI for unsigned message
    • thread
  • tests

  • push key management in solid-logic ?

  • documentation

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the remaining checklist items for key type descriptions, tests, Solid Logic key management, and documentation. Start with the existing key locations under profile/keys/publicKey.ttl and settings/keys/privateKey.ttl, then inspect the chat signing and thread work referenced in the issue. Done requires resolving the remaining tasks and adding the missing tests and documentation.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.