And "Firebase AI Logic" sure sounds like something easy to confuse with a Firebase service...
133 karma · joined October 16, 2025
And "Firebase AI Logic" sure sounds like something easy to confuse with a Firebase service...
<https://en.wikipedia.org/wiki/The_purpose_of_a_system_is_wha...>
> 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.
From Google themselves, in the Firebase docs:
> API keys for Firebase services are not secret. Firebase uses API keys only to identify your app's Firebase project to Firebase services, and not to control access to database or Cloud Storage data, which is done using Firebase Security Rules. For this reason, you do not need to treat API keys for Firebase services as secrets, and you can safely embed them in client code.
<https://firebase.google.com/support/guides/security-checklis...>
... or at least that's what it used to say, until they quietly updated the docs to say this:
> API keys for Firebase services are not secret. API keys for Firebase services only identify your Firebase project and app to those services. Authorization is handled through Google Cloud IAM permissions, Firebase Security Rules, and Firebase App Check.
> All Firebase-provisioned API keys are automatically restricted to Firebase-related APIs. If your app's setup follows the guidelines in this page, then API keys restricted to Firebase services do not need to be treated as secrets, and it's safe to include them in your code or configuration files.
Followed later by (in different section):
> Use your Firebase-provisioned API keys only for Firebase-related APIs. If your app uses any other APIs (for example, the Places API for Maps or the Gemini Developer API), use a separate API key and restrict it to the applicable API.
The problem is that despite using the same DVCS for source code management, other projects insist on a hub-and-spokes development model, which does not scale.
Projects would be a lot more productive (and a lot more resilient) if they also followed a model where "The <x> maintainer hasn't accepted my pull request" just wasn't a big deal.
https://dreamm.aarongiles.com/docs/v40/#intro-games
It doesn't list any Barbie titles. It's not the project that I'm thinking of.
I'm looking for that blog post, the list of titles, and the short subthread about it that I mentioned not being able to find.
I thought I remembered a recent update from one of the various API/engine re-implementation projects (e.g. something like but not necessarily ScummVM, Wine/Proton, or something associated with archive.org's Emularity project) that included a list of new titles that had become playable due to some recent fixes, and among those titles were (I thought) a bunch of Barbie and other low-budget franchise games in that vein. There wasn't any particular focus on these outside any of the other games listed—they were just mentioned in passing. Someone did bring it up in the comment section—maybe here on HN—but searching around didn't turn anything up.
Any ideas?
At the end of a talk about Oauth 2.0 at some indie or fediverse conference during lockdown, Aaron Parecki, who was then and still is employed at Okta, was asked if it might not be worth isolating the parts of the protocol/flow that actually requires a service (i.e. protocol-aware server in the loop) from those that don't, so that you could still get limited authentication/identity-tagging if your "provider" is your personal domain where you're just hosting static site. He immediately acted like he was addressing the dumbest person in the virtual room (it was a remote conference), telegraphing through his response that he might actually be on the verge of physical pain having to deal with such an imbecilic question.
GitHub customers really are willing to do anything besides coming to terms with the reality confronting them: that it might be GitHub (and the GitHub community/userbase) that's the problem.
To the point that they'll wax openly about the whole reason to stay with GitHub over modern alternatives is because of the community, and then turn around and implement and/or ally themselves with stuff like Vouch: A Contributor Management System explicitly designed to keep the unwashed masses away.
Just set up a Bugzilla instance and a cgit frontend to a push-over-ssh server already, geez.
GitHub is an SSO provider and has been for a long time. This criticism is ignorant.
Aside from that, there's nothing stopping anyone from using GitHub's dedicated message boards for message board stuff, or, before those existed, shunting it all off into the "issues" of a separate "$PROJECT/community-bullshit" "repo" instead of cluttering up the actual bugtracker.
> Social media... yikes. No, no, no.
I'm talking about the appropriate-for-social-media stuff people are already posting on GitHub issues. It's like you started writing your comment and lost the context. People are today already misusing GitHub issues for this. I'm saying keep the stuff best kept to social media and email... on social media and email. Don't clutter the bugtracker with it, and for project managers: don't let other users do it either. (You will lose contributors who know how to use a bugtracker efficaciously and are accustomed to it but have a fixed time budget and don't want to have to sift through junk for the privilege of doing free and thankless QA on your software.)
> You will drown in spam.
The irony. Help. It burns.
For emphasis: Everything that isn't a bug belongs on a message board, mailing list, or social media, and not on the bugtracker. Anyone who can't abide by this simple, totally reasonable request should be booted.
If you set user.email using git-config on your machine to a real email address and decide to author and publish commits with it, then GitHub will, of course, not be able to stop you (aside from maybe rejecting the commits when you tried to push them). It can't just arbitrarily rewrite the email address in the commit. That would break Git's data model.
1. Clear steps to reproduce (ideally, using the prepared testcase as input, if applicable)
2. A description of the behavior observed from the program
3. A description of the expected behavior
4. Optionally, your justification for why the program should be changed to behave the way described in #3 and not #4
Everything else belongs on a message board, mailing list, or social media.
But this is all totally foreign to, like, 80% of GitHub's userbase (including the majority of the project managers aka maintainers who are in charge of allowing/disallowing the sorts of things that people post as a way of shaping the tone and tenor of the space).
document.querySelector("#content .section-header + p").className = "date"
document.querySelector("#content .date + p").outerHTML = (`
<p>
We are pleased to announce the release of Ardour 9.0.
</p>
<p style="font-style:italic; font-size:smaller; margin:2em
4em">Ardour is a free and open-source digital audio workstation
app that works cross-platform on Linux desktops, Mac OS, and
Windows. Get Ardour or get involved with the community at <a
href="https://ardour.org/">Ardour.org</a>.</p>
<p>
Ardour 9.0 is a major release for the project, seeing several
substantive new features that users have asked for over a long
period of time. Region FX, clip recording, a touch-sensitive
GUI, pianoroll windows, clip editing and more, not to mention
dozens of bug fixes, new MIDI binding maps, improved GUI
performance on macOS (for most)...
</p>
`)The comments about web stack stuff is probably off. Godot is already a pretty featureful UI framework + form designer that makes anything the "frontend" world has ever produced seem like they only had a fraction (1-to-10%) as much time and resources to build, compared to what Godot was already shipping in 1.0, (even though the reverse is true).
> But they’re fast, and there are effectively infinitely many of them.
That's like saying you can hire effectively infinitely many human workers, because there are 8+ billion people on Earth.
Even though they're cheaper than humans ($200 gets you a month of passable work, rather than a single day), USD is still one of the limiting reagents that determines how much you can get out of them.
So you don't dispute the thesis that the hypothetical general-purpose machine described in the comment would have needed to have been been better than the PS2?
A "native" text editor, style properties viewer, profiler timeline, (and more, e.g., animation curve editor), instead of the ones we've got (like the one in Firefox, that they wrote in React[1] where you can see visible, whole-panel flicker when the UI repaints itself every time the cursor blinks)? Yes, please.
1. <https://firefox-source-docs.mozilla.org/devtools/frontend/re...>
That's the difference between the original "free software" community and the "open source" one to me, including its modern incarnation on GitHub: the former produces a collaborative effort to develop a UNIX replacement/alternative and a thriving ecosystem around free software desktop environments with apps intended for humans to do their personal computing. The latter gets you Apache Kafka.
Besides the library, the PS2 is the most successful video game console of all time in terms of number of units shipped, and it stayed on the market for over ten years, featured a DVD drive, and at one point was positioned by Sony not just as an entertainment appliance but as a personal computer, including their own official PS2 Linux distribution.
In a more perfect world, this would have:
(a) happened with a hypothetical hardware platform released after the PS2 but before the PS3, with specs lying in between the two: a smidge better than the former, but not quite as exotic as the latter (with its Cell CPU or the weird form factor; whereas the PS2's physical profile in comparison was perfect, whether in the original form or the Slim version), which could have:
(b) resulted in a sort of standardization in the industry like what happened to the IBM PC and its market of clones, with other vendors continuing to manufacture semi-compatible units even if/when Sony discontinued it themselves, periodically revving the platform (doubling the amount of memory here, providing a way to tap into higher clock speeds there) all while maintaining backwards compatibility such that you would be able to go out today and buy a brand new, $30 bargain-bin, commodity "PS2 clone" that can do basic computing tasks on it (in other words, not including the ability to run a modern Web browser or Electron apps), can play physical media, and supports all the original games and any other new games that explicitly target(ed) the same platform, or you could pay Steam Machine 2026 prices for the latest-gen "PS2" that retains native support for the original titles of the very first platform revision but unlocks also the ability to play those for every intermediate rev, too.
If they had trouble with Git on GitHub, and then left GitHub for Codeberg, where they also have to use Git, then that would be very strange.
Instead, they had trouble with GitHub, so they left GitHub, which makes perfect sense.
Codeberg is also a Git-based project host. It doesn't even support other repo types. Why would you be expecting the latter?
If a project announcement or article headline says someone/something is quitting or leaving GitHub, it makes a lot of sense to assume that their issue is with GitHub (and in this case, it would be an assumption they'd be right about).