I wish I knew hardware better but I'm coming to the idea that an xTB nvme and ~25gb/s PoE pcie card in my gaming PC would be a sic always on device. Lots of server roles really just need a tiny IoT device but storage/backup/media you're talking NAS and I just don't want a big NAS around all the time.
So an always on network storage in my PC that's sometimes-on. Between NVME-of and pcie that should be doable I would have though. PoE from my router that's got a tiny UPS and that's pretty sick.
Maybe Valve should make it so everyone with a gaming pc it's re-downloading their steam library or running 2 computers just to open a file.
I've always had stuff like this turned down by Netbox, they argue they want to model the logical topology as a source to trust, not the physicality, but then they model rack U placement. I'm always puzzled by their stance.
Like you can't model 1 cat5 split into two 100mb terminations, patch panels are kinda of hack, I think you can now but forever you couldn't just swap a termination direction because logically why would you (but their UI gets messy when 44 are done A-B and the 45th B-A)
Anyway that's thoughts as of maybe v2 or 3? Before the new UI when it was all jquery.
Netbox project used to go on and on about the philosophical justifications for not including n-type connections or different types of LMR. But the most recent release notes that I read had a blurb about all the new coax cable types they are supporting. I understand having limited time but instead of saying "no" they always had to make lofty philosophical arguments. It's weird.
One of the achievements in my career I’m lowkey proudest of is sneaking in the rewire of about 45,000 ports on a campus that were split pair after an explicit project to do so was shot down.
Of course, but a splitter in a PON network or a WDM device are perhaps better examples of things that are hacky to model. Multi-fibre cables and splices are another. Netbox is great for some simple applications, and it's fantastic OSS, but in practice falls short for many use cases.
Yeh it's awful, but all of our CCTV was wired like this through patch panels with 24v/48v power injectors. 2 cameras a cable. So that's what I needed to document, because in reality I can't book scaffolding and change rooftop cameras for a documentation tool.
Oh I wasn't aware of this actually being an intended usecase. And yes like the other poster said, pairing it with a phone infrastructure was more common (in the days before these went all IP of course).
It was a bit of my OCD being triggered as well. I love neat cabling at work (at home it is chaos funnily enough).
Netbox is full of these kinds of things. Where people ask for stuff or even create PRs for it and the Maintainer of Netbox shoots it down because reason.
Wow, that second one was just straight up mean spirited. Doesn't feel like the responder even read it, given the comment about needing a discussion at the end despite it being linked. Not even mentioning the frankly unrealistic expectations of quality is annoying when the contribution guide didn't have those kinds of insane requirements then and still doesn't now.
Reminds me a lot of Grafast too, a new stab at this the people that made postgraphile had. I liked using graphile, haven't needed to rewrite or start a new project yet for grafast. * https://grafast.org/
Then even in the worst case scenario, they were addressing this issue two days after it was publicly disclosed. So this wasn't a "rush to fix the zero day ASAP" scenario, which makes it harder to justify ignoring errors that started occuring in a small scale rollout.
Cloudflare did have early access, and had mitigation in place from the start. The changes that were being rolled out were in response to ongoing attempts to bypass those.
Disclosure: I work at Cloudflare, but not on the WAF
These aren't good because for 0-lists you have an empty parent containers so often you have a wrapping if outside all of that. More generally, template logic indent doubles up inside the indent levels of the template markup and I just find it ugly.
I like vue a lot more;
<ul v-if={users}>
<li v-for={some in users}>{some.name}
</ul>
In my completely uninformed opinion I think China is taking their toys and going home.
The UK gov stepped in to stop a Chinese firm closing our steel mill. Capitalism wasn't made to handle large strategic foreign investments closing their own company at nationally inopportune moments.
It feels like a slow burn of embrace, extend, extinguish but playing out on global critical technology and industry.
It's what my steamdeck is formatted to so I could plop the drive into windows and rip steamapps across to shortcut a lot of downloading.
reply