Also, we need to think of running this at scale. So I believe it would be good if we can get on a slack plan. I saw discussions on getting on to different platform. Don’t know if we have taken any decision.

So, we've been thinking about a slack plan on and off. The cost might be prohibitive if I could say. And if we asked people to pay for the license (which is per user), I'm not really sure how many would cough up.

I echo what @straight-continent-34777’s thoughts. I don’t think any other platform has been enticing so far as to make us really think about moving (which comes with it’s own substantial cost in movement of folks). And unless Slack is sponsoring, it is going to be really expensive running this with Slack Pro. Remotive which is a paid community, still uses the free Slack plan. I think for us, the issue is that lots of discussions we have here (as compared to Remotive, say), are valuable months later as well. So that is why it gets difficult over the long run and the 10K messages are beginning to hurt now.

There is one way to do it though - The community will be closed out and the subscription to the community will involve the slack charges - we can however go for the indian plan. India has slightly better rates compared to slack paid internationally

@straight-continent-34777 agreed. Not easy to run communities with that kind of cost.

@straight-continent-34777 @loud-glass-33663 Discord is unlimited for the features we use. And some extra perks, at no extra cost. https://mule.substack.com/p/dark-horse-discord

Agree that the tool is totally awesome. Who will make the effort of moving everyone And the data over?

yes adding to it, it doesnt fit everyones normal stack. If its slack the majority of the members already use it for some form of communication so its not extra effort to communicate here. if its two platforms trying to achieve the same thing, its very difficult for the user to switch between the two and this being a proactive community the participation could go down as well 😞

Yes, a few communities went on discourse and noone has time to check those - slack ones keep staying as it's just easy and quick for all For any threads/conversations that are very useful, just tag it and add to a new blog - simple

If we want to be here and want full features, the only way is to cough up more money

😈 or build a scrapper and searcher bot

Nahh mate, just use it as is - Nomadlist is a paid product and they don't use subscriptions - who needs to go back 10K+ messages?

@swift-pilot-25722 Thats the irony there. unfortunately @crooked-daybreak-310 explained about why we needed more than 10k messages, some months back when we had the same conversation and that is wiped out because of the limit. So guess that explains it enough 🤷‍♂️

Hey Aravind, Thanks for raising this topic. I have been thinking about it as well. I feel the time has come to have 2 spaces in the community. 1. Slack group - For the transient conversations, networking and outreach for help. 2. Website backed by wiki - This is where the content which needs to be referred by multiple people over multiple points of time can be stored. Something like https://roadmap.sh/ where folks can raise pull requests on GH to make sure the content is up to date. What do you think?

On point 2 - I'd imagine there's some bot that could be commanded to send a specific conversation string to a wiki bot of sorts.

The Bot route can definitely be taken up. Push the conversation to a thread elsewhere is something I've seen this on a few other slacks I'm part of as well. Needs to be worked out though! That is effort someone has to put in.

@straight-continent-34777 yes right. I started this long ago and I didnt proceed after that at all. Its actually a simple enough script/ API calls. Could start as simple as jut backing up the data/conversations every day. One problem, we can do so only for set channels. Cant do it for DMs

DMs are a private thing. Let’s try one step. We’ll see how that lands.

As far as I just checked the API there are two ways, We can do a regular dump of data through channel history API and pull all conversations and dump it in our db. or we can send it via events as and when messages are sent on channels. Seems to me the second option is much better in terms of rate limiting during requests. anyways should do more research. might work on that this weekend and lets see where it goes. https://api.slack.com/events/message https://api.slack.com/messaging/retrieving

Looking forward!