59 karma · joined June 9, 2011
Fuck that, I am AI vegan at the moment, and happy. I may build a machine and find out how to fix the architecual mistakes in this new scene, but thats very different than being an end user of it.
It is certainly a different market than legal, high potency THC, as well as medical.
I would ensure that you have someone to talk to who can discuss what success looks like for the role (of intern). With that, there is always what you want to get out of it, but if you are looking for a job, you need to have performance and goal conversations reguarly. How are you doing compared to peers or other interns, etc.
Are you paid for the hours you work in the internship? If so then you are not an exempt salaried employee.
What I don't like is changing what WFO looked like. If someone had to WFH for personal reasons (e.g. repair, packages, child issues, doctors appt), they just did it. Four days a week was normal, five was never normal. If we are trying to do 3 days and go to four, then everyone needs a dedicated desk. If you aren't willing to put a dedicated desk for people, you don't have a mandate for WFO, you have a mandate for hybrid.
I sit next to an officer who is not ranked highly enough to have a desk. A first year associate should have a dedicated desk.
It took the pandemic and a world in panic to swing the pendulum in this direction. It's going to take as much to get it back, and it may not go back to exactly the same thing.
If the company is taking an action that makes it less likely for people to come to the office or enjoy it, then it's pretty clear what they are doing.
As a *nix tech I could get a call to work on a QNX system, HP-UX system, SGI Altix supercomputer or a Sun Ultra 2. Linux systems were easy, as they had the package management support for FL/OSS, and would commonly come with Emacs in the base-pack (before nano was mainstream). Sometimes you would have a terminal issue and have a single line to work with, in which case you would need to operate vi without seeing what you are doing (or use sed/awk). So maybe it is those instincts to KISS and force everyone to learn vi, like they had to (I had to).
Certainly it provides no significant surface area of attack to have an editor, but I wouldn't put it past a threat actor to leverage plugin functionality as a persistence mechanism. I presume that these applications operate differently as root, but maybe not as service (daemon) accounts. It's not very well hidden, but there are all grades of threat actors.
https://nypost.com/2023/04/24/longtime-nyc-home-of-the-daily...
It's more likely that it would be detected based on the nature of the injected malicious data.
Creative use of advertising platforms is used you could easily narrow targets down and guarantee that you know exactly what the content is.
Anyways, this is just one gadget.
Defending against this being the use of -- to signal an end of command line arguments.
$ diff -u /tmp/a /tmp/b
--- /tmp/a 2015-03-24 08:33:00.021919797 -0400
+++ /tmp/b 2015-03-24 08:33:05.629963015 -0400
@@ -1,5 +1,5 @@
#!/usr/bin/env bash
set -e
i=0
-let i++
+let i++ || true
echo "i is $i"
$ /tmp/a
$ /tmp/b
i is 1
$You can use set -e, and turn it off (set +e) for code blocks and things that are problematic. He could also add '|| true', and you may be able to use colon to avoid point problems without turning everything off. These are edge cases and you can easily work around them if you an advanced user.
If you are not an advanced user then you should certainly use -e.
I would argue that theoretically, a government (or other entity) could use intelligence but use it within a set of moral and/or ethical guidelines that uses a system of checks and balances.
http://www.amazon.com/Cryptography-Engineering-Principles-Pr...
I can't think of a purpose where a collision of a non-malicious sample with a malicious file can be used by an attacker (let alone the same attacker). In addition, there are lots of historical threat data (tactical intelligence) that is based on md5sums. Newer tools support newer checksums, but will more than likely just increase the types of checksums supported, and not deprecate them.
Checksums are less and less useful when the malware can be configured, recompiled and re-assembled for a particular target. There are some good discussions on HN more fuzzy detection techniques that can't be evaded by changing inert parts of the payload, but that is orthogonal to using stronger checksums. Indicator of Compromise data including md5sums can be useful for general security, but because a determined attacker will mutate the files it is better suited to more commodity malware.
Stable 3D depends on the hardware and drivers, but gaming already has hardware requirements for graphics and it's getting much better. As far as OpenGL support, recent posts on HN lead me to believe that we are doing okay.
Audio compatibility? Support ALSA and OSS.
Arguments to xargs do appear to be parsed, example below:
http://explainshell.com/explain?cmd=find+%2F+-type+f+-print0...
GREAT: find / -type f -print0 |xargs -0 grep heythere
I tried some sub-shells, and seemed to not work so well. $() and `` would be nice.
ps -fp $(pgrep -d, krb5kdc)
ps -fp `pgrep -d, krb5kdc`
http://explainshell.com/explain?cmd=ps+-fp+%24%28pgrep+-d%2C...
edit: newlines
Lets say with Artsy, two people get a random piece of art and look at it and discuss it. It would be nice to relate about a common thing somehow. I don't think that I've seen this type of random person thing done with enough existing applications.
Of course I got an explicit picture, but thankfully the animated gif did not load. Conversation was good and it wasn't A/V like CR so that was actually nice.
The random stumbling upon another person is a great thing to have to emulate the randomness of meeting someone IRL.
I saw support for vertical tabs in Chrome that can be turned on, but I think that is experimental. The people that suffer from the memory problems are the people who really just need better tab management features. Maybe this is something for power-users that just needs to be handled with extensions.
Also being able to suspend and resume sessions better is a good idea, and this may help with. When coding on a particular thing, I'll have most of the tabs open that I need. When I get back into it it's just a storm of CMND-T and searching for the references I was using. Sounds like this could help with that.
Lots of rappers wear hoodies. My point wasn't that anything there was racist, just that you do get comments for dressing differently, not fitting in. Those alone don't make this racist, the other comments do.
So is it that baggy jeans are less professional looking, or a racially motivated attack on urban lifestyle and dress. It doesn't matter really, the rest of the comments provide enough of a backdrop for us to make our own conclusions, which is all this is.
I've had a situation that was sort of similar where a co-worker made a comment on my clothing being too uhm, urban. Jeans, oversized hoodie (hood up), and shit kicker boots. I was sick, and it was freezing out walked into a meeting and it was announced that Eminem just walked into the meeting. My reply was (paraphrased) that "Is that the only white rapper you know, I don't look anything like Eminem". I guess I was looking for something like Sage Francis or Necro, but I digress. I felt singled out for the way that I dress. Now I guess that anyone can debate here if what I said or the initial comment was racist, but I would say that it wasn't, just ignorant and stupid. That said, if that comment was slanted ever so slightly to the fact that I have some Jewish heritage, it would trigger a soft spot and would have REALLY irked me. Had some issues with that early in life.
So considering the more over-the-top racist comments, and initial reaction of management when confronted, this whole situation is really awful and should not happen. Instead of debating if this is really racism, we should probably just try to limit and control it's effect on our lives. It exists, it's all around us and you don't have to look very far, even in tech companies.