subignition

I am WAY too unqualified to understand any of the technical stuff, so I’ll be waiting to hear thoughts from experts on this one. It looks like if there are no major flaws in it this is a great thing for the platform overall.

I am a bit out of the loop in terms of RDBMS history, what do you mean by MySQL refugees?

If functionality exists in the client app, there’s nothing to be done to stop someone from bypassing checks.

Looking into it further this looks like it’s an API between the backend of a service and Google though. That would be difficult to defeat, but you could probably spoof the identity of the requesting device with enough effort

It’s not like dedicated people aren’t going to be able to just patch out the calls to this API from the apps themselves…

This feels like yet another attempt at DRM that is doing more harm than help.

Damn, you’re living in the future. I’m still stuck using three shells.

Well today I learned, thanks for the correction.

They’re pretty reasonable for consensus-based programming prompts as well like “Compare and contrast popular libraries for {use case} in {language}” or “I want to achieve {goal/feature} in {summary of project technologies}, what are some ways I could structure this?”

Of course you still shouldn’t treat any of the output as factual without verifying it. But at least in the former case, I’ve found it more useful than traditional search engines to generate leads to look into, even if I discard some or all of the specific information it asserts

Edit: Which is largely due to traditional search engines getting worse and worse in recent years, sadly

The “P” is for predictive, not pre-trained. Generative Predictive Text

Edit: Nope I was wrong.

This is the best article I’ve seen yet on the topic. It does mention the “how” in brief, but this analogy really explains the “why” Gonna bookmark this in case I ever need to try to save another friend or family member from drinking the Flavor-Aid