codemac

And police officers have repeatedly stalked and harassed the public via flock access.

They go up much more than 2% in literally every other state, California is the cheapest place to own property for >10 years.

You can argue against property taxes entirely, but Prop 13 definitely means that families, businesses, and all property owners work very hard to never sell, never reassess, and never change their tax rate.

To be clear, this is slightly smaller than the pixel 10 by ~1mm in each direction, but they are still too big.

McGovern is not someone to hold up, but that's not the quote.

It was: "I would only argue that senators don't have the luxury that a research scientist does awaiting until every last shred of evidence is in"

It adds npm as a dependency, to a go build?

It changes the contributor email?

to install random npm packages?!

in /tmp?! in post_install()??! With a new random contributor email????

Archlinux is focused on enabling a specific type of user, and certainly ones that can read bash scripts, and understand reasonable depedencies vs unreasonable ones. And even then - this is specifically in the AUR and not a package the distro directly offers.

Exactly, these hacks really stand out to me, and used odd patterns (like .install files that just had 2-3 line post_install functions) etc.

Right, the PKGBUILD only helps you review if you're installing what you intend to - not verifying if what you're installing contains any hacks.

This hack in particular added random npm packages that would have been unneeded/unintentional, and was visible in the PKGBUILDs directly.

> isn’t that also the case for every browser extension, VSCode extension, nuget package, Cargo crate, python package, npm package

Yes, and all of those have supply chain hacks in them, and have happened within the last year? In this specific case, it's a malicious npm package being installed with official npm tooling in the PKGBUILD.

The advantage to the AUR is just that you can reasonably review every PKGBUILD for what you're installing, they are very simple bash scripts. It'd be great if more people would donate resources to help verify and validate AUR scripts, but the AUR specifically exists for packages that the trusted users and devs of arch don't have time to personally maintain.

emacsclient + codex has been a game changer.

I probably add or change a feature in emacs once a day, or every other day. I've been using emacs for some insane amount of time, maybe 20 years? And still I had more customization to go.

Emacs and programs with it's level of programmatic user customization will survive the AI period in my opinion. Anything static will falter.

> Nvidia CEO Jensen Huang said his company’s recent investments in OpenAI and Anthropic are likely to be its last in both, saying that once they go public as anticipated later this year, the opportunity to invest closes

ok, sounds obvious

> Nvidia, for its part, isn’t offering much more on the matter

ok, so no more news from nvidia

> Still, a few other dynamics might also explain the pullback..

Wait it's a pullback?

This is terrible reporting, right?

Please reread (or.. read) the paper. They do not make that mistake, specifically section 7.1.

A reward function (R) may be hackable by a model's response, but when asked to confess it is easier to get an honest confession reward function (Rc) because you have the response with all the hacking in front of you, and that gives the Rc more ability to verify honesty than R had to verify correctness.

There are human examples you could construct (say, granting immunity for better confessions), but they don't map well to this really fascinating insight with LLMs.

You are thinking in terms of utility, instead of organizational power. Which is fine - but misses why the meeting behavior continues imo.

While I have several disagreements with this deck, there are two large ones:

1. In my experience, a lot of teams don't have long enough meetings to avoid the litany of small meetings. For example, a lot of staff meetings could easily be 2 hours and then cancel many project specific meetings that have 50%+ of the same attendees later in the week. They also enforce a cadence of execution - everyone knows they need to prepare for the weekly staff meeting, rather than many small meetings every day. It also avoids the problem of people feeling not included - you're always invited to the one huge meeting every week, it's up to you to attend or skip.

2. The problem with meeting culture cannot be solved with education on how to say no, it's about admitting that attending meetings actually does convey a lot of things. Lots of information is not shared outside of meetings. Seniority of attendees actually does have a huge impact on visibility in folks' careers. A lot of the advice in this slide deck feels like it should work, but doesn't in practice because of self interest.

The education that needs to happen is quite different imo:

- leadership needs to be done through writing

- meetings should be recorded and minutes sent out broadly, along with allowing silent attendance.

- decisions need to give time for dissent outside of meeting attendees before committing.

Math notation is high context, so it's great to just ask llm's to print out the low context version in something like lisp where I can read and decompose it quickly.