Keeping track of what's going on in the world these days is almost impossible. So I put together this simplified static timeline site.
Help me make this a jumping off point and a template we can re-use for other high-profile events. It shouldn't be anything fancy, just a timeline of critical related events and (ideally) multiple sources.
The choice of what to include is editorial, and you already have to be neck-deep in the Fox News alternate universe to believe that Feeding our Future was a fraud worth mentioning on a national scale.
Wow, someone with something to lose finally spoke up / out against the Trump administration! :clap:
While (unfortunately) rather heroic in todays day and age, I fear the retribution he's now called upon himself, Germany, and the EU in particular. Vance and Stephen Miller are already always whispering in Trump's ear about the evils of Europe / the EU, convincing him to take action on whatever they want won't be hard.
Sidebar: the fact that we have to be fearful of retribution due to such rhetoric is really all that needs to be said about the timeline we're currently living through.
Pebble are releasing a new slew of products and their arguments with rebble aside, are seemingly doing a good job so far prepping SDKs and more to easily write software for the new watches. Including leveraging the banglejs engine mentioned earlier in this thread to enable folks to write apps / watchfaces in javascript!
This is just not true anymore. The only things that don't work anymore are a few AAA titles that use particular types of anti-cheat systems that rely on Windows kernel drivers (League of Legends is one that comes to mind).
If I remember correctly, after the Crowdstrike BSOD-all-windows-instances update last year Microsoft wanted to make some changes to their kernel driver program and these anti-cheat measures on Windows might need to find a new mechanism soon anyway. That's a long way of saying, it's plausible that even that last barrier might come down sooner rather than later.
As a beginner, just pick Ubuntu and get on with your life imo. Switching distros isn't that big of a lift later on and pretty much everything you learn carries over from one to the other. It's much more worthwhile to just pick _something_ and learn some basics and become comfortable with the OS imo.
So on the surface it seems that we already had many of these types of orgs, but they killed them all and spun up their own renamed and rebadged versions.
That being said, this project does seem like a potential big win.
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.
I'll believe it when I see it wishing them the best!
> To streamline development and shorten time-to-market, VSORA embraces industry standards: our toolchain is built on LLVM and supports common frameworks like ONNX and PyTorch, minimizing integration effort and customer cost.
Help me make this a jumping off point and a template we can re-use for other high-profile events. It shouldn't be anything fancy, just a timeline of critical related events and (ideally) multiple sources.