Message max size vs. auto fragment
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Looks like there is a max message size that is not particularly large. I exceeded it posting a page or so of archived text.
Most messages are probably short, and that’s great. On occasion though longer message support would be useful, or at least some sort of message fragmentation like some other apps do.
Example: when sending a long message in the iOS messages app, if an iMessage it just sends it, but if sending a sms it will fragment it and send multiple sms messages to get the whole thing sent. Note that they seem to sometimes mess it up and clip some of the original... don’t do that 🤪
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
The issue names no files, tests, or entry points. Start by locating the current message-size handling, then assess whether larger messages or fragmentation can be supported without clipping; done means long messages are delivered in full.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100