cakes

With enough games and enough time we could have a real interesting set of game-based tooling :)

I had some issues with the heart rate monitor on the first band. I accept that it was likely user error (my fault) but a few times during a normal exercise routine it reported heart rate values well outside the where my heart rate was (or should be)

twitch makes twitch self-aware

Per #1 - make sure it isn't just change just for the sake of change and that the likelihood is that you'll end up experiencing the same problems (but probably a different spin) is possible. Before you hop jobs make sure it will really resolve some problems you have and won't be experiencing "same shit, different day/place/employer"

I'm interested in how this is going to work in PowerShell with the way everything works now, if there happen to be any details about that (whether here, somewhere else, or a past link)?

Agreed (assuming it was a mistake). If (not that it is a simple flag) a testing flag was left on or something that caused this and went out - sure, mistake. If a decision was made for this purpose and it was like "Oh...I guess they caught us" - that's something different.

I didn't have any OS specific issues either. I, also, had to re-install steam (though all the data files were fine) but after the re-install things seemed fine.

Though I'm not going to say I really care for sysvinit - I prefer it to systemd as well. Every interaction I've had with systemd just ends up confusing me until I either successfully get it work _somehow_ outside of logic I can actually comprehend or giving up entirely. A lot of people I know have had similar experiences.

That has been on my to-read list since watching "The Wire" earlier this year. The minimal research I did into it before deciding I would (eventually) read it was definitely that Simon was (from accounts) given a lot of freedom.

I'm glad to see it here - reminds me I should get around to actually reading it here sometime soon.

I have been having a lot of conversations about SELinux + Containers recently. Is there more/further reading anyone can suggest about interactions/background between containers and SELinux (e.g. docker, systemd-nspawn, etc.)?

Every runtime exception as a bug would seem overwhelming.

Wanting to know when runtime exceptions happen (and grouping them) is very helpful a lot of times but it seems like by itself (without context) would only get in the way of trying to parse what is and isn't really happening in some cases.

Especially when trying to sort out what needs immediate attention and what needs attention at some point later.

This is definitely a question I have especially since in my experience sometimes you had trade-offs due to other restrictions so every functional item needed to have value and new functionality may require removing/changing/disabling other functionality.

The idea of "just get over themselves" can definitely be harmful and that one can "be social" by switching something on/off is definitely not something that someone can "just do".

That's definitely very cool - I wanted to find some more info about the project for my own interests (https://news.ycombinator.com/item?id=4528797)

Actually just had this conversation with someone about setting up a new https setup for hosting a tool and the amount of online "guides" that still reference 3DES (when other options may be more suitable) is impressively high. Yes 3DES is still "secure" in situations but other alternatives are preferred when we can take them.

I started to have that same thought and so looked at the code and of course my next thought was along the lines of "Well...I mean it isn't like it changes that much, right?" and realized that I probably use such a tiny subset of what sudo can do.

There is a lot more in the man page than I expected not to mention options I can even fathom needing (for myself, yet).