envyac
Joined 7 years ago
Karma
8
Submissions
8
Member since
Nov 14
Recent submissions
Comment · 2 years ago
Curious what this will mean for ZWave (908.42 MHz in USA & Canda) and other electronics that still operate in this band?
Comment · 3 years ago
Curious why you didn't stack them like...
1. 24p Patch Panel (Odd ports of switch) 2. 48p Switch 3. 24p Patch Panel (Even ports of switch) 4. 1u Cable Mgmt
Then you could have bought 4-6" Cat 5e/6a pre-made patch cables to connect in the majority of your patch panel ports. The only cables that would traverse through the cable mgmt panel would be longer cables to the servers in your rack.
I have a similar Cisco switch as your 24 port. I am not fan of how they arranged all the ports at the right side of the enclosure. Why not make the 24p one row along the top (or bottom), like the 48p with the 2nd row removed? It would be a lot easier for cable mgmt.
Comment · 3 years ago
You mean besides the last three years of reduced on-site staffing, and employee travel to support maintenance and modernization? No.
$5 says this is the XKCD for this. Corrupted DB file was the culprit, as announced by the FAA. It's a system that relies on user inputs, often manual, and it's all being put into a database. My bet is a user decided to put in a bunch of "fun characters" to make their input easier to read. You can't account for and sanitize all levels of stupidity on user inputs.
Comment · 5 years ago
Agreed. Use JSON, proprietary binary formats are terrible, and 99% of the time the bandwidth savings aren't worth it. For messaging, I really like NATS (incubating in the K8S landscape - probably graduating soon). My fav thing is the wildcard usage in NATS.
Comment · 7 years ago
This could have some implications in the computational expense of trilateration for GNSS applications. "Optimal trilateration is an eigenvalue problem" <title of another paper>.
Comment · 7 years ago
This could have some implications in the computational expense of trilateration for GNSS?