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.

It’s to prevent the person from completing a circuit across their chest if accidentally touching a ground or the like with their other arm. Hearts don’t like that.

Just a way to reduce risk when working with electricity.

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)

But however will it determine the player one controller … on a desktop computer?

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.

I have two words for you, “compensating controls.”

It’s like goddamn magic.

Respectfully, please do not do this. Helium is a non-renewable resource. Once lost to the atmosphere it’s gone for good. Nitrogen on the other hand makes up 78% of the atmosphere and is equally effective.

My issue with FF’s auto update is that the behavior is how painfully the auto-update works with multiple profiles.

I’ll have one window (well three) open for some (measurable in days) time.

1. FF updates silently, I haven’t restarted my browser so I haven’t noticed.
2. I go to open a session in the second (or third profiles)
3. FF decides now is a great time to apply the update, after all it just opened right?
4. All the existing open browsing sessions in the other profiles get bricked. The tabs just stop responding, no browsing works, just dead in the water.

I have to shut it (all?) down to get it working again.

I don’t know how Chrome handles this so I cannot compare. TBH still worth using FF over that adware!

Virtualization in general? Sure, I can. I’ve tried it a bit with bhyve. But it’s definitely a lot heavier since I’m now running a full Linux os and dedicating resources to it to run docker just to run a python or node app.

Learning the project is in Go though is a sigh of relief. Professionally I’ve moved to Go (from Python) just because it’s so damn easy to build and distribute.

I just wish there was better support for the other *nix’s. While the language support them just fine, docker on the other hand strangles it. =(

For me it’s more like new interesting self hosted project and then find out it’s only distributed as a docker container without any proper packaging. As someone who runs FreeBSD, this is a frustration I’ve run into with quite a number of projects.

For sure! I was just thinking of a species that’ll outlive humanity. :D

I thought roach myself.

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.

Yeeap. My FreeBSD box has such pain with 'em. Because unfortunately *bsd is not in Python’s precompiled wheels. So one is almost building from the source.

Now every time I pip install something there’s a high likelihood I’m going to end up having to install the rust tool chain and burn so much time on building libraries. I get why the project made the switch, but man does it hurt being downstream of it.

Every time I see a project decide to use rust I groan knowing my build/packaging time is about to skyrocket. Case in point, the Python cryptography project.

And given cryptography’s importance in the Python ecosystem what used to be an easy pip install of a package now almost always going to include is an enormous and horribly slow rust build environment.

Seeing a rust libraryjust makes me sad now 😭