4 ms·
> Sure, most clients let you automatically save logs, but they were just text files you opened in any text editor. Right, my point is why doesn't Slack do that
by nexuist 5y ago
> Sure, most clients let you automatically save logs, but they were just text files you opened in any text editor.
Right, my point is why doesn't Slack do that? Then you could use `grep` or `find` to search across all your messages and avoid paying a monthly fee to access your entire message history and...oh, right.
- onion2k 5y agoYou can only search a log for the time that you were logged in and saving it. You can search the entire history of many Slack channels from the very first message posted in it onwards, even before you'd ever joined it. That's a significant advantage over a local file. I'm not particularly keen on Slack but suggesting search would be better locally is plain silly. Search is obviously better done at the server.
- TeMPOraL 5y ago> You can only search a log for the time that you were logged in and saving it. That ignores the possibility of the data being synced between local system and the server. Slack is already in the cloud, so cloud options are on the table. And so is syncing data. > suggesting search would be better locally is plain silly. Search is obviously better done at the server. The reverse is obvious to me. Slack search, like all web SaaS search tools, is really bad. I could do better with grep - and it would work faster, and I could actually trust that it searches through all the messages, instead of giving me some eventually-consistent view into results of a query that is only tangentially related to what I requested. And they wouldn't be able to tell me which properties I can or can not search by. And I'm not talking theory - in the past, I did some spelunking in many years' worth of IRC logs in a folder on my drive, and the experience was much better than searching for anything in Slack.