Quite literally my first thought. Great, but I can’t issue certs against that.

One of the major reasons I have a domain name is so that I can issue certs that just work against any and all devices. For resources on my network. Home or work, some thing.

To folks recommending a private CA, that’s a quick way to some serious frustration. For some arguably good reasons. On some devices I could easily add a CA to, others are annoying or downright bullshit, and yet others are pretty much impossible. Then that last set that’s the most persnickety, guests, where it’d be downright rude!

Being able to issue public certs is easily is great! I don’t use .local much because if it’s worth naming, it’s worth securing.

Oh ffs. 🤯

D’oh. I missed that! 😔

Except Google Pay had the ability to send money to/from friends and bill splitting. Wallet has no such features at all. And nothing they’ve published or any news on it seems to mention this. (Which has left me somewhat confused that I’m missing something. But as best as I can tell, I’m not)

If you look deeper at the recorded PR commit, comments, and package description it’s clearly straight up mean-spirited.

Thank you for the correction and details.

I dunno if you noticed or if that was the joke. But you said “8 megs” three times in your comment when I think you meant to say “8 gigs”. 1 gigabyte ~ 1024 megabytes. Just wanted to let you know in case it wasn’t a joke about how 8 wasn’t enough. That’s all, thank you!

A bot I’m very pleased to see! Very cool.

From my understanding, transcode quality is a concern. I’ve unfortunately read AMD’s implementation just isn’t very good. That one is better off going Intel particularly from the last few years.

Jellyfin’s docs specifically talk about the issue.

Intel’s transcoding is also faster in the same generation.

Been debating which way to go for my next rebuild as I’m over due myself.