Mastodon 🐘

0 posts0 participants0 posts today

AlexI'm going to stop re-tooting about the <a href="https://mastodon.org.uk/tags/xz" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#xz</a> <a href="https://mastodon.org.uk/tags/backdoor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#backdoor</a> 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 <a href="https://mastodon.org.uk/tags/upstreams" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#upstreams</a> can take to tighten up their processes.Interesting sidenote: I had to actively go looking on <a href="https://mastodon.org.uk/tags/twitter" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#twitter</a> to find any reporting on this. I got everything I needed to know from <a href="https://mastodon.org.uk/tags/mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mastodon</a> and <a href="https://mastodon.org.uk/tags/lemmy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lemmy</a>.

David RungeSome <a href="https://chaos.social/tags/corporate" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#corporate</a> <a href="https://chaos.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> <a href="https://chaos.social/tags/python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#python</a> <a href="https://chaos.social/tags/upstreams" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#upstreams</a> are more cursed than others.We experience packager drain on <a href="https://chaos.social/tags/molecule" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#molecule</a> and <a href="https://chaos.social/tags/ansible" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ansible</a> 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...<a href="https://chaos.social/tags/ArchLinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ArchLinux</a> <a href="https://chaos.social/tags/packagerlife" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#packagerlife</a>

Kevin Karhan :verified:<a href="https://social.afront.org/@kwf" class="u-url mention">@kwf</a> that reminds me of news stories that <a href="https://mstdn.social/tags/DTAG" class="mention hashtag" rel="tag">#DTAG</a> abusing <a href="https://mstdn.social/tags/Cogent" class="mention hashtag" rel="tag">#Cogent</a> & <a href="https://mstdn.social/tags/Level3" class="mention hashtag" rel="tag">#Level3</a> as <a href="https://mstdn.social/tags/Upstreams" class="mention hashtag" rel="tag">#Upstreams</a> and refusing to upgrade the bandwiths, causing <a href="https://mstdn.social/tags/PacketLoss" class="mention hashtag" rel="tag">#PacketLoss</a> and instable connectivity out of their <a href="https://mstdn.social/tags/ego" class="mention hashtag" rel="tag">#ego</a> not wanting to peer at <a href="https://mstdn.social/tags/DECIX" class="mention hashtag" rel="tag">#DECIX</a> 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.

Recent searches

Search options

Administered by:

Server stats:

#Upstreams