nuintari's rules of networking 0x2c:
Never scrounge a cable out of the trash. It's in there for a reason.
1st Corollary:
Always cut any cable you're throwing in the trash to prevent breaches of the aforementioned rule.
2nd Corollary:
If you replace ends on a trashed cable without also running it through a tester, you deserve any and all of the pain coming to you.
3rd Corollary:
The end connectors are not the only place cables break.
Mom: I think I need a new phone.
Me: Okay, I ordered you a new one, it'll be here in two days.
Mom: my phone is dead, this is me from your sister's phone, please call me as soon as my new phone arrives.
Mom five minutes later: my phone is dead, this is me from your sister's phone, please call me as soon as my new phone arrives.
Mom fifteen minutes later: my phone is dead, this is me from your sister's phone, please call me as soon as my new phone arrives.
Shit like this is why I hate dealing with end user issues.
nuintari's rules of networking 0x4a:
Whenever possible, use bi-directional (BiDi) optics. Fiber connections are a finite resource that often require manual labor and a fusion splicer to add. Less fiber used means less fiber spent. It is also half as much fiber to break.
So, shortly after the nuclear bombing of Hiroshima, the USSR declared war on The Empire of Japan, and began invading Japanese held territories.
Shortly after this and the bombing of Nagasaki, The Japanese surrendered unconditionally to the allies. Ending World War Two.
But the USSR never signed any kind of peace treaty with Japan.
Does this mean that legally speaking, WW2 did not end until the Soviet Union collapsed in 1991? Or that it never has, and that the Russian Federation, the successor state to the USSR, inherited the state of war with Japan?
nuintari's rules of networking 0x4d:
Your network naming convention should be specific enough to inform the operator what facility a device is located within, and what said device's role is on the network. It should be generic enough that neither moving the device to a different rack nor replacing the hardware with a different model will require a name change.
Breathe
Identify the problem
Tea break
Consider your options
Handle it
B.I.T.C.H.
I love it!
A word on how the bot works.
Bot is probably not the best term for it, because it is so dirt simple. It is literally just fortune piped to a perl script called cat4stuff which is executed via cron. It used to be called cat4mastodon, but I have since merged another script called cat4mm (as in MatterMost) into the same codebase. So it can be used to pipe command outputs to multiple destinations on multiple platform types now.
The Roman date bot works in a similar way, but instead of fortune, I execute a perl script called kalends that uses Date::Roman, and corrects a spelling error along the way. It also is piped to cat4stuff.
And before anyone asks, yes, the year is correct. It is the years since the founding of the city of Rome, which has nothing to do with the birth of a certain deity associated with the common era.