lemmyng

Has your instance blocked hexbear? Because they do this a lot.

Or the classics of symphonic metal like Stratovarius.

Opposite for me - I do so many things that I don’t strongly identify with any single one. Get a tattoo?? Nah, I’ll probably be bored of the subject in a few months!

Since FF 6 and 7 have already been mentioned, I’m going to give a honorable mention to Shining Force.

SVG is probably a better fit for this use case.

Absolutely… when available. But many companies/teams do not release SVG artwork. PNG material is much more commonly available, and actually works with these tools.

WebP supports both lossy and lossless compression.

WebP did not always support lossless compression. It’s conceivable that the tools’ developers made the decision before that.

Images on the web usually aren’t large enough for this to make a significant difference, and it can sometimes be offset by the quicker download time.

That does not fit the use case of diagramming tools. They usually have comparatively few assets that are used multiple times in the same document. The larger the document, the more benefit lower CPU cost has. And I’ve seen LARGE diagrams.

libjpeg and libpng have had a number of CVEs too though.

Fair. I’m just speculating that it might be a contributing factor for the tools still not supporting the format.

Maybe because in those scenarios PNG offers sharper images, which is more important than compression when you have complex diagrams. Or because webp is more CPU intensive, and PNG gives better performance when rendering. Or because of CVE-2023-4863.

Good luck using webp in any kind of collaborative diagramming software.

Meanwhile…

If it was a Futurama setting, would he be Gender Bender?

Structure like a skeleton. Gives you the rough shape, but you have some freedom to arrange the squishy bits hanging off it.

rapid mitosis

As in you are seeing multiple boot entries? It’s likely one entry per kernel version that you have installed. It doesn’t happen often these days any more, but in some situations it’s handy to be able to revert to a previous kernel if for example third party modules break.

Not sure about erasing all of it, but it is (or was) certainly possible to delete enough of it to brick a motherboard https://www.phoronix.com/news/UEFI-rm-root-directory

I don’t know where you got the idea that I’m arguing that old versions don’t get new vulnerabilities. I’m saying that just because a CVE exists it does not necessarily make a system immediately vulnerable, because many CVEs rely on theoretical scenarios or specific attack vectors that are not exploitable in a hardened system or that have limited impact.

The fact that you think it’s not possible means that you’re not familiar with CVSS scores, which every CVE includes and which are widely used in regulated fields.

And if you think that always updating to the latest version keeps you safe then you’ve forgotten about the recent xz backdoor.

Just because it has a CVE number doesn’t mean it’s exploitable. Of the 800 CVEs, which ones are in the KEV catalogue? What are the attack vectors? What mitigations are available?

Haven’t used it myself, but every person I know that tried Pulumi ended up going back to Terraform. From what I’m given to understand it is fine for small projects, but runs into problems at scale.

Personally I don’t like the default SaaS/account required model in Pulumi. I have lots of things to dislike about Terraform, but that isn’t one.

Mind you too with either tool you (or your devs) will still deal with Dockerfiles and Kubernetes manifests, you just would use Pulumi or Terraform or whatever to manage them.

Lastly: I have done the jump from Ansible to Terraform myself. If you have a large amount of machines to manage and want to minimize transition pains then don’t just use vanilla Terraform, but instead go for a platform like env0 or Spacelift, or at least use Terragrunt to manage your plans.

You did a recursive chown or chmod, didn’t you.

Here’s a third one: They have a Welcome Stamp visa program where you can work remotely from there for a year, and it’s renewable. You can even bring your family. Under this program you only pay income tax on your country of origin.

Bazzite, as a gaming-first distribution, makes some choices that are acceptable for such a platform, but that I believe are unacceptable in a secure development environment. This is why I wrote “not ideal” instead of “bad”. If you don’t care about security then it’s perfectly cromulent. But I value security, so I would not recommend it.