Research Increasing Support Forum Post Character Limit
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 912
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 58
Description
See this post in the contributor forums for context. The tl;dr is that pastebin.m.o is slated for retirement and without another pastebin recommendation the support forums may need to support larger posts to accommodate the info copied from about:support.
My initial thoughts are that we should keep the support forum character limit and find an alternate recommendation for a pastebin. Our database is already huge and increasing the amount of data stored and served by those views doesn't seem like a good direction for us. I might even prefer that we stand up a support pastebin with auto-expiry of posts rather than recommend this content live in kitsune itself. But, I'm willing to be convinced otherwise.
All suggestions are welcome.
/cc @jgmize @metadave @jpetto @glogiotatidis
Contributor guide
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 linked contributor forum post and reviewing the current support forum character-limit behavior. Compare the proposed options—retaining the limit with an alternate pastebin, increasing the limit, or using an auto-expiring support pastebin—and document a decided recommendation; no implementation files or tests are identified.
Written by the indexing model from the issue text.
Assessment
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100