seuros

7 ms·

1.
by seuros 1mo ago
The image is there for SEO and also to fill context window of people that can't read, before commenting.
2.
by seuros 1mo ago
I do write drivers, it is pretty very hard. The only thing AI there is the image (for SEO), everything else i wrote it myself. As for the purple, i had this color before AI took over, it a space the themed, but i get your point, i will chan
3.
by seuros 2mo ago
They can't! They waiting for a token reset.
4.
by seuros 5mo ago
I built this to give people that can't refrain from publishing packages to official registries, a way to purge that need. The platform will be totally controlled by AI, most of its source is already opensource. I will never sell it, or
5.
Show HN: [PKG47] AI-Controlled Package Registry(pkg47.com)
3 points by seuros 5mo ago|1 comments
6.
by seuros 7mo ago
This is crap .. the driver is untested piece of hallucination. I have exact MacBook and chipset that op is claiming to support. The driver doesn't even compile without modifications. It attach to the device, but you can't scan, as
7.
by seuros 1y ago
Author here: Let’s be clear on backups: Yes, I had backups everywhere. Across providers, in different countries. But I built a system tied to my AWS account number, my instances, my IDs, my workflows. When that account went down, all those
8.
by seuros 1y ago
Thank you for your concern, and I appreciate the nuance in your take. Yes, it is totally possible that AWS monitors blogs and forums for early damage control, like your company does. But we shouldn’t paint it like I was bailed out by some a
9.
by seuros 1y ago
That might be a 'lesson', but it’s like saying: "If you want your paperwork processed in Morocco, make sure you know someone at the commune, and ideally have tea with their cousin." Yes, it works, but it shouldn’t be the
10.
by seuros 1y ago
The AWS employee actually contacted me before my blog post even reached three digits in views. So no, it wasn’t PR-driven in the reactive sense. But here’s what I learned from this experience: If you are stuck in a room full of deaf people,
11.
by seuros 1y ago
The person paying the account is not the author, i'm. What happen is that the person paying for the account had to settle an invoice of many thousand of dollars. They offered me AWS gift cards,to send me electronics and they will pay
12.
by seuros 1y ago
Yeah, it's fishy. I never claimed the Java theory is confirmed, just that it’s what an insider told me after the fact. They said a dry-run flag was passed in the --gnu-style form, but the internal tool expected -dry, and since Java has
13.
by seuros 1y ago
The idea of a rogue AWS team running a deletion script without oversight should sound ridiculous. At a company that size of AWS, you will expect guardrails, audits, approvals. But here is the thing: no one from AWS has given me an official
14.
by seuros 1y ago
When you put a repo in Github, everybody that forked or clone that repo become a Mirror.
15.
by seuros 1y ago
My post is not about backup strategy, it’s about what happens when the infrastructure itself becomes hostile, and support throw you from one team to another. AWS didn't just delete files. They gaslit me for 20 days while violating thei
16.
by seuros 1y ago
I dont disagree with your broader point—centralizing everything in one provider is a systemic risk. The architecture was built assuming infrastructure within AWS might fail. What I didn’t plan for was the provider itself turning hostile, sk
17.
by seuros 1y ago
I did have backups. Multi-region. Redundant. I followed AWS’s own best practices to the letter. The only failure I didn’t plan for? AWS becoming the failure. The provider nuking everything in violation of their own retention policies. That’
18.
by seuros 1y ago
Not AI-generated. Not everyone is born writing flawless English. If it sounds like an LLM, maybe it is because people like me had to learn how to write clearly from LLMs because English is not our first language. I could’ve written in my na
19.
by seuros 1y ago
Hi, The infrastructure was not complex at at all, i can transfer it in 1 day. I was hospitalized, in another city, with all the computer at home, and locked behind 2FA. They send me is on notice on Thursday, by Monday evening, all access w
20.
AWS deleted my 10-year account and all data without warning(seuros.com)
229 points by seuros 1y ago|160 comments
21.
by seuros 1y ago
Same here, i used them for years. Feel you.
22.
by seuros 1y ago
No offense taken—you're absolutely right. In fact, I even added an em dash shortcut to my Logitech POP keyboard. That’s dedication. See? — — — — — I’m not just writing like this—I’ve industrialized it. If it sounds like a chatbot, mayb
23.
by seuros 1y ago
Circuit breakers are inherently bi-modal (all-or-nothing) while token buckets provide smooth pressure control like cruise control vs an on/off switch. BreakerMachines focuses specifically on failure protection rather than rate limiting
24.
by seuros 1y ago
Merci pour la remarque ! Your 2 space credits are worth their weight in dilithium. Funny thing is the gem originally started exactly like that, pure explicit constructors. Then I wrapped it with the DSL sugar but the explicit approach never
25.
by seuros 1y ago
I did split the readme now. Thank you again.
26.
by seuros 1y ago
Appreciate the feedback—really. You are correct to point out the mismatch on the image caption, i generated a few and copied the wrong one. That one's on me, i will update it later. And while AI might correct a typo or help rephrase a
27.
by seuros 1y ago
Hey HN! I extracted BreakerMachines from my apps after seeing people dealing with cascading failures in production Rails apps. Key features that set it apart: - True async/fiber support (works with Falcon, async gems) - Built-in fallba
28.
Show HN: BreakerMachines – Modern Circuit Breaker for Rails with Async Support(github.com)
45 points by seuros 1y ago|19 comments
29.
The Reality Check Nobody Talks About: What OSS Costs(seuros.com)
7 points by seuros 1y ago|1 comments
30.
by seuros 1y ago
Hi HN! I'm sharing COSS (Contribution Open Source Standard) addressing two big problems: vendor lock-in and AI computational waste. The AI angle: Current AI tools waste enormous compute re-analyzing the same project patterns. &quot

More ›