4 ms·

Please don't "Show HN" something that is neither complicated nor interesting. The other "Show HN" on the front page right now, for comparison, is Claudia.js. T

by TheDong 11y ago

Please don't "Show HN" something that is neither complicated nor interesting. The other "Show HN" on the front page right now, for comparison, is Claudia.js. That's not something anyone on HN could trivially write in 5 minutes. It's about 5k lines of javascript. It's already somewhat mature. For comparison, the project you posted is under 50loc, any of us could trivially write (in fact, piping http://tools.suckless.org/sic/ http://tools.suckless.org/sic/ would be sufficient... or using znc with its "log" module, or using weechat / irssi's builtin logging functions), and doesn't really accomplish something super interesting to HN imo. I expect everyone who uses IRC in a significant capacity on HN has already solved the most basic level of their logging problem. I solved mine by just running a ZNC bouncer with the log module. The harder level of the logging problem, indexing it and presenting it in a nice UI and solving availability by merging logs from multiple leafs in a netsplit event, I'm not so you can consider commonly solved, but hey, your solution has nothing to say there either. Others have already mentioned that there are some issues with your code, so I won't touch on them, but I will emphasize that you should probably work on improving code quality and make something both more significant and more interesting prior to doing a Show HN. In addition, this actually is something people on HN actively couldn't trivially use because it has no configuration (hard coded connection strings) and no docs.

tilpner 11y ago
I'm curious, in what circumstances would you merge multiple log files (from different perspectives, I assume) because of a netsplit? That'd require one log/connection per server of the network, which isn't something ZNC or weechat will do by default. Have you ever needed that functionality?
- TheDong 11y ago
  Let's say that you're an irc network operator trying to make the channel's entire history searchable (e.g. botbot.me type thing). For absolute correctness, you'd want to record per-leaf and merge. However, the last time I needed log-merging functionality was much more boring; some of my log-files were corrupted, and someone else had logfiles that weren't as extensive, thus I needed to munge the two together. The timings were subtly different (because that's how irc works), so I wrote custom code to munge them together, preferring his for the range of corruption. So yes, I've needed that functionality, though it wasn't actually done due to a netsplit. I can foresee it being useful in the case of a netsplit if your logging is at the ircd level or you run one bot per leaf.
  - tilpner 11y ago
    I wonder whether any large network keeps logs of channels, let alone one per server. And if they do, they probably don't have much use for a merged log except for taking up less space. My own IRC log tool [GH: tilpner/ilc] can be used to merge logs, but I rarely use that functionality. For two log files "a" and "b", in weechats default log format: ilc sort -f weechat -i <(cat a b) | ilc dedup -f weechat I've never tested this with logs over 200MB, but sort will read the combined log into memory, which is definitely not optimal.
dang 11y ago
> Please don't "Show HN" something that is neither complicated nor interesting. The bar for Show HN doesn't have to be that high. It's ok for people to post projects that they're working on while learning something, for example. https://news.ycombinator.com/showhn.html https://news.ycombinator.com/showhn.html

by TheDong 11y ago

tilpner 11y ago

I'm curious, in what circumstances would you merge multiple log files (from different perspectives, I assume) because of a netsplit? That'd require one log/connection per server of the network, which isn't something ZNC or weechat will do by default. Have you ever needed that functionality?

TheDong 11y ago
Let's say that you're an irc network operator trying to make the channel's entire history searchable (e.g. botbot.me type thing). For absolute correctness, you'd want to record per-leaf and merge. However, the last time I needed log-merging functionality was much more boring; some of my log-files were corrupted, and someone else had logfiles that weren't as extensive, thus I needed to munge the two together. The timings were subtly different (because that's how irc works), so I wrote custom code to munge them together, preferring his for the range of corruption. So yes, I've needed that functionality, though it wasn't actually done due to a netsplit. I can foresee it being useful in the case of a netsplit if your logging is at the ircd level or you run one bot per leaf.
- tilpner 11y ago
  I wonder whether any large network keeps logs of channels, let alone one per server. And if they do, they probably don't have much use for a merged log except for taking up less space. My own IRC log tool [GH: tilpner/ilc] can be used to merge logs, but I rarely use that functionality. For two log files "a" and "b", in weechats default log format: ilc sort -f weechat -i <(cat a b) | ilc dedup -f weechat I've never tested this with logs over 200MB, but sort will read the combined log into memory, which is definitely not optimal.

dang 11y ago

> Please don't "Show HN" something that is neither complicated nor interesting. The bar for Show HN doesn't have to be that high. It's ok for people to post projects that they're working on while learning something, for example. https://news.ycombinator.com/showhn.html https://news.ycombinator.com/showhn.html