- Slack
- dialogue 、 flow 、 drift away
- stock must be changed to
- Wiki mode
- Types of Wiki Usage
- It would be nice if Slack conversations could be easily cropped, reordered, edited, and cleaned up.
- Permalink.] to each statement in the chat.
- If you want to know the context of the original statement, be able to trace (trace back) allows you to cut, rearrange, and edit without worry.
- But I don’t see that happening with Slack today.
- single-function orientation So? No, no.
- Known to be a flow-specific tool and users need a separate stock
- Then it makes sense to prepare an API to retrieve data or add a mechanism to automatically send the data to an external service via Webhook.
- Useful to increase [interoperability
- Then it makes sense to prepare an API to retrieve data or add a mechanism to automatically send the data to an external service via Webhook.
- And yet, only the API and webhooks that get information into Slack are enhanced, not the ones that get information out.
- Their business model is that if it’s free, you can’t go back beyond a certain amount, and if you want to go back, you have to pay for a paid plan.
- Strategies to hold information hostage and cause lock-in
- Mattermost
- Open Slack clone
This page is auto-translated from /nishio/SlackのビジネスモデルとWikiモード using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. I’m very happy to spread my thought to non-Japanese readers.