Recently switched from VsCodium to neovim - but still use Codium for some specific tasks.

My setup customization focuses around Telescope, Treesitter, Trouble & Blink.

But the advice I got was to start with vim keybindings in VSCode. I used those for six weeks until I got the hang of the basics and it had gone from frustrating to somewhat second nature.

Then I made the move.

I still use Codium for Terraform work (I have struggled to get the Terraform LS working well in neovim and I don’t use it often enough to warrant the effort) and as a GUI git client - I like the ability to add a single line from multiple files and I haven’t looked up how to do it any other way - I’ve got other stuff to do and it’s not slowing me down.

But I grew to hate Codium / VS code tabs in larger codebases. I was spending so much time looking for open tabs ( I realise this is a me problem). While neovim has tabs, it’s much more controlled and I typically use them very differently and very sparingly.

If I need to look up a data structure I just call it up temporarily with Telescope via a find files call or a live grep call (both setup to only use my project directory by default), take a peak, and move on.

The thing is - security risks are going to exist anywhere you install plugins you haven’t audited the code for. Unless you work in an IDE where there’s a company guaranteeing all plugins - there are always going to be risks.

I’d argue that VSCode, while a bigger target, has both a large user base and Microsoft’s security team going for it. I don’t see the theme being compromised as much as problem because it got solved and also prompted some serious security review of many marketplace plugins. Not ideal, but not terrible.

Mother would be proud.

Agreed.

For us the mitigation is to do a little monitoring with alerts set to start casually at 29 days out and enter critical 13 days out (out from expiry).

Awesome. Thanks.

I hope I’m wrong but it looks like they disabled the ability to do opt into the program.

I cannot join my X1C to the program currently. It just errors out or leaves me in a CloudFlare “are you human” loop.

Up until this change you could install and root the firmware with Bambu’s permission.

One idea that crossed my mind is that the open(ish) firmware started to edge into future product territory.

Bambu’s pages for third party firmware are still up but seem to no longer work: (I tried today) https://bambulab.com/en-us/third-party-firmware/plan?ref=blog.bambulab.com

Canada too.

Email is notoriously hard to self host. It requires constant care, planning, and interfacing with the big guys when your email can’t get delivered despite jumping through all the hoops (DKIM, DMARC, SPF and more).

I used to run email services for my small business and former start-up. It was a never-ending pain. IP warming, monitoring, deliverability checks…. blah blah blah.

Both Google and Microsoft would regularly blacklist massive IP address blocks because of one bad IP address. Days to weeks for resolution in some cases.

I’m a little salty though ‘cause I just switched to proton away from RackSpace. There are so few good and reliable options that aren’t the big guys and the big guys want it that way.

I’ve had good luck with Garuda after nearly two decades on Ubuntu and its derivatives.

So much so that I moved my work os to it, despite the gaming bent.