levleontiev
Joined 11 years ago
Karma
36
Submissions
31
Member since
Jul 11
Recent submissions
Comment · 7 months ago
Comment · 9 months ago
I am terribly sorry for self-advertising, but:
I am just now busy building a solution: self-hosted sophisticated rate-limiting.
More complex than nginx, more private than cloudfare. Please joint the waitlist if you want to morally support me ;)
Comment · 1 year ago
That's why I am building a Rate Limiter as a service.
Seems that it has its niche.
Comment · 2 years ago
Sorry if I trigger anyone's paranoia, but
1. who told you that it's not a state-backed attack?
2. and if 1 is true, who told it, it's not Russia staying behind it?
and if 2 is true, the KGB university alumni Kaspersky definitely is related to it.
Comment · 2 years ago
>does he get penalized if part of the dev team gets hired by another company, which makes it harder for him to hit the milestones?
Of course yes. The part of executive responsibility is to maintain the team and calculate the riscs .
Comment · 3 years ago
Is it only me who sees BDSM logo here?
Comment · 3 years ago
Also interesting that a new “bad guy” from the Caucasus might be the actual attacker.
Comment · 3 years ago
and it's even not the first goverment backed attacks:
https://www.qurium.org/alerts/news-media-websites-attacked-f... (2017)
https://about.fb.com/wp-content/uploads/2022/04/Meta-Quarter... (2022)
The problem: one buggy integration, scraper, or infinite retry loop can suddenly explode your API costs or overload infrastructure before anyone notices.
Fairvisor acts as a guardrail in front of your API:
per-tenant and per-route rate limits
request budgets and soft/hard caps
anomaly alerts for sudden spikes
The edge component is open source (OpenResty / Nginx + Lua) and the SaaS part provides policy management and audit.
Still early, validating whether teams would use something like this instead of building internal scripts.
https://github.com/fairvisor/edge