

Winget would have been a better one here
Winget would have been a better one here
It’s probaly Lua
I would probably find a way to move to files to a better file system than ntfs for use in jellyfin
Even without WSL it’s basically the same portion of people using windows and using linux for personal use.
Arc is a neat browser I might try out if it weren’t Mac only and chromium based.
I think Tabby is a similar project, but personally I spin up and throw out terminals very liberally. Tabby had a horrendous launch time, something more than a second which constantly bothered me while trying to work. I’d love to see how quick this is though!
I don’t imagine express is wireguard under the hood but that’s a pretty common wireguard configuration method.
I tried to use kitty but I have to ssh in to remote machines often for work, usually one of a few hundred edge devices, and I can’t configure them all to work properly with it. Is solid ssh support just not a deal breaker for others?
Finishing the manga made me not want to finish the anime at all. The release schedule put the final nail in the coffin.
works with vim but never tested on vi
But that’s a choice made by Garry Newman, not a limitation of the platform
Hopefully the coming lemmy update will alleviate that a bit, users being able to block instances will be good.
You can just make a usb stick a boot drive with a linux install, it wont’ be performant but it would work.
Sounds like it’s not the game for you. Overcoming environmental challenges is kind of the name of the game, and if the baseline “cold bad but fire hot” thing isn’t something you enjoy then I’m not sure you would enjoy trying to navigate any of the main story areas in the game.
So I personally use two computers on a daily basis, a personal desktop I use all day long, and a laptop I use during work hours. Both are running Linux with pipewire and the pipewire-pulseaudio extension. I do my best to keep everything work related on the work device and everything personal on the personal device, so discord chats with friends stay on the personal machine etc. I occasionally need to participate in work meetings and the like, so I would like my audio interface to be shared between the two devices. Turns out this is exceptionally simple.
On my “host” machine with the audio interface I always use I have a pipewire config file at /etc/pipewire/pipewire-pulse.conf.d/50-network-party.conf
that contains
context.exec = [
{ path = "pactl" args = "load-module module-native-protocol-tcp listen=0.0.0.0" }
{ path = "pactl" args = "load-module module-zeroconf-discover" }
{ path = "pactl" args = "load-module module-zeroconf-publish" }
]
And on my work laptop I similarly just load the module-zeroconf-publish module. Once that’s done all of my desktop’s audio devices show up on the work laptop and I can set them as my defaults, and everything just works! Didn’t even require installing any extra software or anything, both systems worked out of the box when I learned about this module.
As for using my desktop’s audio devices for my phone, turns out pulseaudio also supports connecting android devices using a2dp and simply pairing my phone and computer had my phone streaming its audio to my desktop and using its microphone for calls. Honestly wish I’d looked in to this sooner, having everything going through my desktop’s audio setup is so nice.
Pulseaudio’s networked audio devices are sick, and similarly getting your computer’s headphones/mic on your phone by just connecting your phone to your computer over bluetooth is fantastic.
deleted by creator
Was wondering why this didn’t work, thanks!
I wasn’t able to figure out how to run it on any lemmy instance