Every week or so we have a discussion somewhere on Slack in which a member complains about some aspect of the service (this week was the lack of message retention; last week was rendering; the week before was message retention, …). This usually turns into a bunch of people suggesting alternatives and getting shot down because of perceived technical deficits in whatever platform is being suggested.
I promised in one of the previous gripefests that I’d put this up here: the thing that bugs me about these conversations (besides their frequency and their predictability) is that we never actually get to listing the features we as a community want in a real-time chat system. All we get is “X doesn’t do Y, therefore we won’t consider it” – but the default is using a system that doesn’t do Y, or Z, or A, …
So here’s the thread I promised to start last week. It is to hash out a prioritzed list of desired technical features for a real-time chat system, not to propose alternatives to Slack. Without knowing what’s important, we can’t explore options that meet the majority of the users’ needs.
So, have at it. Again, requirements only, please. No solutions at this point.
So far (I will add or create new polls as people suggest other features, so scroll down to make sure you’re seeing all the options):
- web-based client
- os-specific client
- mobile client
- Markdown support
- LaTeX (or derivative) support
- OAuth support
- 2 factor auth support
- long (unlimited) message history
- file upload capability
- giphy integration
- open source
- ability to access through most reasonable corporate firewalls