Problems are Solved by Method\" 🇦🇺👨💻👨🦯🏹♔ 🏓⚯ 👨👩👧👧🛥 -- James Mills (operator of twtxt.net / creator of Yarn.social 🧶)
If this user/feed is violating this Pod's (yarn.meff.me) community guidelines as set out in the Abuse Policy, please report them immediately!
You are also free to Unfollow or Mute this user or feed. Muting will also remove that user/feed's content from your view and you will no longer see content from that user/feed anywhere.
@prologic does not follow you (they may not see your replies!)
So blackholing my Gitea instance’s DNS for the day seemed to have worked 🤣 (if only I had a real target I could have made their fucking crawlers DDoS themselves 😂) – Let’s also see if enabling DDoS proection on the Edge via Vultr’s DDoS capability also helps? 🤔
(#h3pxyfq) @movq@www.uninformativ.de sorry dude I think we’re getting our language confused. I think I actually meant private Internet connections.
Something I caught myself saying earlier in the day:
As a human species we need to stop doing stupid shit™.
–James Mills
T-shirt coming soon™
Tired to re-enable the Ege route to git.mills.io today (after finishing work) and this is what I found 🤯 Tehse asshole/cunts are still at it !!! 🤬 – So let’s instead see if this works:
$ host git.mills.io 1.1.1.1
Using domain server:
Name: 1.1.1.1
Address: 1.1.1.1#53
Aliases:
git.mills.io is an alias for fuckoff.mills.io.
fuckoff.mills.io has address 127.0.0.1
PS: Would anyone be interested if I started a massive global class action suit against companies that do this kind of abusive web crawling behavior, violate/disregards robots.txt and whatever else standards that are set in stone by the W3C? 🤔
(#iusym5q) @bender@twtxt.net Maybe so. But running Mastodon or GotoSocial is actually not as easy as you’d think 😂
(#h3pxyfq) @movq@www.uninformativ.de If by that you mean ISP(s)? No. so far most are hosting providers by the looks? 🧐
(#iusym5q) @aelaraji@aelaraji.com Ahh that would be awesome!!! I’d also somehow need read access to logs so i can figure shit out on my own 🧐
(#i2ybi2q) @aelaraji@aelaraji.com Haha! 😂 Welcome back 🙌
(#hllrena) @aelaraji@aelaraji.com Tell me more? How does this work?
Oh fuck me! I had basically turned off the route to git.mills.io last night and went ot bed at ~2AM after unsuccessfully trying to control the attacks (bad bots) that were behaving like a DDoS attack. Tried to re-enable the route this monring and *BOOM, they’re back! As-if they never stopped?! what da actual fuq?! Anyone have any clever ideas of what I can do here to allows normal users, like you nice folk and block ths obnoxious traffic?!
Fark me again with the bots. This time DDoS-style crawling from hundreds of IPs and dozens of ASN(s) wtf?!
I’ve had to disale the Ingress to my Git instance for the time being, i need to sleep and I can’t fight this :/
(#j2bl5vq) @bender@twtxt.net Just a donations thiny I knew about from years ago that I never setup properly. Now an acceptable form of donation on my prologic.dev site 👌 (if anyone ever does that is!)
Bye bye PayPal 👋 Hello LibrePay 👋
When I try to login to PayPal I now see:
Please enable JS and disable any ad blocker
Here’s the thing. PayPal takes fees from transactions and payments received and sent.
I have very right not have ads shoved in my face for something that isn’t actually free in the first place and costs money to use. If PayPal would like to continue to piss off folks me like, then I’ll happily close my PayPal account and go somewhere else that doesn’t shove ads in my face and consume 30-40% of my Internet bandwidth on useless garbage/crap.
(#7dtwepq) @shinyoukai@neko.laidback.moe Haha 🤣 Nice typo there!
(#kzoqkdq) @shinyoukai@neko.laidback.moe I’m mostly against it because it forces Javascript™ on the client(s) at a blanket level. Doing “Proof-of-Work” explicitly IMO is fine™, but not at an Ingress/Edge level IMO – Which is why I haven’t adopted it myself.
My day (yesterday), stand up at 09:30AM (AEDT), P2 Incident at 10:20AM. End of my day 04:30AM (AEST) the next day! Oh my 🤣 🔥 🤦♂️
(#ocuiada) @movq@www.uninformativ.de @bender@twtxt.net I’ll also start spamming from my upcoming Vietnam holiday (flying out this Friday) for a couple of soliday weeks 🤣
(#d2pj7pq) @movq@www.uninformativ.de Seems fine to me! Plenty of time to get our shit™ in order! 🙌
(#xyy4hrq) @shinyoukai@neko.laidback.moe Welcome back! 🤟 You have been missed! 😅
(#ykqom5q) @shinyoukai@neko.laidback.moe Welcome back 🤟
(#d2pj7pq) Obviously yarnd 🙋♂️
(#jryh2ba) This is what this looked like visually 😳
(#jryh2ba) At this point I’m considering starting a class action lawsuit for all the self-hostess and little-web folks that want to host a small thing or two and sue these fucking inconsiderate fucking corporate giants, hopefully win, and make them respect others on the web.
Fark me 🤦♂️ I woke up quite late today (after a long night helping/assisting with a Mainframe migration last night fork work) to abusive traffic and my alerts going off. The impact? My pod (twtxt.net) was being hammered by something at a request rate of 30 req/s (there are global rate limits in place, but still…). The culprit? Turned out to be a particular IP 43.134.51.191 and after looking into who own s that IP I discovered it was yet-another-bad-customer-or-whatever from Tencent, so that entire network (ASN) is now blocked from my Edge:
+# Who: Tentcent
+# Why: Bad Bots
+132203
Total damage?
$ caddy-log-formatter twtxt.net.log | cut -f 1 -d ' ' | sort | uniq -c | sort -r -n -k 1 | head -n 5
61371 43.134.51.191
402 159.196.9.199
121 45.77.238.240
8 106.200.1.116
6 104.250.53.138
61k reqs over an hour or so (before I noticed), bunch of CPU time burned, and useless waste of my fucking time.