Funny, I was automatically refunded for a pair of shoes that Amazon thought I never received even though I’m wearing them right now. I couldn’t even find a way to dispute the refund so I just took the win…
This would be a useful feature to bake into the commits generated by agents. Heck you don’t even need to wait — just change your prompt to tell it to include more context in its commit messages and to sign them as Claude rather than yourself…
>Iran which is why Israel struck at daytime because
Israel struck because they had info that some people were going to be at a specific place at a specific time. One would suppose they could have chosen Saturday for another reason only if they had the luxury of continuous intelligence providing multiple options with equal chances of success. In that case, choosing that day to avoid unnecessary economic volatilty for you and your allies makes sense.
That the copyright notice on their site still says "2025" probably says a lot. I was kinda expecting to find an AI pivot when I opened that landing page.
For what it’s worth, they are living a AI pivot. TOS just changed so they keep transcripts of all voice and actually pop it into an LLM to subjectively determine your karma points. They are absolutely selling audio data for fine tuning purposes imho, and they are absolutely training on all audio. It’s a AI shovel selling company for sure.
And people wonder why others say we are living in a "low trust society". You can only read a story like this so many times before you decide to simply opt out of society.
The S3 API is quite stable and most new features are opt-in (e.g. ApplyIfModified) or auxiliary (e.g. S3Tables). It’s highly unlikely that S3 proper will break backwards compatibility for clients with any future API change. So if all you need is basic object storage that works with existing S3 clients, then MinIO is enough. The fork just needs to keep CVEs patched and maintain community hygiene (accept new PRs for small bug fixes, etc.). And as the author points out, this is much easier in the age of AI than it might have been previously.
I can't see how Amazon is incentivized to avoid making any changes that break compatibility for their imitators, so long as their first party SDKs continue working. Standardized feels like it should be suffixed with "as long as Amazon doesn't ever feel like evolving the product further".
I think my point doesn't really land. I was trying to express the idea "S3 is not a standard where AWS is the reference implementation, it is a successful commercial product with many many copy cats".
Their only real inherent commitment here is to whatever backwards-compatibility expectations are being set for their first-party SDKs. If they fulfill that but other vendors can't or won't follow suit, the outcome is gonna be different than it would be for an actual standard rather than an assumed one. There is no meaningful leverage for the third parties to exert to force a community-favored outcome if Amazon decides otherwise.
If amazon changes the API they've angered their entire customer base that relies on the API. Sure, some will stick around if they're fully entrenched by the ecosystem, but others will be able to leave, and they will, because hey, S3 is a standard-ish API.
It would be pretty shocking for Amazon to break the S3 API at this point. There is a huge 3rd party ecosystem that would be affected. For example, in Rust land the object_store crate is at least as popular as the official SDK.
From whatI can tell, "s3 compatibility" usually means compatibility with some subset of the actual s3 API. And what subset that is varies a fair amount between projects.
> crime, jobs, the economy, inflation, and health care
These are the post-facto rationalizations voters cite to explain or defend their vote. But the actual decision is made much earlier than voting time, and it’s one driven primarily by emotion and social influence. The “issues” are a convenient alignment mechanism but not the primary motivator.
This should be obvious by the fact voters must choose between two viable candidates – the choice has been made for them, long before they get the luxury of sorting through which issues are most important to their vote.
> that isn't offered by native blocking/existing extensions
There is no “native blocking” on HN. You cannot block a user or hide their comments and submissions in perpetuity. You can only hide on a per-story basis.
reply