xcjs @ xcjs @programming.dev

Posts

0

Comments

100

Joined

2 yr. ago

PNG support lossless compression through deflation, but there are encoders that can apply a lossy filter to the image to make the compression more effective.

PNG doesn't support lossy compression natively, to be clear.

Rust specializes in making parallel processing secure and approachable, so it's going get used in problems where parallel processing and efficiency matter.

Rust is also now allowed to be used in the Linux kernel for the same reasons, which is exciting!

Nice! I didn't realize this was a feature of Joplin!

It's encrypted during transit only (if using HTTPS), though you can look into an encrypted filesystem on the server and the clients you use.

Sounds like a job for Ansible. ;-)

Of course! Here's the documentation for the docker-compose module: https://docs.ansible.com/ansible/latest/collections/community/docker/docker_compose_module.html

It does rely on the recently-made-legacy docker-compose client, so for now it's still required to install that. If you need some advice or pointers, let me know.

That depends on what you mean by container. I use it to orchestrate Docker containers for my infrastructure and then some.

I'd say not because of those things but due to overall socioeconomic well-being.

I was going to recommend Ansible as well - documentation as code can never be out of date if you continue using it.

This is a bit outdated with .NET Core. You can just compile it for a Linux target or install the .NET runtime from Microsoft.

I'm not sure Mono supports all the newer language features.

By some metrics, Firefox surpasses Chrome now.

I think discoverability is still a problem.

I use Discord for real-time communication, but leaving a platform that's closing up access for a platform with already closed access makes no sense to me. It doesn't solve the original problem.

If it does include a VPN provider, then you're correct - it would work for other applications.

I don't think it's common knowledge for people who don't have the app, so you may want to include information about that in your original post.

Just so you're aware why people are disagreeing with you - an installed browser does not change the behavior of HTTP calls made in other applications.

It doesn't quite say that, but I think the meaning is essentially the same: "Don't choose a name after a project unique to that machine." - RFC 1178

For my homelab, I think that's fine to do. I'm unlikely to have multiple Plex servers locally, for example, and if so, numerically naming them is fine - I provision with Ansible, and if I'm at the point where I'm having sequentially numbered hosts, they'll be configured as cattle anyway. Also, having the names reflect the services a host provides makes it easier to match in my playbooks.

I think it's a better scheme than turning to mythology, fiction, or animal species, which oddly enough RFC 1178 does encourage you to do.

I use significant hardware component or model:

• Z390
• AERO15

...or sometimes intended purpose:

• USERV - Ubuntu SERVer
• PlexBox - Plex Server
• NAS - NAS
• Runner - GitLab Runner
• MDEV - Mobile DEVelopment
• MDEV2 - Mobile DEVelopment, Version 2

I also have a Kubernetes cluster that ranges from K8S_0 to K8S_5.

Always has been.

Same story here, and Connect seems to be the furthest along.

I'll probably switch to Sync for Lemmy when it makes it's debut, but Connect is almost a good enough replacement.

I'm still using the old docker-compose executable - my Docker role is still installing it until the Ansible module catches up.

I've done something similar, but I'm using compose files orchestrated by Ansible instead.