6 million. is that a lot? it's too bad they don't tell us.
but i think based on their statement that north of 90% of the buying repos were terminated by github, i'd say there would be very very many more fake stars without any github intervention.
i guess i just wish they hadn't made the first words of the article "Six million fake stars" without putting that into scale.
> One thing that surprised me is the [high] price [vs SES for example]
Not sure if you read the announcement closely:
> Sending email that actually reaches inboxes usually means wrestling with SPF, DKIM, and DMARC records. When you add your domain to Email Service, we configure all of it automatically. Your emails are authenticated and delivered, not flagged as spam.
Well played. I don't think many remember this. The product was completely forgettable but the introduction of this user hostile pattern was a turning point.
> That notice is meant to provide a chance to challenge the request.
That's the author's interpretation. The promise doesn't indicate anything of the sort (as of this writing). And users cannot challenge these requests -- users don't own the data (in the US). The promise is very clear that Google will provide the data, if the request is compliant.
Now the text of the notification was past tense, that the information was provided, whereas the promise is crystal clear that Google will notify before providing the info, but to me that could amount to a simplification of "we have verified that the request is legally compliant and will be providing the info to them in 250 ms".
Don't get me wrong, I'm not on Google's side. I'm a huge privacy nut. But the fix is to not give your info to Google, not trust that they will abide by any policy. Especially in a case like this where your freedom is at risk. Most people are completely unaware and unthinking but this guy seems that he was fully aware and placed his trust in Google.
Right, a PR is "just" a set of commits (all must be in the same branch) that are intended to land atomically.
Stacked PRs are not breaking up a set of commits into divisible units. Like you said, you can already do that yourself. They let you continue to work off of a PR as your new base. This lets you continue to iterate asynchronously to a review of the earlier PRs, and build on top of them.
You often, very often, need to stage your work into reviewer-consumable units. Those units are the stack.
You "just" need to know the original merge-base of PR B to fix this. github support is not really required for that. To me that's the least valuable part of support for stacked PRs since that is already doable yourself.
The github UI may change the target to main but your local working branch doesn't, and that's where you `rebase --onto` to fix it, before push to origin.
It's appropriate for github to automatically change the target branch, because you want the diff in the ui to be representative. IIRC gitlab does a much better job of this but this is already achievable.
What is actually useful with natively supported stacks is if you can land the entire stack together and only do 1 CI/actions run. I didn't read the announcement to see if it does that. You typically can't do that even if you merge PR B,C,D first because each merge would normally trigger CI.
EDIT: i see from another comment (apparently from a github person) that the feature does in fact let you land the entire stack and only needs 1 CI run. wunderbar!
a blog about traceroute in 2026. imagine that. hard to believe it could possibly be of any interest at all, especially written by someone that only just discovered it. but i'm oh so glad i stopped in, to learn about trippy! it looks amazing.
but i think based on their statement that north of 90% of the buying repos were terminated by github, i'd say there would be very very many more fake stars without any github intervention.
i guess i just wish they hadn't made the first words of the article "Six million fake stars" without putting that into scale.
reply