They are different -- higher level languages like C++ and Python surface the abstractions, making them more apparent to the human reading the code. LLMs typically hide the abstractions. You can still read the source code, sure, but even the latest models will produce a lot of repetition of utility functions and produce data structures of various shapes without commonality or reuse. This is moving in the opposite direction that machine code -> assembly -> C -> ... were heading.
Prioritizing something other than 7% week over week growth. This doesn't appeal as much to venture capitalists so we may have to try it with some bootstrapped products first.
Having seen the abuse vectors that get thrown at this and similar products, I suspect it is less about whether they care and more about finding a suitable threshold for some arbitrary features, or moments of demand exceeding the available moderators. The repetitive 6 minutes make me suspect there are reports timing out in the moderator queue and the automod doesn't like images or something.
Or, perhaps a part of the process that is two or three teams away, like photo attachments being deemed too large (getting passed from Maps UI through internal task queues to some abuse analysis, or even as early as the frontends that take the request). Plausible, especially as phone photos have steadily increased in size while some thresholds remain ossified.
I'm outside that world now so I can't investigate or effect change.. there used to be people there who care about these things. I suspect there still are.
Even more likely is that other priorities exceed the capacity of the headcount on the relevant teams. I don't know if that counts as the company not caring. It's hard to attribute intent on corporate-scale embodiments. Perhaps that's the root of the problem, I wonder if any collective that reaches hundreds of thousands of members can ever exhibit that. Maps is a huge product that a small competitor could hardly compete with but I'd love to be proved wrong (either on the smallness or considerateness aspects).
This is the key to the problem that I think people are missing, possibly because they kind of want to miss it. Google and the other companies hiding behind LLMs and primarily doing it because they can't operate at the scale they do, with the dedicated ecosystems to gaming them that they develop, without this hiding. They can't afford humans to review in a minute or two what scammers can generate in fractions of a second, not even at their scale.
Now, I'm enough of a fan of decentralization and the destruction of these massive sites with way too much control to say that I'm perfectly comfortable saying that they should be mandated to handle these things more sensibly and with more humans. That such a plan would have the side effect of breaking them up into vastly, vastly smaller pieces, causing an technological Cambrian explosion of various sites and diversity resulting in the parasites no longer being able to focus all their firepower on a very small set of targets, is for me a bonus, if not the main goal. However, I, and anyone who agrees with me on this, is rather clearly in the minority.
In the meantime, if we're going to have things the size of Google or Facebook, there simply is no solution where we all get human review whenever we ask for it, because instantly every spammer and abuser will ask for the human review. There just isn't a solution. It looks like there is an obvious solution when you consider "how will Google review this one application" but that's not the landscape Google faces. They have to solve the problem of how to deal with the entire landscape of requests they face at once.
> This is the key to the problem that I think people are missing, possibly because they kind of want to miss it. Google and the other companies hiding behind LLMs and primarily doing it because they can't operate at the scale they do, with the dedicated ecosystems to gaming them that they develop, without this hiding. They can't afford humans to review in a minute or two what scammers can generate in fractions of a second, not even at their scale.
"Alphabet, Google's parent company, reported $112.1 billion in profit for the three months ending in June."
Ah yes, they definitely can't afford it.
I genuinely cannot grasp how someone who is capable of 1. finding hackernews 2. creating an account 3. writing a coherent English comment, can come to such an absurdly wrong understanding.
Scammers generating things in fractions of a second is an incredibly well understood problem that affects every single surface of the earth that has a "submit" button. Even completely anonymous services have largely managed to solve this. Google Maps requires a verified account, meaning it's entirely solvable. It's a non-issue.
Give me $112.1 billion every 3 months and I'll solve it for you, no worries.
This gets rid of the scams but makes all surviving reviews unreliable since they'd all be pay-to-play. It'd be better to just remove reviews altogether at that point.
Which doesn't seem like such a bad idea now that I've said it out loud.
Kind of, but not really.. though there are simple models with electrons as a point charge, a more accurate model involves the electron field describing the probability of an electron existing at any region in space (not to be confused with the electromagnetic field, the medium in which photons propagate).
Sure the position of an electron is not definite, but neither is that of a buckyball, but a buckyball has a shape we can describe, an internal structure we regard as extended over space, in a way that is separate from the indeterminacy of its center of mass position. This is unlike an electron, for which, if we set aside the uncertainty as to its center of mass, my understanding is that the only internal degrees of freedom it has left (in the Standard Model) are its spin and whether it is left or right handed, with no other structure to it.
It is in this sense that, AIUI, electrons are modeled as point particles.
Of course, that doesn’t mean that if we zoom in enough, probing at higher and higher energy scales, that it can’t turn out to have some non-zero fundamental size outside of just uncertainty in its center of mass position. I think string theory would say that at the string scale it would be a string.
But, AIUI, no experiment has shown it to have the kind of extent that would make it be called not a point particle (an extent in a sense beyond just uncertainty in COM position)
I think they're referring to the Enterprise sales where people have felt pressured to sign six- or seven- figure contracts after usage goes above a certain point. However, all the articles I've read on it are from companies using Cloudflare to do suspicious things with rotating domains through IP addresses, or doing things to try and get around service costs. It also seems like they give you months of warning and will try to convince you to sign up for Enterprise, they don't just shut things off. But their sales team seems to portray themselves as legal, support, or compliance teams sometimes so not exactly forthcoming in their approach either.
I'm a happy user of Cloudflare, but if you're using it for domain registration and hosting infrastructure, you need to see it as a single point of failure. Any account issues and you won't be able to point your domain to an alternate host while you work things out. Any service outage in CF systems will similarly lock you out of routing around the failure. It's better to have DNS off of cloudflare if they're handling your hosting services also. Or host elsewhere and only handle domains on cloudflare. Their domain pricing doesn't add any costs over the base registrar cost, so the latter is a reasonable option.
Now remove the spacebar, combine the two buttons into a single one for "tone" and adapt it to morse code. All the buttons still do only one thing and now there's only one button!
And, you don't have to worry about what to do in the case that someone hits the "rotate ball" button while it's still rotating.
If you're suggesting that the different columns of a comptometer would relate to different rotational axes of the ball, you will likely run into gimbal lock in 3D.
You could build an interface in 4D around quaternions but that is much more complicated than my suggestion (even including the part where you learn morse code).
The quoted part of my comment is in reference to the core topic of TFA where iOS and Nothing/Android photo apps handle the "pressed again during rotation" action differently. That "rotate the typewriter ball" interface runs against the same problem, by necessity of rotating a physical ball.
I am suggesting that the whole keyboard can lock during the time the physical ball rotates; the comptometers and pinwheel arithmometers of the yore had this functionality: while the mechanism was performing the addition of the number just entered, the user was blocked from fiddling with the input mechanism.
I get that's what you're suggesting. The locking per-axis or across all axes is fine but doesn't address the problem I'm talking about. In gimbal lock, which many graphics programmers first encounter by using only sequential rotations around the camera's axes, you can get into an orientation where you lose one of the three degrees of freedom.
Why remove the code and binary artifacts, though? Don't you want to verify that the business logic is accurate and the processing is deterministic?
In some circumstances there is no substitute for something that you know will produce the same answer for a given input, consistently. And that's before even considering the watts per response.
The AI is the business logic, and the processing, and all of it. The context window is effectively infinite, with layered context window depth and speed.
Think of short and long term memory, or think of RAM vs SWAP. Dip into swap to pull needed data into RAM context. SWAP can be anything storage related, including a symbolic database or a best-encoded set of priorities.
If a person knows 100 knots, but hasn't tied one in 23 years, they might have to think a bit before they get full use of their long term memory... and tie that knot. I don't see an issue with layered speed context, that is, GPU ram, slower RAM, DB storage, all in the same format.
Imagine a world where a 'factory' is just high-tech 3d printing, with a dozen different methods (eg, plastic, laser+metal, etc), and getting specs for everything possible is, well, an immense amount of work. Imagine having a billion item catalog of things to print, and, imagine new requests for new things to print.
And the request doesn't come from an expert, but from some dude who sketched something on the back of a cardboard box.
The LLM can pull from long term storage for how those things were done before, how similar things were done before, and just get to work.
Regardless, the connection was what I was talking about before. Data transfer. Do you need http? json once established? What? Imagine instead that's all in the wind?
And it's so fast, so capable, that dynamic is easy.
reply