@MechMK1 If you were local (and I'm not shipping it), eh, I would offer to front you a free shitty AMD card or sell you my 980TI at a fair offer :D
@forest w3m is awesome, especially for low effort/skill web scraping :D
@forest >_>
@forest only... I don't EVER mix work with personal stuff
My laptop stays at work
As much as possible I seperate work from home, though less for security and more for "I am not touching this steaming pile of doo if I can avoid it"
AMUSINGLY, I started doing that cause I didn't trust my work PC at a previous job + I was a little paranoid about employers after job -3 or 4 suddenly shut down
@JourneymanGeek You aren't a high-profile target of course (since not all government work is classified), but it's very easy to accidentally mix work and personal stuff without realizing it. A simple example would be a waterhole attack which could potentially be possible even by simply knowing what sort of things you do on your work computer (e.g. what kind of websites you load).
@MechMK1 Do you play games that require a particularly strong graphics card?
@JourneymanGeek Well you said you worked in your country's equivalent of ICE and although I don't know anything about it, I could imagine that there are likely websites you frequent which are work related and, given that you've revealed enough information that one could potentially guess which websites, place a waterhole attack on them.
Of course it's unlikely that anyone would do that for such a government agency, but still.
So for you it's more of a "I don't want my employer to screw with my personal life" and not so much "I don't want someone in my personal life from screwing with my employer".
Most people who would want to screw with SE will have an easier time breaking into them via their horrible backend security than trying to get in through an employee. :P
Not that I know anything in particular about their backend, myself. I'm a Linux person.
I find that it's helpful in probably 50% of serious issues. Of course, most of the stuff I do involves the Linux kernel, and often experimental and customized ones at that, so there are more bugs.
Sadly lots of the underlying issues are so difficult to debug that you can't really find them without a deterministic fuzzer, and afaik, only Microsoft uses those regularly.
Do you work with a specific program/library/etc or a system/network?
(i.e. do your jobs tend to involve using a literal debugger finding memory corruption bugs and undefined behavior and the like, or working with networks/interactions between system components?)
I think the most 'fun' is when you thought you solved the problem, at the taxi stand waiting for a ride to get home, and something else goes boom at 2 am
Thankfully I've never been on-call for anything that needed me to be somewhere physically.
But even having to get to a computer dripping wet with a towel around you and not know if you'll need to work for 5 minutes or the rest of the night is a truly awful way to end the day.
I've heard horror stories about people who had to jump up despite having the flu.
Probably not legal in the US at least to make someone work in that condition, even if remotely, but sometimes a job really is too important to wait.
@MechMK1 Actually blacklist comes from "blackbook" which was a literal book that a king would have containing a list of allowed citizens. And white is the opposite of black, so it was used as the opposite.
@JourneymanGeek It was a change from "master" to "main" or something in kernel code. Literally resulted in millions of vulnerable devices just so someone's feelings weren't hurt.
But thankfully terms like master/slave are not unique to programming, and in virtually every other subject, they're still used ubiquitously. Hell, even in the 24th century, Commander Riker uses those terms to confuse a Ferengi.
@JourneymanGeek No, they exist because of etymology.
Blackbook -> blacklist, not black person -> blacklist.
It was referring to the literal color of a book's binding. Had nothing to do with power.
I'm not even talking about racism here. I'm talking about "A term that's based off obsolete linguistic skeomorphism" vs "It says what it does on the tin"
@MechMK1 "My friend was killed by a cop for the crime of walking while black" or "waaaah someone refers to a seccomp array containing disallowed syscall numbers as a blacklist!"
@JourneymanGeek That's appropriate when coming up with new words, but these words are so deeply ingrained in tech terminology that changing it all actually causes serious confusion.
If someone wants to change slave to minion for master/minion, that wouldn't be nearly as bad as primary to secondary. Whereas master/slave works in most situations, now you don't know if you have to look for primary/secondary, main/second, first/last, leader/follower, client/server, or what.
So to me a pragmatic solution would be "Change it on new things" and "if we're going to change it, do so with a bunch of planning and clear documentation"
The amount of time I personally have wasted because of the change due to ambiguity has been considerable, especially considering that I work with sandboxes a lot so "whitelist" is a common term in code I use. And given that it's resulted in actual security vulnerabilities means that it's already caused real damage in addition to wasted time.
@MechMK1 The other thing is the Americentrism here. Many of these terms are specifically offensive in our culture, and we ignore terms which are offensive in other cultures.
You know, diversity hires are actually a real problem because it causes people to assume that minorities don't deserve their jobs, which causes actual discrimination.
I have to (only partially) disagree there. There are many people who are truly put in a position where it's nearly impossible to pull themselves up and git gud.
But someone living in a ghetto who has the choice to either starve or commit crimes to feed their family is not going to be able to spend the hours and hours out of their day studying programming to git gud so they can get enough money to move to a better city and get a good high-paying job.
@MechMK1 And that's the problem: No one cares about a working alternative unless it makes them feel like they're "doing something about -ism".
