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? 🤔

@eldersnake This was an interesting read for sure! 👍 I don't think it had anything I hadn't already considered in terms of the ethical/moral points of view. I'm not sure where I stand myself either to be honest. I've forced myself to get familiar with the ecosystem and tooling, because in my line of work as a tech lead (staff engineer in sre) you don't want to be that one guy that ya know 😉 Ethically/Morally though, I'm definitely with the sentiment of this post 😅 Much like the whole Crypto hype yaers back (if y'all remember?!) this is also one of the most energy hungry pieces of "tech" (if you can call it that?) in a while. Then there's these other issues "stealing people's work", "reliance is causing humans to become cognitively weak and neural connections to shrink", to name a few...

One of the nicest things about Go is the language itself, comparing Go to other popular languages in terms of the complexity to learn to be proficient in:

• Go: 25 keywords (Stack Overflow); CSP-style concurrency (goroutines & channels)
• Python 2: 30 keywords (TutorialsPoint); GIL-bound threads & multiprocessing (Wikipedia)
• Python 3: 35 keywords (Initial Commit); GIL-bound threads, asyncio & multiprocessing (Wikipedia, DEV Community)
• Java: 50 keywords (Stack Overflow); threads + java.util.concurrent (Wikipedia)
• C++: 82 keywords (Stack Overflow); std::thread, atomics & futures (en.cppreference.com)
• JavaScript: 38 keywords (Stack Overflow); single-threaded event loop & async/await, Web Workers (Wikipedia)
• Ruby: 42 keywords (Stack Overflow); GIL-bound threads (MRI), fibers & processes (Wikipedia)

Move beyond basic threshold alerts! Define clear Service Level Objectives (SLOs) and measure Service Level Indicators (SLIs) to track real user impact. Use Prometheus to alert when your SLOs are at risk, ensuring you focus on what truly matters to your users. #Monitoring #SRE #Prometheus

@bender Bahahah 🤣😂 mate, me and one of my SRE colleagues actually came up with the terminology ourselves! 😛

@bender Ahh okay, I must have misread the website 🤔

This is an example of what I believe every SRE should master and whatever Post Incident Review (PIR) should focus on. Where did the system fail. What are the missing or incomplete Safety Controls.