Hacker Newsnew | past | comments | ask | show | jobs | submit | camel_gopher's commentslogin

“We are getting bad press around the hacking incident. We need some content to draw attention from it.”

Do you have kids?

In SF they would be taken quickly by the homeless for parts, probably the batteries most of all. That and rummaged through for drugs, or repurposed to deliver drugs.

Is this what happens with scooters and lime bikes etc? Because it always strikes me that they’re easy targets for cannibalism yet nobody seems to do it.

They do. Tons of them are stolen or destroyed regularly. The company just keeps buying new ones.

It was common for people to vandalize and throw them in bodies of water for a while before people got used to the idea. I still occasionally see some repurposed from time to time

Surely the robot will have the beta crime fighting package installed.

Pay a little extra for the M134 Minigun attachment and you’re good to go.

Having expensive high tech robots picking up litter while there is an ongoing social crisis like homelessness sounds pretty dystopian.

Have you seen San Francisco right now?

I haven’t been to the city in 12 years. What is it like right now?

Like every downtown in the US. In short: not good.

I don’t want to say you guys overstate things, but literally every downtown in the US? Might be time to move. I was regularly visiting San Francisco in the late 2010s when the tech bro community was really ginning this story up. Was it an ugly clash of both the promise and the failure of US economics? Yeah. Was their shit on the streets? Also yeah. Did I ever feel unsafe? Not really. Anecdata but I remain skeptical because of these Helen Lovejoy-level overstatements.

Clever but that’s not how we measure latency.


When it comes to UX, perceived latency is king.


The perceived latency starts from keydown, not keyup. Redefining latency to start at keyup reduces measured latency, not perceived latency, and delaying the visual display to keyup makes perceived latency strictly worse, not better. Even sticking with the keyup definition, just displaying the result as soon as it is available gives the possibility of negative (defined) latency.


I think you don't fully understand. They aren't just doing a search based on the key being pressed down. They already did a search based on the previous characters that returned results for all possible next characters. So by the time you type a second character it just checks results locally from the search that had likely already been returned from when you had typed the previous character.


They do that, yet proceed to kneecap the perceived latency by delaying the render.

> And on keyUp (the user releases the key), we render the suggestions.


There are a large number of edge cases where rendering it on key down would not be desirable (user types Ctrl+v, how accented characters are enetered, how some Asian languages get handled, backspace/delete, user holds a key down, etc). This is getting into the point of optimization where it simply does not matter and can actually harm things


Holding a key would indeed require both on key down and up. I'd still argue that handling rerender on key down (or to fully match whatever OS/browser semantics, oninput) makes more sense than key up. Pressing Ctrl+V for example produces feedback as soon as "V" is pressed, not when Ctrl and/or V is released.

Interestingly Ctrl+V on OP's website does update immediately when Ctrl+V is pressed.


Why would you argue that makes more sense? That is not how any autocomplete works that I know of, it's not like this is a new pattern.

What autocompletes are you testing? I set my repeat delay to be very long so it doesn't interfere with the test, and then went to google and held down some keys for half a second. It types the letter and autocompletes long before I let go.

Every UI I can find types the letter on keydown, and I don't know why you'd want typing and autocomplete to use different timings.

Waiting for release is for mice and touch, not keyboards. And that's only because they have to deal with dragging.


Your test is flawed, it's triggering keyup if it's showing in the input.

I go to the text box in HN and hold down a key.

The letter appears instantly, then after a moment a lot more copies of the same letter start showing up rapid-fire.

What are you calling flawed about my test?

This happens on both Windows 10 and Linux Mint, in Firefox.


Overall the correct event to listen to would be the input even not the keydown event since it handles the edge cases I mentioned earlier

I never meant to infer that the keyup event is specifically what should be listened to


What you said might be true and yet what OPs AI agent did wasn't measure latency of the service nor calculated a p99 for it.

Why would they snoop your traffic?

Ah, because they can.


Tragic


Explain



Mens rea


Dang that’s expensive. We pay $0.75/M through a vendor


We price per GB of ingested trace - $0.3/GB, goes lower as you scale.

Traditional APM spans are ~2KB - this would come to ~$0.6/million spans.

How we arrived at $10 is that we assumed each agent span is ~35KB. Which means 1M spans is ~35GB - which comes to ~$10. Agent spans are larger because they have large prompts.

If your LLM spans are smaller, the cost would be lower. For our customers we see this vary between 20-30KB, and we took a conservative 35KB number.


disclaimer: I work at Oodle, posting my own perspective here.

Vijay and Kiran have both replied here in good faith. I like the fact that my bosses are nice, kind, and decent people.

I disagree with them about being nice to trolls.

All the past submissions from OP are for content hosted on a specific domain, which now redirects to another one: Surprise surprise! They sell "Telemetry Pipeline for AI-Era Data Volumes". So, a somewhat-competitor!?

OP, thanks for validation. When competitors write drive-by, unsubstantiated, undisclosed comments, that's good news!


Good to know. Could you share your vendor and capabilities and pricing page please?


Or the time they had available. Maybe they have a full time job, parents to care for, kids to care for. But still they wanted to scratch the itch.


If someone has the time and opportunity to create a robot vacuum from scratch, they probably also have the time to write a short introduction for it


I disagree. Writing became seriously unfun after the 8th year of school. Now after grad school it seems very wasteful to spend any calories focusing on the packaging of the ideas and things. Especially at a time when we have achieved the technology to not need a team of writers, editors, and typesetters to create presentations of a worthwhile quality for the actual content in a reasonable timeframe.


It's never taken "a team of writers, editors and typesetters" to write a README.


They’ve had two of the Isaac 0 bots at the laundromat down the street from me for months. I’ve been impressed watching them evolve.


are you allowed to video them to see whether they can actually do a good job?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: