@marcel @cryptoparty @zalintyre ja, und juristisch wäre das was was ich nicht ohne fachanwaltliche Rücksprache versuchen würde.
Ich bin ja eher für automatisiertes Reporting:
Und in der Zwischenzeit werden die Hoster automatisch blocklisted!
@f2k1de @Lili keine Ahnung, aber soweit ich weiß machen die massives #TrafficShaping und #QoS weil #Telekom hat halt so schlechtes #Peering dass deren de-facto #Upstreams (#Cogent & #Level3) die verklagt hatten.
I'm going to stop re-tooting about the #xz #backdoor as I'm pretty sure everyone is aware now. I'm sure there will be further analysis and recommendations in the following days and hopefully concrete action other #upstreams can take to tighten up their processes.
Interesting sidenote: I had to actively go looking on #twitter to find any reporting on this. I got everything I needed to know from #mastodon and #lemmy.
Some #corporate #opensource #python #upstreams are more cursed than others.
We experience packager drain on #molecule and #ansible related packages, as upstream knowingly breaks compatibility from time to time and doesn't guard or test against it properly. Instead afterwards suggests to "just pin it" 🤡 (which does not work after the fact in system packaging).
Soon they will have their wish fulfilled when no one wants to touch that stuff for packaging anymore...
@kwf that reminds me of news stories that #DTAG abusing #Cogent & #Level3 as #Upstreams and refusing to upgrade the bandwiths, causing #PacketLoss and instable connectivity out of their #ego not wanting to peer at #DECIX and have properly sized ports.
This even went into lawsuit filings, but propably got pulled due to arbitration.
After all, I remember colleagues saying one should not exceed 30-50% of the network capacity prior to upgrading just to have enough breathing room.
Kevin Karhan 
Alex
David Runge
Kevin Karhan 