#ratelimiting — Public Fediverse posts

Scoop: #WSocial has been experiencing major technical problems for over a week: it is effectively a ghost town, filled with thousands of new accounts that cannot use the platform.

Because my new article contains a possible solution to their problem, by the time you read this the issue may have been fixed. Or not. It has been going on for 7+ days, with complete radio silence by its developers and founders.

My exclusive:

🔗 : https://blog.elenarossini.com/w-social-a-broken-ghost-town/

#SocialMedia #ATproto #RateLimiting

When the edge is not yours and you cannot put Varnish in front, it is time to rate limit your Rails app from the inside 🛡️.

We are diving into how rack-attack works and why Rails 8 now ships with these quality of service protections out of the box 🚀

Read more to see how we are handling authenticated traffic and middleware configuration

👉 https://developer.upsun.com/posts/insights/rate-limiting-rails-apps-when-you-cant-put-varnish-in-front

#Rails #WebDev #RubyOnRails #RateLimiting

Modernizing .NET Part 26! 🛡️

Today we’re implementing the Rate Limiting Middleware in ASP.NET Core.

✅ Concurrency control
✅ Stable response times under load
✅ No more cascading failures

https://medium.com/@michael.kopt/%EF%B8%8F-modernizing-net-part-26-implementing-rate-limiting-middleware-in-asp-net-core-29eb8451d762
#dotnet #csharp #dotnetcore #aspnet #aspnetcore #ratelimiting #performance

#Development #Challenges
Web­space invaders · Let’s level up our anti-AI scraping game! https://ilo.im/16ahl8

_____
#AI #Crawlers #RobotsTxt #RateLimiting #WAFs #Cloudflare #IndieWeb #WebDev #Frontend #Backend

Одно кольцо, чтобы повелевать остальными: собираем лимитирование, ретраи и circuit breaker в одной библиотеке

Я чувстовал себя клоуном подключая 5ю библиотеку для написания устойчивого к ошибкам API клиента. После этого я написал библиотеку объединяющую все воедино. Мотивация и история архитектурных решений.

https://habr.com/ru/articles/992902/

#отказоустойчивость #отказоустойчивые_решения #отказоустойчивые_системы #отказоустойчивая_архитектура #python #ratelimiting #retry #pypi

📌 Hướng dẫn nhanh về Rate Limiting cho API:
🛑 Ngăn chặn client “đánh rơi” API bằng cách đặt giới hạn.
🔧 Bắt đầu với giải pháp in‑memory đơn giản; mở rộng dùng Redis để hỗ trợ nhiều server.
☁️ Hoặc dùng API Gateway của cloud (AWS, GCP) để tự động scale & bảo vệ DDoS.
⏱️ Áp dụng token‑bucket, trả về header X‑Rate‑Limit và mã 429 kèm retry‑after.
📈 Giám sát vi phạm, thiết lập mức limit theo tier (user, IP).

#API #RateLimiting #Redis #APIGateway #Tech #Lập_trình #Công_nghệ #Bảo_mật

Rate limiting simple avec Nginx.

🔗 https://joshtronic.com/2025/11/09/rate-limiting-nginx/

#nginx #ratelimiting

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.

• Explotación Masiva: Al explotar esta falla, los investigadores pudieron probar secuencias de números de teléfono de forma masiva. En solo media hora, lograron extraer 30 millones de números de WhatsApp registrados en Estados Unidos. Al finalizar su investigación, habían recolectado los números de teléfono de 3.500 millones de usuarios a nivel mundial.
• Exposición de Perfiles: La falta de limitación no solo expuso los números, sino también la información de perfil. Los investigadores pudieron recolectar las fotos de perfil del 57% de esos usuarios y ver el texto de perfil del 29%, ya que la configuración de privacidad de estos usuarios permitía la visualización pública.

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 #tecnologia2 #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 меня спас.

https://habr.com/ru/articles/963880/

#python #asyncio #semaphore #ratelimiting #performance

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.

#golang #ratelimiting #rate

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?

#http #curl #golang #webdev #api #ratelimiting

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.

#ageVerification #feed #overload #rateLimiting #reddit #tor

🎉 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

Updated rate limits for unauthenticated requests

https://github.blog/changelog/2025-05-08-updated-rate-limits-for-unauthenticated-requests/

#HackerNews #UpdatedRateLimits #UnauthenticatedRequests #HackerNews #APIChanges #RateLimiting #TechNews

🚀 Oh wow, #Supabase is now officially the golden child of the "Too Many Requests" club, raising $200M to ensure even MORE requests get queued. 🙄 I guess their new valuation proves that rate limiting is the new black in tech fashion! 💸
https://finance.yahoo.com/news/exclusive-supabase-raises-200-million-112154867.html #TooManyRequests #TechFashion #FundingSuccess #RateLimiting #HackerNews #ngated

#ReleaseMonday — One of the recent (already very useful!) new package additions to #ThingUmbrella is:

https://thi.ng/leaky-bucket

Leaky buckets are commonly used in communication networks for rate limiting, traffic shaping and bandwidth control, but are equally useful in other domains requiring similar constraints.

A Leaky Bucket is a managed counter with an enforced maximum value (i.e. bucket capacity). The counter is incremented for each a new event to check if it can/should be processed. If the bucket capacity has already been reached, the bucket will report an overflow, which we can then handle accordingly (e.g. by dropping or queuing events). The bucket also has a configurable time interval at which the counter is decreasing (aka the "leaking" behavior) until it reaches zero again (i.e. until the bucket is empty). Altogether, this setup can be utilized to ensure both an average rate, whilst also supporting temporary bursting in a controlled fashion...

Related, I've also updated/simplified the rate limiter interceptor in https://thi.ng/server to utilize this new package...

#ThingUmbrella #DataStructure #RateLimiting #OpenSource #TypeScript #JavaScript