pretty_lorelei

As I understand it, it's a tuple of lists of cubes, i.e. a slot stores a head of a linked list of cubes.

The button in the bottom left corner of individual rule pages is almost sadistic: "Do you want to scroll down a screen to view actual content you already clicked for - or find and click the button in the place your cursor spends the least time at?" Edit: also I will never click the social links on the right, because they are absolutely unreadable to me.

Honest question: how often does the code ambiguity due to lack of semicolons lead to non-obvious bugs? I'm nowhere close to being a JS expert, but I've done some JavaScript-heavy pet projects and I've got an ambiguous statement interpreted wrong exactly once, and the cause was pretty obvious within a minute of looking at the error.

"p and not p" is false, "p or not p" is always true.

> or should it be read as "the system logs don't have the year"? That's the case. RFC 3164, which specifies the log format, is the only one usbrip can read, and it doesn't have an option to specify year.

Oh, sorry. My third-party app previewed it just fine, but I've just tried it in the browser now and I promise I'll never do such thing again.

They explain the reason in README:

  usbrip works with non-modified structure of system log files only, so, unfortunately, it won't be able to parse USB history if you change the format of syslogs (with syslog-ng or rsyslog, for example). That's why the timestamps of "Connected" and "Disconnected" fields don't have the year, by the way. Keep that in mind.

IMHO, this is just different defininiton of boring, as in "doing this repetitive shit is boring and I would be better off automating it and doing something challenging" vs "being alone with my thoughts rather than consuming delicious Internet information is so boring, let me just mindlessly scroll HN instead".

GitHub is owned by Microsoft though, so there's no guarantee they won't have problems with someone else doing this.