MaddyUnderStars / MaddyUnderStars/shoot
better compatibility with non-Shoot software
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 61
- Forks
- 5
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 1
Description
Mastodon/Mitra/etc do not understand Shoot channels. Would it be a good idea to somehow detect if the remote supports groups, and if not then fall back to sending a normal DM? Or is there a way to instead support both without doing capability detection? perhaps by just setting the to field of a dm to all the recipients, and basically getting rid of the concept of channels at the dm level? or perhaps the to field could include both the channel, and all the recipients? so shoot can check find any channels in there, and do normal addressing, and other software can see all users in the channel and do it's own thing?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how Shoot channels are represented and sent to remote Mastodon or Mitra software. Compare capability detection with the proposed DM addressing alternatives: recipients, the channel, or both. Done means choosing and documenting a compatibility approach, with interoperability behavior defined for software that does not understand channels.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100