MaddyUnderStars / MaddyUnderStars/shoot
attachment federation
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 61
- Forks
- 5
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 1
Description
I've implemented attachments (roughly), but haven't federated them yet. It shouldn't be too hard, but will need to store some more data about attachments in the message object. I could make the message to ap note transformer async and get the metadata from s3 or whatever there, but I'd rather not make it async
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 reading the message object and the message-to-AP Note transformer, then trace how attachment metadata is currently stored and where federation consumes it. Define the additional attachment data needed in messages and confirm that attachments can be federated without making the transformer asynchronous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100