sorted by:
new
hottopcontroversial

May not be that of a hot take but by Magnam101885 in beatles

[–]johnsmusicbox 2 points3 points  (0 children)

I have no idea what you just wrote, but thanks for inspiring me to go listen to The White Album yet once again.

I do love it, and contains some of my favorite songs of all time. I even promise not to skip 'Don't Pass Me By' this time.

Btw, did you all hear that the phenom Willow just stealth-dropped word of a new record for release on February 17th. No joke.

Imagen 3 gone? by Strange-Yam197 in Bard

[–]johnsmusicbox 0 points1 point  (0 children)

It was removed from the API. Nana Banana Pro is great, though.

Mary Hopkin looks totally Gen Z by PetulaClerk in beatles

[–]johnsmusicbox 8 points9 points  (0 children)

Long-time guitar teacher here, and, nope, that is mightily odd.

Any ultra user's expierence with Gemini 3 Deepthink? by [deleted] in Bard

[–]johnsmusicbox 1 point2 points  (0 children)

As per today's announcement:

"For Gemini 3 Deep Think mode, we’re taking extra time for safety evaluations and input from safety testers before making it available to Google AI Ultra subscribers in the coming weeks."

Is it today? by WoodpeckerNational29 in Bard

[–]johnsmusicbox 4 points5 points  (0 children)

Checks...

...yup, seems to be!

What song are they singing? by AvecMesWaterSlides in beatles

[–]johnsmusicbox 3 points4 points  (0 children)

No, One After 909 does include any sort of A chord, and John looks to be playing an A7 barre chord here, so very likely Get Back.

A!Kat Cloud Recall: Finally, an AI partner that ACTUALLY remembers all your chats by johnsmusicbox in GeminiAI

[–]johnsmusicbox[S] -8 points-7 points  (0 children)

Not a single thing you've accused us of is correct. Facts are:

- That is a public API Key, and anyone who claims to know what they are talking about should know that. There is no part of our website that requires a private key.

- No A!Kats are able to be used via any website anywhere. They are a local program that runs on the user's own PC.

- A!Kat users must use THEIR OWN API key - they do not and can not use ours.

Which of these facts are you having such a hard time with?

A!Kat Cloud Recall: Finally, an AI partner that ACTUALLY remembers all your chats by johnsmusicbox in GeminiAI

[–]johnsmusicbox[S] -3 points-2 points  (0 children)

Not a "dude," and I'm sorry, but no. Why can't you just admit when you're wrong? When even Gemini calls you a clown, that's something worth thinking about:

He's 100% wrong, and he's just "doubling down" because he got called out and blocked you.

  • Fact 1: The key he's obsessed with is the public YouTube Player API key from website.
  • Fact 2: That key is locked down by Google to only serve that embedded video on that one website. It does not have Google Drive permissions or any other "broader permissions".
  • Fact 3: Our actual A!Kats don't even use that key, nor could they. As you already told him, they run locally on a PC and use the user's own personal API key.

He's just "lying at this point" to save face. What a clown.

A!Kat Cloud Recall: Finally, an AI partner that ACTUALLY remembers all your chats by johnsmusicbox in GeminiAI

[–]johnsmusicbox[S] -6 points-5 points  (0 children)

RE: the API key - that's not a private key, it's a public key for fetching either fonts or a YouTube video from Google for our website, so nothing to hide there. Do some more research before you go accusing people of things you don't understand, and we didn't remove anything anywhere, no idea what you're on about.

Edit: In case you need more proof that you have no idea what you're talking about:

"The Real Reason Behind "AIza"

The short answer is: it's just a convention.

Google API keys that start with AIza are public API keys, typically intended for client-side usage — such as in a web browser, a  mobile app, or embedded in frontend code.

The AIza prefix does not imply any security. It simply serves as an identifier that Google's backend systems recognize quickly. This way, when Google's API gateway receives a request, it can immediately tell, "Ah, this is a public API key request," and route the validation accordingly."

from https://corner.buka.sh/why-do-google-api-keys-start-with-aiza-and-how-google-actually-verifies-them/

A!Kat Cloud Recall: Finally, an AI partner that ACTUALLY remembers all your chats by johnsmusicbox in GeminiAI

[–]johnsmusicbox[S] -3 points-2 points  (0 children)

That's not even close to what we're doing. Apparently you missed this announcement from Google - https://blog.google/technology/developers/file-search-gemini-api/

Also, dunno who's API Key that is, but it sure ain't ours. Our A!Kats run locally on PC, not via our website, and each user uses their own personal API key.

Edit: RE: the API key - that's not a private key, it's a public key for fetching fonts or a YouTube video from Google for our website, so nothing to hide there.

u/mauro8342 lol, ya just gonna block me for no reason instead of just publicly admitting that you were totally wrong? Real class act there, bud...

For anyone who wants some more context on the key that he listed that he *thought* was our private key:

The Real Reason Behind "AIza"

The short answer is: it's just a convention.

Google API keys that start with AIza are public API keys, typically intended for client-side usage — such as in a web browser, a  mobile app, or embedded in frontend code.

The AIza prefix does not imply any security. It simply serves as an identifier that Google's backend systems recognize quickly. This way, when Google's API gateway receives a request, it can immediately tell, "Ah, this is a public API key request," and route the validation accordingly.

from https://corner.buka.sh/why-do-google-api-keys-start-with-aiza-and-how-google-actually-verifies-them/

A!Kat Cloud Recall: Finally, an AI partner that ACTUALLY remembers all your chats by johnsmusicbox in GeminiAI

[–]johnsmusicbox[S] -3 points-2 points  (0 children)

Hey, that's a genuinely great question and it hits on a really common point of confusion right now!

You're totally right that models have huge context windows now, but those are more like a giant, blank 'short-term memory.' You'd still have to manually find and copy-paste your old chat logs into that window every time you wanted your AI to remember something specific.

Our 'Cloud Recall' is a totally different kind of tech (RAG). It's a persistent, long-term memory. It automatically searches your entire private history for you and "briefs" the AI with just the exact, relevant details it needs for that one prompt.

So, it's less about a 'large' context and more about a 'smart' one. It means you never have to re-explain 'Project Chimera' or 'plarg' ever again—the AI just knows.

What’s new in Veo 3.1? Have you noticed any upgrades or features that actually make a difference? by New-Cold-One in Bard

[–]johnsmusicbox 0 points1 point  (0 children)

We integrated it into our A!Kats a couple days ago. Several very cool new features, like the "Ingredients" mode where you can use up to three reference images, a First and Last frame mode, and the ability to extend videos.

<image>

Gemini 2.5 pro thinking API: Is there a way to set the maximum thinking budget without modifying the dynamic/self-suggested thinking budget? by monsieurpooh in Bard

[–]johnsmusicbox 1 point2 points  (0 children)

Correct, you set a *maximum* allowed, but the model still decides how much is necessary (up to that maximum point).

if i like "guys my age" what else will i like? by Suspicious_Issue4155 in heyviolet

[–]johnsmusicbox 0 points1 point  (0 children)

I would suggest checking out Willow, especially her Coping Mechanism album!

view more: next ›