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...