61–70 of 94 posts
Earlier quoted context omitted.
Why aren't they? One of the great strengths of the internet is that information doesn't usually go away; most of the time, you can refer back to something said 10 years ago with little extra effort. Slack breaks that.
Isn't that the norm for chat apps though? It's not like they're breaking anything... people are just expecting something that doesn't really exist?
Slack is great, but it's adoption by popular opensource communities is problematic. Why? Because opensource communities are on the free plan, which limits search once you have 10k messages. I've had experiences where I wanted to revisit a question I had asked in a Slack channel the previous week, and been unable to find it. As a result, everyone burns out faster b/c the same questions get asked and answered over, and…
Earlier quoted context omitted.
Thanks for the kind words and the useful critique. I found it tricky to strike a balance between new budding search devs and people more advanced. I may write a more advanced book at some point.
And thank you for considering my reply as "kind words". :) I would not have been so harsh if I knew you were going to read the reply! That first chapter though. So many points repeated. For those that want to read more: http://opensourceconnections.com/about-us/doug-turnbull/ or really anything at http://opensourceconnections.com/blog/
Most of the time I search for information I need is because I don't know anything about that part of the software. I never found this kind of information in Slack.
Parse the company docs, or our rep, and now we're talking.
Open-source desperately needs more search-tool projects. Lucene/Solr/Elasticsearch are nice, but they need competition, especially outside the Java world.
Slack is great, but it's adoption by popular opensource communities is problematic. Why? Because opensource communities are on the free plan, which limits search once you have 10k messages. I've had experiences where I wanted to revisit a question I had asked in a Slack channel the previous week, and been unable to find it. As a result, everyone burns out faster b/c the same questions get asked and answered over, and…
I agree. I am dismayed when I see open source projects using Slack in lieu of IRC or a mailing list. It means I'd be forced to use their awful client (which is slow, buggy, and far too resource intensive for a chat application) or use their awful IRC integration. This is all in addition to the issue you raise of Slack being a black hole beholden to a profit motivated entity. Just use IRC. It's practically impossible…
Usually when I'm searching, I'm looking for a particular message, possibly even one I read earlier that day, and I may know a few things about it, like who sent it and that it had an important link, but I still can't necessarily find it! The results are also presented in a giant cartoony way that makes me page through many pages. Tokenizing my search into "keywords" means that even if I know a substring of what I'm looking for, it doesn't come up as relevant, or the tokenizer tokenized the text differently. This is also why GitHub search can't find a lot of things.
What I would want in a search experience is the equivalent of Control-F over the list of messages I've actually seen.
Slack is great, but it's adoption by popular opensource communities is problematic. Why? Because opensource communities are on the free plan, which limits search once you have 10k messages. I've had experiences where I wanted to revisit a question I had asked in a Slack channel the previous week, and been unable to find it. As a result, everyone burns out faster b/c the same questions get asked and answered over, and…
Earlier quoted context omitted.
And thank you for considering my reply as "kind words". :) I would not have been so harsh if I knew you were going to read the reply! That first chapter though. So many points repeated. For those that want to read more: http://opensourceconnections.com/about-us/doug-turnbull/ or really anything at http://opensourceconnections.com/blog/
Haha. That chapter was revised a lot and ultimately shortened a ton in the final version. I agree it had a lot of repetition. Hopefully it's better in the final printing.
I tried to see your talk at last year's Elaticon, but it was packed due to the small room. Not surprising since Elasticsearch tends to minimalize search in favor of analytics/logging. So few talks regarding pure search.
I've never used Slack because last I remember they don't allow local installation, therefore no access to any documents that were dropped in, is this still the case? I have been using mattermost instead, and wrote a bot which processes all documents uploaded into mattermost, extracts metadata, creates tags and summaries for each, archives the documents in an ECM -categorizing them by their tags, and opens them up for…
This is like saying Ford sells cars they don't allow you to fly.
If you want something that flies, buy a plane.