@briankrebs

what the IRS audit folks recovered in the current administration is exactly why TFG's handleers all want the IRS audits gutted yet again. you can be sure they all remember the lesson of how they finally got al capone.

@atax1a @austinkocher

and the old screw rule "righty tighty lefty loosey" morphs accurately "righty tighty, lefty loses"...

@TheGibson

i also worry that we already have enough companies cutting security staff/resources and not listening to proactive warnings. using AI to generate such warnings gives them yet another excuse to ignore them.

@Viss

i was a very early employee at one of the first two commercial US ISPs, UUNET.

all of us were using cisco routers. there was a bug where at about 24-26 hours, the BGP session in them crashed, causing waves of BGP convergence issues, affecting all the tier 1 providers.

the solution was to reboot carefully at about 22 hours. we waited desperately for cisco to get us a patch.

we were at a usenix conference in the terminal room at about 11pm when we got an email that they'd isolated the bug and thought they had a fix. at this point, the senior router folks for UUNET, MCI, and Sprint sat in the terminal room, waiting.

about 1:30am we got email that tony thought he'd fix it. we asked how much testing he'd been able to do.

tony: "it booted in the lab"

us: "we'll take it!"

then, all 6 of us downloaded the code and proceeded to reboot about 70% of the internet backbone to start using the new code, all of UUNET, MCI, & Sprint.

fortunately, in those days, cisco let their senior engineers talk directly to customers and they got things fixed fast.

this never made the newspapers at the time. i can't even imagine any ISP these days allowing engineers to reboot their entire backbone from a terminal room with code that "booted in the lab".

kind of miss those old days.

@ryanc

lack of revision numbers on change in general is just evil.

i remember buying a couple of hundred boxes with a very specific controller board that we had to have due to OS support. first batch worked fine. second shipment, every one failed. checked board revision versions. no change.

turns out they did new board firmware but didn't increment version number.

hilarity ensues.

sigh...

@bortzmeyer

"the cobbler's children have no shoes"

glad this is getting reviewed.

@jmsdnns @mekkaokereke

promises to minorities are like a FIFO stack in programming. when the election is tight and they need support, politicians will make public pledges to minorities first.

once they win, those promises are the first ones removed from the stack.

we all need to be better at holding politicians accountable for actually following through on campaign promises.

@goetz @googlepixel

ipv4 supported printing, so obviously it's broken and inferior and ipv6 shouldn't support it... ;(

and yes, i can name folks at google who have this kind of attitude...

@darkuncle

i think we need a new term. legacy has positive connotations, tradition, etc.

i propose we start describing things as "albatross services".

@dentangle @julian

amazon: "let's see how many different ways we can soak customers for revenue before they object..."