Yea, after another hour today I’ve decided that my time is better spent elsewhere, so I’m just going to stick with Navidrome and not worry too much about losing out on the federated music idea for now.

I gave up on funk whale about 6 months ago and was loving navidrome, but hadn’t realised the lack of library separation. Thankfully that doesn’t bother me too much. I’ll give this another go and see how I get on though if I can find some time over the weekend

I’ve got my instance of matrix working with voice calls. It’s not built in, but it’s just another service in my compose file alongside the bridges I use to have my unified chat app.

I’m using coturn and it just works when doing voice and video calls with federated users.

I think I’ve seen people using jitsi as well, so it seems there are many options available

I know it doesn’t help you at the moment, but at some point between June last year and last week they’ve updated the kickstand to include an extra little crossbar up at the top of the metal u shaped piece of metal that makes up the stand so that you need to lose both pins for it to fall off now. (I ordered one last year and ordered a replacement kit for a 2nd steam deck that I’ve gifted to my wife) And I’m liking the look of the new design.

I’ll see if I can take a photo later on and share it to explain as I suspect my words aren’t doing a great job.

Edit: here’s a quick photo I’ve taken to try to show the new crossbar thing in action.

I considered trying that then read about some kernel versions not being compatible with certain versions of the dkms package so decided to give up, go to bed and deal with the issue later. (This was Saturday night and sadly time hasn’t permitted me to start investigating again yet)

I have the same issue on my desktop. I’d assumed it was something I’d done (it usually is) but I had to admit defeat and resort to switching to booting into a backup OS so that I could get on with all the tasks I need to get done but I’m assuming it was a problem with the Nvidia-dkms package that’ll be resolved in time as people have reported similar issues in the past.

Ah, thanks for correcting me there. I knew that EA were involved at some level and I didn’t think to research that part of the post I was replying to, so I stand corrected, but I think the main point I was making is still valid, that the team that initially developed the game weren’t behind this re-release.

The original was EA, this re-release is Aspyr, so as bad as EA are I’m not convinced that they’re to blame here.

Oh, I’m fine with my setup, I have a couple of external servers that can monitor all my web accessible stuff with kuma and then I’ve got another local one to monitor my non-web accessible stuff.

Thanks for those tips though, definitely useful to consider other options

On the uptime monitoring I’ve been quite happy with uptime kuma, but… If you put it on the same host that’s down… Well, that’s not going to work :p (I nearly made that mistake)

Haha, that’s fair. I was being sincere.

I’d initially scrolled past thinking “I played this whilst I was still at Uni, why is anyone talking about it now?”

Now that I know this person’s focus is intentionally looking at older games I’m willing to go and give it a watch.

Thanks for that additional insight into this channel. This completely changes the way that I will now look at this content.

If the extra charger that covers with the official dock doesn’t work to you (fair enough since you mention that portability is key) I backed the jsaux case on Kickstarter and am quite happy with us: https://jsaux.com/products/omnicase-2-storage-docking-station?variant=43986713772252

I got the pro version, but there’s no reason that you can’t get the standard one and it came with a nice little travel pouch, but I don’t know if that covers with the ices you buy directly.

That sounds like a rather unpleasant experience indeed! I’ve never looked into it in more detail than scrolling through the lsio containers they offer, so thanks for that insight and saving me a headache in case I get around to a similar project I’ve also been meaning to embark upon

Could Snipe it work for you? https://docs.linuxserver.io/images/docker-snipe-it/

It looks like an asset management tool. The description copied and pasted from above reads:Snipe-it makes asset management easy. It was built by people solving real-world IT and asset management problems, and a solid UX has always been a top priority. Straightforward design and bulk actions mean getting things done faster

One time I ran out of disk space due to it having created since 200gb log files (not sure why that happened) then another time I think I broke something whilst moving from I’ve got to another. I can’t remember what else happened to break my instances but it was always big enough there I couldn’t restore it to working it after hours if work, so if just export the vaults from everyone’s machine, nuke it, start again and try to learn how I broke it so I didn’t do it again.

I believe I was the problem for most of them except the massive log files one, but still, it was probably my fault as the things usually are. (Guess whose wife has them well trained at accepting the blame 😋)

I pay my $10 license and a personal organisation license for bitwarden because I like their platform but after yet another irrecoverable loss of data (partly my fault for not sufficiently backing it up) I’ve moved over to vaultwarden for my family’s password management.

I don’t think I’ll stop supporting bitwarden even if I’m not using their platform directly though as I do like the service I’ve had from them for something like 4 or 5 years now.

I was going to say that the big downside to that would be a lack of any kind of version control, but I guess if you need that you can always use git and just commit changes there and (optionally) push them to a repository somewhere.

I chose to take down my production instance of lemmyz do a cp -r of it, update the docker compose file to specify the new version numbers for Lemmy and lemmy-ui plus change the port that the stack exposes and do a docker-compose pull && docker-compose up -d on that stack to check to see if it could all work. Thankfully it did, so I updated the production compose file and tada! I’m on 19.0 safely

Ooo, I’ll add that to one of my planka boards for “things to look at later” thanks for sharing