GM 🌞
Gzuuus
gzuuus@contextvm.org
npub1gzuu...a5ds
Forever learning, continuously buidling⚡
cryptoanarchism student
#noderunner#Bitcoin | #technology | #art | #electronics
If someone else wonders why nostree.me is down 👇
View quoted note →
This is really cool! 🔥 Amazing job @Schlaus Kwab
View quoted note →
> If “AI-rewriting” is accepted as a valid way to change licenses, it represents the end of Copyleft. Any developer could take a GPL-licensed project, feed it into an LLM with the prompt “Rewrite this in a different style,” and release it under MIT. The legal and ethical lines are still being drawn
Tuan-Anh Tran
Relicensing with AI-assisted rewrite
Exploring the chardet v7.0.0 controversy: Can an AI rewrite legally 'launder' a library from LGPL to MIT?
GM 🌞
"It’s not so much staying alive, it’s staying human that’s important" George Orwell
GM🌞
The saddest thing is... It was probably vibestriked 🥲
View quoted note →
There will be signs
Man i love this tune
GM🌞 Wild times ahead! Buckle your seatbelts, hug your loved ones, it's going to be a crazy ride!
> tl;dr Google spent over a decade telling developers that Google API keys (like those used in Maps, Firebase, etc.) are not secrets. But that's no longer true: Gemini accepts the same keys to access your private data. We scanned millions of websites and found nearly 3,000 Google API keys, originally deployed for public services like Google Maps, that now also authenticate to Gemini even though they were never intended for it. With a valid key, an attacker can access uploaded files, cached data, and charge LLM-usage to your account. Even Google themselves had old public API keys, which they thought were non-sensitive, that we could use to access Google’s internal Gemini.
View quoted note →
Google API Keys Weren
Google spent over a decade telling developers that Google API keys (like those used in Maps, Firebase, etc.) are not secrets. But that
LNVPS down? @Kieran