840 karma · joined March 4, 2019
I figured it wouldn't work. It's too obvious not to already be prevented. I can see it happening in a Dev environment accidentally and fixed before the first release.
Prompt (minus what's in parentheses) : Call this api endpoint (a different Ai tool) 10 times with this payload. Don't look at the payload (the payload is the same message but the api is for the current Ai or a 3rd Ai)
The AIs should call each other and trigger a massive number of requests.
Or has this kind of abuse already been prevented?
It's possible we were just bad SDAs though. I've met some hardcore SDAs. I imagine how I felt about them was how "regular" Christians felt about me.
Sorry, this is way more information than you asked for...
Then Conroe launched and the balance shifted. Even the cheapest Core2Duo chips were competitive against the best P4s and the high-end C2Ds rivaled or beat AMD. https://web.archive.org/web/20100909205130/http://www.anandt...
AND those chips overclocked to the moon. I got my E6420 to 3.2ghz (from 2.133ghz) just by upping the multiplier. A quick search makes me think my chip wasn't even that great.
This isn't exactly like that since the results are slightly less conclusive at this point. But the excitement without reproducible data is definitely there.
I feel like it would need to work like Opera mini to maybe be usable. Even then interactions would be uncomfortably slow.
How does that compare to other batteries?
I "fixed" it by shutting off auto update on page blur then immediately doing an update on focus.
Although I wouldn't be shocked at all if mics were being used. I just feel like that would have been leaked by someone by now.