Одно кольцо, чтобы повелевать остальными: собираем лимитирование, ретраи и circuit breaker в одной библиотеке
Я чувстовал себя клоуном подключая 5ю библиотеку для написания устойчивого к ошибкам API клиента. После этого я написал библиотеку объединяющую все воедино. Мотивация и история архитектурных решений.
https://habr.com/ru/articles/992902/
#отказоустойчивость #отказоустойчивые_решения #отказоустойчивые_системы #отказоустойчивая_архитектура #python #ratelimiting #retry #pypi
Token Bucket Rate Limit
Smooth bursts without letting bots flood your API.
#php #python #ratelimiting #tokenbucket #api #botdefense #performance #reliability #backendsafety #viralcoding
@Air_Quotes_Comedian @admin still happening, suspect it might be another of those #rateLimiting things [like only 4 search results] that seem to afflict masto servers when the load on them is heavy. someone's even made the longest hashtag I've seen for it, which I've followed: #503RemoteDataCouldNotBeFetched
#RateLimiting issues on #mastodon #servers
As it becomes more popular, these are going to be experienced by more users. We just revealed one in the linked thread.
Here's another, and a work-around - large media files in posts. If I go to a post from an instance I dont often visit, images etc may be missing. Not a lot happens for several minutes, even if I repeatedly attempt to load the image.
#workaround [right-] click-hold on the image etc and choose open in new browser tab, it loads instantly, with the url being to the post's host site [without all the rest of the site you get if you use [...]>"open original page"
https://climatejustice.social/@wavesculptor/115872885582390334
[ edit - cc mention @MastodonEngineering
]
Live Chat Spam Lockdown in 60 Seconds
Sliding window rate limit that saves your live event.
#python #php #ratelimiting #livechat #spamprotection #slidingwindow #viralcoding #codecomparison #realtime #developertips #performance
Class Variable Shared Between ALL Instances Breaking Rate Limits?!
CLASS VARIABLE DISASTER! All instances share SAME list! User A's requests counted in User B's limit! 470K users randomly blocked! $2.3M lost API revenue! Rate limiter architect FIRED!
#python #pythondisaster #classvariable #sharedstate #ratelimiting #productionbug #pythonshorts #pythonwtf #instanceconfusion #careerending #apithrottling #oop
CEO một SaaS bất ngờ "tự DDoS" người dùng do lỗi code! Khi Redis gián đoạn, hệ thống trả về 429 cho mọi yêu cầu. Lỗi đến từ việc return false khi Redis down. Cách sửa: return true để giữ luồng traffic. Bài học: Ưu tiên "fail open" với rate limiting, luôn lường trước rủi ro hệ thống. #SaaS #DevOps #RateLimiting #FailOpen #HeThong #LamViecNhóm
https://www.reddit.com/r/SaaS/comments/1pv0z0d/i_accidentally_ddosd_my_own_users_a_saas_horror/
Get the comments posted to the artwork.
https://www.pixiv.net/ajax/illusts/comments/roots?illust_id={ARTWORK_ID}&offset={OFFSET_COUNT}&limit={LIMIT_COUNT}
Method: GET
Referer: https://www.pixiv.net/artworks/{ARTWORK_ID}
Rate limiting simple avec Nginx.
El fallo de WhatsApp que expuso los números de teléfono de 3.500 millones de usuarios
Investigadores de la Universidad de Viena descubrieron que una vulnerabilidad de seguridad, conocida por Meta desde 2017, permitió extraer los números de teléfono de 3.500 millones de usuarios de WhatsApp a nivel mundial. La falla residía en la ausencia de una limitación de frecuencia ( rate-limiting ) en la función de «descubrimiento de contactos», lo que facilitaba a los atacantes el scraping masivo de números. Afortunadamente, Meta implementó protecciones más estrictas en octubre de 2025 para corregir este fallo (Fuente y Datos).
Un equipo de investigadores de seguridad de la Universidad de Viena en Austria ha revelado una vulnerabilidad crítica y simple en WhatsApp que, al ser explotada, permitió la exposición potencial de los números de teléfono de miles de millones de usuarios.
El Fallo de Diseño y el Scraping
La vulnerabilidad se encontró en la función básica de WhatsApp que permite a los usuarios buscar un número de teléfono para verificar si está registrado en la plataforma. Los investigadores descubrieron que WhatsApp carecía de protección de limitación de frecuencia ( rate- limiting ), una medida de seguridad que evita el abuso de dicha función.
Falta de Acción Previa de Meta
Lo más preocupante es que Meta, la empresa matriz de WhatsApp, tenía conocimiento de una falla similar desde 2017, reportada por otro grupo de investigadores. En ese momento, Meta no tomó medidas suficientes. Los investigadores austríacos informaron sus hallazgos a Meta en abril del año actual, advirtiendo sobre el grave riesgo de que actores maliciosos pudieran usar el truco para robar datos a gran escala.
Afortunadamente, en octubre de 2025 , Meta finalmente impuso una medida de limitación de frecuencia más estricta, lo que detiene la posibilidad de realizar descubrimientos de contactos a escala masiva. Los investigadores han confirmado que han eliminado de forma segura su base de datos recolectados.
El incidente subraya la necesidad de que las aplicaciones con cifrado de extremo a extremo (como WhatsApp, que promueve su seguridad) también implementen protecciones básicas a nivel de plataforma, un área donde competidores como Signal ya estaban avanzados.
#arielmcorg #ciberseguridad #infosertec #meta #numerosdetelefono #portada #privacidad #ratelimiting #scraping #seguridad #tecnologia #vulnerabilidad #whatsapp
#Development #Approaches
Rate-limiting requests with Nginx · An alternative approach to counter AI crawlers https://ilo.im/168axr
_____
#RateLimiting #Nginx #WebServer #AI #Scrapers #RobotsTxt #DevOps #WebDev #Backend
Как не положить API: rate limiting в Python
История о том, как я случайно устроил DDoS на внутренний API, обрабатывая 10 миллионов векторов. И как asyncio.Semaphore меня спас.
Fiz uma prova de conceito rápida e simples para testar um controle de vazão de requisições em Go (uma API HTTP em Go recebendo tráfego). Implementei do zero, sem pegar exemplo de documentação, sem sugestão de Copilot da vida, sem ler nenhuma referência.
Considerando minhas habilidades medianas, ficou bem eficiente e deu os resultados esperados. Nota 10/10.
I am wondering how website admins feel about HTTP rate limiting.
If a rate limit is declared both in the documentation, and is exposed through headers, and I implement the HTTP client with a token bucket rate limiter that behaves exactly as requested by the documentation (N requests every M time), are the admins happy?
I presume, if the server was 'unhappy' in any way, it could issue a GOAWAY error, in which case I can back off. But if I stay very close to the rate limit and simply continuously do requests (24/7), is that something that the server admins will be happy about?
f(x) = 9.6000 + 0.7459 * sin(1 * x + -1.459) + 0.0321 * sin(2 * x + 2.367) + 2.5724 * sin(3 * x + -1.166) + 6.0682 * sin(4 * x + -0.417) + 1.8330 * sin(5 * x + -1.904) + 2.7066 * sin(6 * x + -2.837) + 0.5208 * sin(7 * x + 2.207) + 1.0797 * sin(8 * x + -1.789) + 2.4578 * sin(9 * x + 2.200) + 1.4048 * sin(10 * x + 3.059) + 1.1191 * sin(11 * x + 2.544) + 1.8734 * sin(12 * x + 0.249) + 0.8845 * sin(13 * x + 0.848) + 1.8114 * sin(14 * x + 0.789)
Reddit appears to be mildly struggling with a sudden influx of traffic over Tor; hopefully they will make some tweaks to help it real soon now
https://alecmuffett.com/article/113756
#AgeVerification #RateLimiting #overload #reddit #tor
Reddit appears to be mildly struggling with a sudden influx of traffic over Tor; hopefully they will make some tweaks to help it real soon now
See the image; similar overloading also seems to be affecting the Reddit Onion site.
I can’t think why it’s happening, but I’m sure they will sort it out soon. Vulnerable people are being prevented from accessing any content which is labelled as NSFW, including: alcoholism recovery, bulimia, domestic violence discussions…
Oh, and porn.
@troed @dalai @foone The problem will be that one will have to reimplement the "#API" as #api0 from scratch by running inspectors in browsers all the time...
It'll necessitate all api 0 calls to come from the same #IPv4 and/or #IPv6 as the end-user and hide itself with a fake #UserAgent to prevent countermeasures like #RateLimiting and #blocking.
🎉 Welcome to "Sagyam's Super Fun Guide to Rate Limiting" - because who wouldn't want to spend their weekend playing with token buckets? 💼🤖 Forget Netflix and chilling, it's all about server starvation prevention! 🙃📉
https://blog.sagyamthapa.com.np/interactive-guide-to-rate-limiting #SagyamGuide #RateLimiting #TokenBuckets #ServerStarvation #FunLearning #HackerNews #ngated
An Interactive Guide to Rate Limiting
https://blog.sagyamthapa.com.np/interactive-guide-to-rate-limiting
#HackerNews #InteractiveGuide #RateLimiting #TechTutorials #WebDevelopment #CodingBestPractices
