Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://social.wildeboer.net/users/jwildeboer/statuses/117179143797479215">Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Sunday, 30-Aug-2026 04:03:36 JST</a><a href="https://social.wildeboer.net/@jwildeboer" title="jwildeboer@social.wildeboer.net"><img src="https://gnusocial.jp/avatar/2767-48-20251201222121.webp" width="48" height="48" alt="Jan Wildeboer 😷:krulorange:" style="position: absolute; left: 0; top: 0;">Jan Wildeboer 😷:krulorange:</a><div><ul><li></ul></div></section><article><p><a href="https://toot.liw.fi/@liw">@liw</a> It's the same. But the methods have changed. What happens now is that these "residential proxy" providers go to app/device developers and make them a simple offer: add our library and we will pay you for every active user. That library just steals network bandwidth from unsuspecting users that the "residential proxy" provider sells to whoever wants to use that bandwidth. So it's BaaS, Botnet as a Service.</p><p>See <a href="https://jan.wildeboer.net/2025/04/Web-is-Broken-Botnet-Part-2/" rel="nofollow">https://jan.wildeboer.net/2025/04/Web-is-Broken-Botnet-Part-2/</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/6656756#notice-13102115">In conversation</a><time datetime="2026-08-30T04:03:36+09:00" title="Sunday, 30-Aug-2026 04:03:36 JST">about a month ago</time> <span>from <span><a href="https://social.wildeboer.net/@jwildeboer/117179143797479215" rel="external" title="Sent from social.wildeboer.net via ActivityPub">social.wildeboer.net</a></span></span><a href="https://social.wildeboer.net/@jwildeboer/117179143797479215">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: jan.wildeboer.net</div><h5><a href="https://jan.wildeboer.net/2025/04/Web-is-Broken-Botnet-Part-2/">Botnet Part 2: The Web is Broken</a></h5><div></div></header><div>I guess you have all heard about the growing problem of AI companies trying to aggressively collect whatever data they can get their hands on to train their models. This has caused an explosive surge in web crawlers relentlessly hitting servers big and small. But who runs these crawlers? Turns out — it could be you!</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Sunday, 30-Aug-2026 04:03:36 JSTJan Wildeboer 😷:krulorange:
- Lars Wirzenius
@liw It's the same. But the methods have changed. What happens now is that these "residential proxy" providers go to app/device developers and make them a simple offer: add our library and we will pay you for every active user. That library just steals network bandwidth from unsuspecting users that the "residential proxy" provider sells to whoever wants to use that bandwidth. So it's BaaS, Botnet as a Service.
See https://jan.wildeboer.net/2025/04/Web-is-Broken-Botnet-Part-2/
In conversationabout a month ago from social.wildeboer.netpermalink
Attachments
1. Domain not in remote thumbnail source whitelist: jan.wildeboer.net
  Botnet Part 2: The Web is Broken
  I guess you have all heard about the growing problem of AI companies trying to aggressively collect whatever data they can get their hands on to train their models. This has caused an explosive surge in web crawlers relentlessly hitting servers big and small. But who runs these crawlers? Turns out — it could be you!

Public

Embed Notice

HTML Code

Corresponding Notice