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.
Good linters correctly highlight all missing semicolons as a symptom of sloppy, negligent, careless programming (or pointless syntactic showboating). It's also technically syntactically valid to omit braces around single statements after if, else, for, and while statements, but idiotic and dangerous to do that, too.
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.
If the format of syslogs doesn't change there should be no issues (or should it be read as "the system logs don't have the year"? )
If you don't have the year, it is not a "full date" in the forensic sense of the term, and you simply cannot present such a result in a Court.
A statement like "A Netac USB device was connected on May 26, presumably in the year 2019, exactly at 00:51:54 and soon after disconnected, exactly at 00:52:21" won't be good.
If it is technically not possible to retrieve the year, then the whole stuff has very little relevance on itself.
It would be needed to create a complete timeline of the system under investigation and correlate the month, day, time with activities that have an objective timestamp including the year.
> 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.
Well, then the tool has no actual "forensics" use by itself.
It's a pity, of course, but it can only be a tool to confirm findings that have a "proper" timestamp.
Most probably the log consists of "appended" entries that might mitigate the issue, still it is needed a clear and extended "justification" to the procedure with wich the year is "attributed" to the yearless entry for forensics use.
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".
As a musician, I can tell you that practicing a song (particularly a well known song) is very frustrating partly due to boredom. A practiced musician will know when they’ve reached their limit for the day of learning a song. Muscle memory is much slower than neural memory, and usually requires “sleeping on it”.
Knowing you’ve reached the limit of your current capability is boring because you know the next few practice rounds will be much of the same, with minor improvements that provide a dopamine rush.
Regardless, nothing has changed in the age-old saying of how to get to Carnegie Hall: Practice, Practice, Practice. The practice is the boredom, but without training your muscles and building up myelin sheaths, you’ll never be good enough to automate most of the music to an extent that you can improvise on top of it (the fun part).
I guess my point is akin to OP’s, in that boredom isn’t inherently a bad thing, but a means to an end. Without the boring practice, we wouldn’t have experts/artists...and even then, the practice doesn’t have to solely be boring.
Yup. ESR's opinion and the OP are not mutually exclusive. Avoid boring, repetitive work, but deprive yourself of constant stimulus every once in a while.
