Slack won: SlackBucket must be discontinued
Unfortunately, SlackBucket is being discontinued.
It's been a fun — and full of learning — journey. I got so many feedbacks about it that I'm 100% sure this is a wanted service. I knew that it would probably violate one or more rules of the Slack's Developer Policy.
The next day I released SlackBucket, I got an email from their legal team. Since then I've been discussing with them trying to fit SlackBucket in a green zone. We had an amicable and productive discussion. But the verdict is: As is, SlackBucket is violating Slack's policies and shall be discontinued.
But I got a green light about a slightly different version of the service, and I would like your feedbacks:
Instead of storing all the history, I can provide a tool to store important discussions in an external knowledge base selectively. In that external platform, users would be able to search, organize and evolve the knowledge. It would be like a smart WIKI fully integrated to Slack and other chat platforms.
What do you think about this tool? Would it be useful for you?
Thanks in advance for your feedback.
Definitely a great idea! :) I would recommend checking out the competition and finding a niche you can serve in a unique way: https://www.google.com/search?q=slack+wiki
Yeah, there are competitors already. I gotta find a niche.
Thanks for your contribution.
If you look at Stack Overflow for Teams, it has a similar slack integration that they just released. Not telling you not to do it, but that's the level of competition you're looking at.
Nice, I just found it: https://stackoverflow.com/teams/integrations/slack
Thanks for your contribution ;)
that is cool you were able to resolve. I'm going through a similar situation now with another well known company.
I agree with others than you new path may be even more appealing than your previous. Good luck with new strategy.
Well, I hope they are as amicable as Slack is. If you need any help, feel free to poke me.
Thanks :)
I like this new path. I find a lot of solutions on sites like IH, StackOverflow etc, but I don't know a good way to store them. I've tried Delicious, Pocket, Evernote, but anything has worked at all.
Although the service is not supposed to be a "read later" tool, I agree that it's possible to integrate it with all those services.
Thanks for your feedback!
"Read it later" is not a solution for this case. It's something that could help me bookmark "the best solutions" for anything. On Stack Overflow, people upvote and choose winner solutions. Here on IH, there are tons of good answers that could be bookmarked (or favorited/stared) but this feature don't exist yet. I can upvote but can't save it. On Slack is the same. I can star messages but I can't store them in collections. Got it?
Now I got it! Thanks for your feedback, Cadu! :)
That sounds like a cool new idea to play with! I think it's a big downside to the popular forum-style sites right now.
There are subreddits, chats, sites like IH, blogs, etc, where there is tons of great content flowing through every day, but the only way you can find it is through a google search.
I wanted to work on the idea of a more organized style that could help create structured data or learning paths based on user-submitted posts and replies, but never thought I'd get around to it :)
Good luck with whatever direction you choose!
Well, I would first integrate with tools used by teams and communities. There are tons of valuable discussions that must be organized in a searchable way. But definitely it would be good to integrate all such sites/services/tools :)
Thanks for your feedback.
Conflict was inevitable in this case because your service essentially undercut their paid version and made it redundant. If they would have allowed it then their paid service subscriptions would have been hit.
I think your your different version of the service is interesting and it would be useful for me and many others.
Using the free version of Slack, there are often some old conversations that I want to search for but can't.
Now I always try to star messages that I think might be useful.
How would your service differ from just starring a message? What would be the limits to your service? What if someone tries to store everything from Slack onto your smart Wiki?
BTW, if you want to be a beta tester, feel free to contact me ;)
Thanks for your feedback.
Yes, exactly. It would be like "starring" a message.
The difference is that the starred messages will not be in Slack's service. It will go to an external service, in which you can organize, edit and make it a complete knowledge.
I'm not sure yet. Maybe separate tiers by number of users (since there will have granular permissions).
Well, I don't think you would star every message. Since it required a minimal effort, you would filter what you would star. This way you would only have important discussions in your knowledge base.
This comment was deleted 6 years ago
Yes, exactly.
Slack is great for conversation, but it's not good to save and retrieve knowledge. This tool would incentivize users to save the importante conversations so that they can search later.
And yes, since it will be saved outside of Slack, there will be a way for users to edit and organize the saved messages. And to set privacy as well.
Thanks for your feedback :)