SolidOS / SolidOS/chat-pane

Assign topic (URL) to a chat

Open
#106 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
10
Forks
5
Avg merge
2m
Merged PRs (30d)
3

Description

When starting a chat (or at any later point), allow the user to optionally specify a topic (URL). This would make chats discoverable by topic and help relate different conversations.

Use properties like schema:about, foaf:topic, dcterms:subject, as:inReplyTo, sioc:reply_of, or similar.

While playing with dokieli's notifications feature - which surfaces activities and interactions from both my contacts and myself with the current document - I realised this could also be used to discover chats related to a page and display them in the notifications side panel. This is conceptually similar to how Activity Streams uses object or target, depending on the activity type.

For example, if I can locate Tim's LongChat via his TypeIndex (assuming I have access), and identify the one tied to a specific topic, I could show that thread in the side panel. The user could then read or post new messages from there.

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

Start by reviewing how chats are created and located, then read dokieli's notifications feature and the TypeIndex discussion referenced in the issue. Compare the proposed topic properties and Activity Streams relationships before deciding how a topic should be stored and discovered. Done means a chat can receive an optional topic URL and related conversations can appear in the notifications side panel.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend-api-design, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.