Fiveplus

The "commitment to open source" line in these press releases usually has a half-life of about 18 months before the telemetry starts getting invasive.

Great project and we definitely need to maintain these public lists. Well done!

I concur. It is an incredibly stupid practice for an e-commerce portal to distract or burden their users with anything other than the product they're viewing. I'm like, "Buddy, you have a potential paying customer at your doorstep, all you have to do is not insult them and they'll whip out their credit card on the next step."

Anyone reading this purely as a child safety or campaign finance story might miss the broader architectural war happening here. If you zoom out a little, this is the inevitable, scorched-earth retaliation for Apple's ATT rollout from a few years back.

Apple cost Meta billions by cutting off their data pipeline at the OS level, justifying it with a unilateral privacy moral high ground. Now, Meta is returning the favor. By astroturfing the App Store Accountability Act through digital childhood alliance, Meta is forcing Apple to build, maintain and also bear the legal liability for a wildly complex state-by-state identity verification API.

Gotta give it to Zuck. Standing up a fully-fledged advocacy website 24 hours after domain registration and pushing a bill from a godaddy registration to a signed Utah law in just 77 days is terrifyingly efficient lobbying.

The return of com.getpebble.android.provider.basalt is a very nice development. It revives the legacy plugin ecosystem overnight without requiring original developers (many of whom may be long gone) to push updates. Moving the app store native and switching iOS weather to WebSockets are also solid wins for latency, but I'm most curious about the package ID reclamation.

Has anyone else successfully recovered a dormant package name from Google Play recently? I was under the impression that once an original developer account goes inactive, those namespaces were effectively burned forever? Is that an incorrect assumption on my part?

We have officially reached the logical conclusion of the feature-bloat-to-vulnerability pipeline.

For nearly thirty years, notepad.exe was the gold standard for a "dumb" utility which was a simple, win32-backed buffer for strings that did exactly one thing...display text. An 8.8 CVSS on a utility meant for viewing data is a fundamental failure of the principle of least privilege.

At some point, they need to stop asking "can we add this feature?" and start asking "does this text editor need a network-aware rendering stack?"