Goldkin @Goldkin@awoo.space

@qdot @Kyreeth Thankfully, there's a mod that fixes this for other entries in the series, and will presumably be ported to this one as well:
https://www.reddit.com/r/furry_irl/comments/rl4rze/yakuza_irl/
https://m.youtube.com/watch?v=LZCFGdW9lcI

@qdot This made me wonder what Hamlet (Wagner James Au) was getting up to these days, and man, he's still going: https://nwn.blogs.com/nwn/

@Leviamicky Yeah, I'd assume they tried to do so here and either didn't find it or discovered that fiber doesn't scan like power lines do?

It's also probably not the work crew's fault, nor most of Comcast's. Specs and city plans can be inaccurate, underground lines can drift over time, and it's hard to get an accurate reading below concrete without, well, digging. I'm assuming they used their best judgment on this and only knew it was a problem after they struck the line.

Comcast probably had to haggle with the city to run a single line. Typically there's redundancy in these systems, so the fact there wasn't here is... a thing.

At 9PM yesterday, we lost home internet along with much of the greater Seattle area. Still out (I'm tethering over wireless). We figured it was probably a fiber cut, but not a whole lot of information was circulating about it.

Today we learned: at least three cities were disrupted by a single box in the middle of Renton:

https://washington.comcast.com/2023/01/18/service-outage-in-the-burien-kent-and-renton-areas/

Who would win: Comcast service for all of Seattle vs one shiny diggie boy.

Some reputable security researchers and SREs on birdsite are sharing that Hive has already had a major security breach and responded to private disclosure with public whataboutism instead of immediately patching:

* https://twitter.com/dynamicsymmetry/status/1598330367374680064

Direct article link: https://zerforschung.org/posts/hive-en/

Avoid, avoid avoid avoid with anything resembling sensitive data. This is about as big a red flag as they come.

@erincandescent@queer.af @Dex Yuuuuup