When you consider “my problem is solved this time” as documentation then a discord discussion can be considered good documentation. But If you want documentation as reference for everyone and don’t wan’t to repeat process/procedures every time some one needs it. It’s the worst platform for it. And For documentation we never want the first.

In this context email lists were the best of the best documentation ever.

Totally unrelated, these second black circles on the people in the background 🤣

I wouldn’t ever imagine to shed a tear for the processes I have killed in my whole life. I feel like a homicidal maniac.

this is not cancellation. This is Google taking a step back, and regroup to attack back.

I suppose it’s “confusing perspective” worthy.

Then I hope it won’t get any traction.

I hope this is a joke and not intended to be real.

I want to see the 10x hamsters!

I never used Chrome. happy user of Firefox since it’s conception.

You can use pencils as supports too

Shots fired! Shots fired!

It is, but If you review 3 lines of pr and not the whole 50 lines of the file without thinking of the overall picture, this happens. I got this while reviewing a pr like this. And most probably I approved similar prs for this file in the past. Shame on me too…

Yep that’s on me:) let’s call this second breakfast!

It’s not the real issue. I introduced that while anonymizing the data. It’s that a 3-5 liner code became a huge switch case by just incrementing the code and never thinking how it should be done. This was caused by like 15 engineers in time :)

Something like below would be huge improvement:

subs1 = ["cluster1", "cluster2"]
if subs1.contains(clusterName) return subs1

And no reason to state this is from production.

no one looks behind and questions how and why.

it was never an array to begin with!

is prowlarr better than jackett? Is it wise to invest some time to migrate?