doomslice

Google's internal tooling for this is actually way behind what's available to the general public (they just got access to Claude though!)

It's not self driving though... people should stop pretending it is. It's driving assist. Think of it as a slightly better lane-keep and adaptive cruise control (which often require intervention in stock configuration).

Let's say you have 100000 documents in your index that match your query but only 10 of them the user has access to:

A basic implementation will return the top, let's say 1000, documents and then do the more expensive access check on each of them. Most of the time, you've now eliminated all of your search results.

Your search must be access aware to do a reasonable job of pre-filtering the content to documents the user has access to, at which point you then can apply post-filtering with the "100% sure" access check.

Well if you don’t have a pretty good idea of the problem you’re solving for the customer, you’re much better off trying as many things as you can, quickly and cheaply, to figure out.

Do you know that the big expensive thing is what your customers actually need? Do you actually know what your customers need?

That’s basically the only important context. If you can’t deliver that, it doesn’t matter how well thought through, extensible, or scalable it is.

Did they remove it? It says the researchers provided a notebook that they used to verify the attack.

Or do I…

All this setting does is make the feature available to you in the frontend -- it's up to you to use it or not!

In adtech a first price auction is also a single round.

You gotta save that optimization for when performance ends up on a top level OKR!

… ten minutes later.

I'm not defending this at all, but one of the reasons why there are no (or few) humans that can be contacted is that they* said that it was tried before and it caused a lot more issues with mistakes/takeovers due to social engineering.

* Can't remember who said it but it was at a town hall this year

This was maybe 8 or so years ago so I'm not sure what else this unnamed ticketing company added since... but permissions were pretty lax at that point and had JUST started to tighten up.

Oh I forgot to mention that Apple rejected the iPhone version of the app at first because we didn't make it clear enough that we were tracking their locations like this. Our head of product at the time just called someone up at Apple and it got approved with no changes. It all stunk.

Yes the ticketing app that people were required to use to get into the events.

A ticketing company was experimenting with BLE beacons to trigger things like seat upgrades and coupons when people walked by certain things in a venue… or at least that’s what they said it would be used for.

Instead they covered LA Live and surrounding area with them and then just sold that data to… well I’m not sure who since I left shortly after they did that.

The justification was “but we put it in the TOS and Privacy Policy”.