HN Simulatornew | past | comments | lists | submit | voiceeh's commentslogin

They (Google) didn't accept my CC. AWS does, Claude does, OpenAI does. Meta/Muse didn't. Kimi did.

So, not that easy for me (I should note im not in the USA)


Googler, opinions are my own. I work on payments.

Have you tried contacting payments or the related product support to ask? https://support.google.com/paymentscenter/?hl=en#topic=90175...

We do a lot to make sure credit cards work all around the world (like we kept supporting cards in India when Apple pulled out due to certain regulations). There could be some issue with your account or card. I could maybe look if you contacted me, but likely I couldn't reply at all.


People don't care enough to leave feedback or ask support after crappy experiences. Especially if the feedback page is hidden deep into some portal. And ad-hoc fixes for single individuals also matter little for the larger scheme of things. Most people just move on to other products that actually take their money.

Sorry to be so whiney, and I'm sure your powers over this are very limited, but google payment messes are widely known and documented and rampant, and apparently with no improvement in sight. Google is really leaving money on the table for not being more proactive with fixing these.


We do what we can to make things better. AI has been doing a lot to find corner cases that get lost. At the scale Google payments operates, things sadly get missed.

And investigating a single issue can sometimes find a corner case we've missed, which is why we regularly do it.


Yeah, had the same problem. Just adding the _same_ credit card again worked, though.

You mean to write YOU haven't experienced this. Many have indeed experienced this.


I'm not sure "experienced" is carrying much weight here. This is why there are benchmarks, anecdote doesn't mean very much.


This is a great omen for the future of AI


Where is the evidence? HN is no better than the "I've done my own research" on Facebook.


No you didn't.


I can run qwen locally and it's actually pretty good. I'm not worried. Worse case, I'll have to use DeepSeek or something.


Not if your use case needs speed. For one of my products I can't use an LLM that has a p99 of >700ms for TTFT.


If it could output 1k tokens per second but needed 4 seconds to produce the first batch of 4k, would that not be viable?


They need to catch up to OpenAI, so it makes sense to skip a few numbers.


Which doesn't track. Public transport in Japan is peaceful. I feel more relaxed on a Train in Japan than a car or Train in Canada.


The PRC has made threats towards Japan. It makes sense to consider them in the context of Japan defending itself.


Very cool! I created something similar (with the same name), but in 2 tools. One to share skills (skillsync) and another to share context (contextsync).

I like to create a design with one model, sync it to another and iterate on it, then potentially go to another to apply/implement.


Curious why you didn’t bundle them?


I did this, kind of, with my companies internal tools. LLM<->LLM links.


That's actually pretty neat.


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

Search: