tech404logs VS slack-ruby-client

This is interesting to see, and reminds me that I really have no idea how to sell myself. I spent 7 years on this exact thing--a project to archive a community Slack server to an crawlable website, even with full-text search that (IMO) worked better than Slack search. I made the code available for other communities to use, and never once considered that this was a sellable product. I shut it down this year after a flurry of folks started asking to be opted out of the archive.

In case you want to run your own: https://github.com/zacstewart/tech404logs

Ah, I'm surprised Slack doesn't support Ruby, but to be fair they are pretty tight on official support with only Python, Node and Java.

Fortunately there's https://github.com/slack-ruby/slack-ruby-client, but it's not official. Although it seems to be a good example of a community driven library coming together. I haven't used it personally (I never interfaced with Slack in a Ruby app) but at a glance it looks like it has really good docs, a decent amount of contributors, well maintained, etc.. If I were building some Rails app that used Slack I'd likely reach for this and not feel bad about it.

Kind of a bummer on the other 2 tho. Thankfully I wouldn't be building too many apps using those tools, but I get the point you're saying. In the grand scheme of things I think this also shows at how much more popular Python is than Ruby.

Slack's Ruby client works well and is well organized: https://github.com/slack-ruby/slack-ruby-client