Hacker Newsnew | past | comments | ask | show | jobs | submit | rietta's commentslogin

The server is not returning anything. Is this a honeypot that now has firewalled my IP for trying to see that page or is the site just hugged to death?

Change your DNS to something that respects you.

> is the site just hugged to death

This one. Works for me now. Good luck.


What is the best alternative that can run as a Docker image that mimics AWS S3 to enable local only testing without any external cloud connections?

For me, my only use for Minio was to simulate AWS S3 in docker compose so that my applications were fully testable locally. I never used it it production or as a middle ware. It has not sat well with me to use alternative strategies like Ruby on Rails' local file storage for testing as it behaves differently than when the app is deployed. And using actual cloud services creates its own hurdles of either credential sharing among developers and gets rid of the "docker magic" of being to run a single set up script and be up and running to change code and run the full test suite.

My use case is any developer on the team can do a Git clone and run the set up script and then be fully up and running within minutes locally without any special configuration on their part.


S3 is evolving rapidly. While sticking with the old MinIO image might work for the immediate short term, I believe it is not a viable strategy for the long haul.

New standards and features are emerging constantly—such as S3 over RDMA, S3 Append, cold storage tiers, and S3 vector buckets.

In at most two or three years, relying on an unmaintained version of MinIO will likely become a liability that drags down your project as your production environment evolves. Finding an actively maintained open-source alternative is a must.


Hence my question.

Have you heard of LocalStack’s AWS emulator? [1] It’s runnable within a docker container and has a high fidelity S3 service.

Disclosure, I’m a SWE at LocalStack.

[1] https://github.com/localstack/localstack


I like(d) LocalStack fine, but you've got the same kind of problem that Minio has.

> As a result of this shift, we cannot commit to releasing regular updates to the Community edition of LocalStack for AWS.

https://blog.localstack.cloud/the-road-ahead-for-localstack/


That’s fair. There’s still a free tier that you can use.

https://blog.localstack.cloud/the-road-ahead-for-localstack/...

But IMO, LocalStack community’s S3 service is pretty stable, so I’m doubtful there’ll be much parity drift in the short to medium term.


I work on SeaweedFS.

I am trying to support AWS S3 APIs as complete as possible.

Recently added support for Table Bucket, besides myriads of details, such as policies, STS, IAM, OIDC, WORM, lock and versioning, governance, etc.


for me its rustfs https://rustfs.com/

Anyone interested in keeping access should fork this open source repository now and make a local archived copy. That way when this organization deletes this repository there can still be access to this open source code.

In the Ruby on Rails space, we had this happen recently with the prawn_plus Gem where the original author yanked all published copies and deleted the GitHub repository.

On GitHub, when a private repo is deleted forks are deleted. But for public repos, the policy is different. See https://docs.github.com/en/pull-requests/collaborating-with-....

This is the latest of a sunset trap set for those of us who use Minio for local testing but not production use.


Spot on. The Criterion of Embarrassment is a powerful tool here; the fact that women were the primary witnesses to the resurrection is a classic example, given that a woman's testimony held little to no legal weight in 1st-century Roman or Jewish contexts. If you were inventing a myth to gain social traction, you simply wouldn't write it that way.

Your point about verisimilitude extends to Onomastics as well. Research shows that the New Testament Gospels accurately reflect the specific frequency of Jewish names in 1st-century Palestine. In contrast, Gnostic texts often use names that don't fit the era or geography, frequently showing 3rd-century Egyptian linguistic influences instead. It suggests the canonical authors had "boots on the ground" knowledge that the later Gnostic writers lacked.


This has been a source I’ve referred to on and off for years. It’s really interesting to read some things that don’t show up in our everyday Bible. Including things that were considered not canon by the early church. I enjoyed reading the translation of the Shepherds of Hermas. It was not the easiest to follow, but in a sense it was a very popular allegory like Pilgrim’s Progress was centuries later!


Interesting to hear someone discuss Hermas. I have never taken to it personally, but have attempted to get into it a few times. Hermas was very popular at one stage, and I've even heard some people argue that it should have been in the canon and the Book of Revelation taken out. (Although both books tend towards metaphorical imagery which is not always clear.)


It was certainly popular enough to be included in the 4th-century Codex Sinaiticus, which is the oldest extant "complete" Bible (Genesis through Revelation) in a single bound volume. Interestingly, in that manuscript, The Shepherd of Hermas and the Epistle of Barnabas actually appear right after the New Testament. The library has published scanned copies online at https://www.codexsinaiticus.org/en/. It is an epic resource for anyone studying this history or textual criticism.


Extremely interesting read. I need to go back over it again in detail on my computer not just my phone while holding my baby.

A key theme in a future fiction I am writing (slowly) is that all digital data has been lost and the time we are in now is known as a digital dark age where little is known about our society and culture. Resurrecting an archeologically discovered DVD is a key plot point I am working through. That it will be the first insight into our time in over a millennium. Other conflicting interests will be finally succeeding at re-introducing corn at commercial scale after all hope had been lost and past attempts at re-germinating from the frozen seed bank had failed for hundreds of years. It's a work in progress.


We are loosing so many of the legends. I don't distinctly watching the Chronicles when it first aired - was too young, not in the right market - but as a computer history nerd watching the videos on the Internet has been eye opening. It is also a really good way to get a sense just how advancing things were in the 1980s and how in many ways we have gone backwards in many areas.


Interesting. The model picked Trixie as the name for Debian 18, which is actually the name of Debian 13 which is a current release in 2025.


Very succinct, I agree.

I honestly have never heard anyone—even those executing it poorly—try to frame Servant Leadership the way the original author did here (the "curling parent" analogy).

I have certainly seen people fail badly at practicing this style, but that failure was invariably due to a lack of character, poor communication skills, or other individual execution matters, not an issue with the core concept of servant leadership itself.


I think the author is significantly straw-manning the concept of servant leadership.

The short take presented in the article doesn't match my lived experience with this style, both in secular and faith-based circles. The core idea is absolutely not that of a "curling parent." Instead, it embodies living the walk, walking the talk, and putting the team's needs before your own ego.

In fact, this profound concept goes all the way back to Jesus Christ, who modeled it by washing the feet of his disciples—a task reserved for the lowliest servant of the time. This act was deliberately shocking and context-defying. He effectively "turned the world upside down" by saying, "Anyone who wants to be first must be the very last, and the servant of all."

I'm not trying to proof-text, but this idea is ancient and deep. It's a profound leadership style that is unfortunately often executed poorly or misunderstood by modern practitioners. Poor execution doesn't invalidate the concept itself.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: