Hacker News new | past | comments | ask | show | jobs | submit login

Information dropping into a black hole happens in IRC on Freenode all day, every day. The issue isn't just Slack.



Many IRC channels are archived and the archives are searchable, so the information is not necessarily lost.


Archives are a start, but the problem is most channels are not indexed. There is no "google for irc" of sorts.

Even if the archives are searchable (the searches generally suck in the first place), who's going to know to go into this specific archive, for this specific channel, and search for this particular query?

As someone who was interested in this a few years ago: This is still an open problem for someone to solve. The solution isn't particularly hard, it's just nobody has really gotten to it yet.

(And yes, you may come across the odd irc conversation in your google searches once in a while - but it is not to scale with the immense amount of information that comes out of irc).


Every single open source project's IRC channel I've seen is logged and searchable, with a link in the topic.


Please re-read my post. Searchable doesn't mean indexed and mass-searchable.

Are you going to know that the problem you are encountering with your bluetooth connection was solved in freenode's #pulseaudio 3 years ago?


Oddly enough, I prefer the IRC channels I frequent to not be logged, just like the conversation I'm having at the corner coffee shop (probably) isn't logged beyond the ears of those who hear it.

To me it helps create more of a community feel. Often times you'll see active community members turn problems they deal with on IRC into blogs, articles or even books to spread that knowledge.


Here's a solution, e.g. for the #rust channel: https://botbot.me/mozilla/rust/


Botbot is nice but does not solve the issue of mass-searchability.


actually, most channels have logging. I've frequently stumbled across solutions on public (and indexed!) IRC logs.




Consider applying for YC's W25 batch! Applications are open till Nov 12.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: