Terrible UX.
35 karma · joined December 27, 2013
Terrible UX.
The other thing is the idea that, for those of us growing up in various segments of society that are affected by the above, our very mechanism of thought was generated by this system, and that affects how we think about and perceive these systems (and everything else).
I believe he's simply advocating for being conscious of the above two facts, when examining these systems and reforming them (and of course when teaching the history of these systems). To ignore race and racism as if it never happened is to allow all of that ingrained racism to perpetuate (of systems and of thought). All of this sounds pretty reasonable to me, but that may be due to my particular experience.
That said - I'm no expert, I've only read the linked passage so far, though I've now ordered the book and will start reading it tonight. I'll refrain from commenting further here (I think we're pretty off-topic already). Thanks for the discussion!
https://www.penguin.co.uk/articles/2020/june/ibram-x-kendi-d...
I think it's pretty clear from the full text that he's not advocating for racism against past racists or their offspring (which, intentional or not, is what your use of the quote makes it sound like).
And Broadcom _does_ note that they associate with Vault7 group via the whole picture, but it's weird they present the strings and dates data without noting that it would be trivial to fake, and don't give any specificity to the other data points.
I guess for this type of work the only thing you _really_ have is the code's intent, if you can figure that out.
That said - it ABSOLUTELY BOGGLES MY MIND that, if these are not leaked, but rather recovered from attempted attacks, how are _any_ valid timestamps and strings not randomized as part of the build process!? I'm not saying it refutes or confirms, I'm just wondering - how difficult is it to read an ELF | PE and remove / change those things, and if it's as easy as I'm thinking, why would you not do so? Or replace with preprocessor directives that you could setup to random values for production builds to use strings and timestamps that indicate some other entity? All of this seems straightforward to me, like, could do via shell scripting or python. Is there a valid reason to leave this stuff in? Are we seeing some low priority work that the TLA wants to leak to show that they're out there and capable?
They can announce this now and change their mind as they please, right? I'm not sure about Apple's track record on things like this, they may be good, but they could just slowly pull or decrease funding, and we probably won't even hear about it in the future, or am I missing something?
The church across the street from my house is large and I'm sure heating and upkeep is no small chunk of change. A good portion of the cars parked in the reserved row (staff) are nicer than mine, so I'm guessing the salary isn't necessarily "modest".
While it's not terrible, I find powershell pretty frustrating. I started off enthusiastic, especially given how archaic cmd.exe is. As mentioned elsewhere though, the advice not to use aliases, coupled with unbelievably long command names that I hate typing and can't always recall exactly - is it convert-to-csv? to-csv? no it's convertto-csv - I can never remember and I don't feel I should need to use ISE to work around this. This utterly prevents me from internalizing.
Even worse, until v3 apparently, iterating over an empty array would fail out (iterate once on $null instead of not iterating at all) and had to be protected with an explicit check. I was on v2, and it was at this point that I completely checked out and decided it wasn't worth learning and that I'd wasted my time. In general I could do what I needed with either cygwin or win32 cpython and those didn't make me feel like clawing my own eyes out.
It seems the situation has improved, but I just don't see any reason to take it up again, ESPECIALLY on linux, unless I _have to_ do dotnet stuff, and even if I do I'll explore every other available option first (ironpython? f#? is there a dotnet tcl?) TBH I avoid dotnet anyways given Microsoft's past (EEE) and current (telemetry, start menu ads, etc) behavior. Fool me once etc etc etc.
I have been sick a lot lately and I feel like it's due to bad sleep, and I hate my bed, but buying a mattress is such a scam.
Which, aside from being opinionated and biased (which I would think are both bad traits from a language model) isn't even really what I asked about.
I suppose the bias comes down to the training data. But this all strikes me as Eliza 2.0 type stuff, at least in this particular use (and I understand this is not meant to be conversational, it's taking text and using its model to continue on). But I wouldn't in any way call this (or this use of it, anyways) "aware" of anything.
This is literally the only keyboard I have found that uses those switches.
[1] https://www.prohavit.com/products/hv-kb395l-low-profile-mech...
It doesn't appear the code was ever released either.
If this researcher was able to access it via not much more than a hole that was _already reported multiple times_, then I think it's not a stretch to think that [many?] other less honest parties could (and in my opinion most likely do) already have it.
If it was me, even if it's definitely only a single researcher who got access (and it doesn't sound to me like they know for sure - but regardless), something _that_ sensitive would have to be rotated anyways. If it was someone outside the teams that strictly require access to it operationaly, I'd rotate it, let alone outside the company.