Question here then, is when will we see a competitor enter the market who both cares about getting it right and is actually able to compete with google maps
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.
It isn't about making a better product at this point. It is about cracking into the mindshare that makes people reach for software like google maps reflexively in the first place. That is far harder than the technological challenge. Almost impossible in the current era, arguably, with all the astroturfing.
Before Google maps, map services used to be super expensive. You can't compete with free beer. You would need to disrupt Googles main business first in order to even out the playing field.
I've sent in corrections to Apple Maps in Portugal (shopping mall is 1km away from the location on Apple Maps) and Canada (speed camera does not exist). Both were taken care of within a couple of days.
but then again Apple Maps seems (certainly here in London) to be absolutely full of geofraud entries and out of date slop, such as small businesses with linked websites that have been shuttered for years, and strange businesses located in the middle of playing fields, parks and lakes.
They are absolutely awful and won't accept even a correction of opening hours - when you are the owner of the business and registered as such with Apple.
true but if you're actually running k8s and similar workloads, chances are it might eat memory that LLM requires.
you'll also notice these articles rarely specify their context window in tokens, because it is small, usually 30k to 70k tokens and it gets slower as it fills up.
I actually have a Mac Mini M4 Pro with 48G. I gave the k8s example because this is what I was doing with it.
Was because I am back to using Linux as my workstation.
My Mac Mini is now a headless server for llama.cpp.
So, you are right that for these workloads , I would not be using the Mac Mini for k8s AND llama.
Another thing going against using a Mac for Linux containers is that there are no solutions that I know that properly manages memory : memory is given to the Linux vm , but never fluctuates if the needs in the vm are less than the initial request.
I know Orb Stack does that but is it proprietary. I think UTM does it , but not sure I would use UTM instead of Lima, Colima , multipass , etc to run containers.
reply