clojureverse / clojureverse/clojurians-log-app
Capture images / attachments
- Dominant language
- Clojure
- Stars
- 85
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
When people share images on Slack we don't render that.
Compare:
This may become a bit involved since we will have to actually download and store the images somewhere on our side. Similar to the limit on message history, Slack has a limit on how many of these attachments it retains, so if we link to Slack they will soon break.
So capturing them and storing them somewhere (S3?) is really the first step, to stop us from losing this history. Rendering can come after.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by locating the Slack message ingestion flow and determining how captured attachments can be stored before Slack retention expires; the first milestone is reliable image storage, with rendering explicitly deferred.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100