Matrix is the closest replacement, and XMPP can replicate some functionality too.

A while back I put together a pretty big list of free Linux games, along with their license info. A good amount of them are FPS games, hopefully one of them interests you 🙂

I guess for tactical shooters, Urban Terror might qualify?

The information I’ve seen regarding deep discharge life-cycle for sodium ion is that the latest tech is actually extremely good, at least according to this. I don’t see how the lower voltage is a problem, since for grid situations you’ll have step-up transformers anyway, and the batteries can just be hooked up in series to increase the voltage.

They use abundant materials, will be much cheaper than lithium ion, don’t need to be actively cooled, and massively lessen the risk of rupture and fires.

The low density per unit of weight isn’t relevant for grid storage, so they seem pretty ideal.

Sodium batteries require very little rare earths in comparison to lithium batteries.

Sodium electric batteries, like the type that CATL developed? Or do you mean hot molten salt thermal batteries? Because I think the other poster is referring to the first kind.

There should be a tl:DW in the comments here.

Oh damn, even better than the estimates I found.

Ladybird is in a prime position if they keep up their steady progress, I really hope they succeed.

PNG is a lossless format, and hence results in fairly large file sized compared to compressed formats, so they’re solving different issues.

JPEG XL is capable of being either lossy or lossless, so it sorta replaces both JPEG and PNG

JPEG XL supports lossless compression with a roughly 35% reduction in file size compared to PNG.

No worries! :D

Ah! quite right, thanks for the correction :)

That’s a good argument, and as a fan of permacomputing and reducing e-waste, I must admit I’m fairly swayed by it.

However, are you sure JPEG XL decode/encode is more computationally heavy than JPEG to where it would struggle on older hardware? This measurement seems to show that it’s quite comparable to standard JPEG, unless I’m misunderstanding something (and I very well might be).

That wouldn’t help the people stuck on an outdated browser (older, unsupported phones?), but for those who can change their OS, like older PC’s, a modern Linux distro with an updated browser would still allow that old hardware to decode JPEG XL’s fairly well, I would hope.

The video actually references that comic at the end.

But I don’t see how that applies in your example, since both JPEG and JPEG XL existing in parallel doesn’t really have any downsides, it’d just be nice to have the newer option available. The thrust of the video is that Google is kneecapping JPEG XL in favor of their own format, which is not backwards compatible with JPEG in any capacity. So we’re getting a brand new format either way, but a monopoly is forcing a worse format.

Existing browsers and apps can’t render jpegXL without adding a new decoder.

Why is that a negative?

Jpeg XL isn’t backwards compatible with existing JPEG renderers. If it was, it’d be a winner.

According to the video, and this article, JPEG XL is backwards compatible with JPEG.

But I’m not sure if that’s all that necessary. JPEG XL was designed to be a full, long term replacement to JPEG. Old JPEG’s compression is very lossy, while JPEG XL, with the same amount of computational power, speed, and size, outclasses it entirely. PNG is lossless, and thus is not comparable since the file size is so much larger.

JPEG XL, at least from what I’m seeing, does appear to be the best full replacement for JPEG (and it’s not like they can’t co-exist).

TL:DW, JPEG is getting old in the tooth, which prompted the creation of JPEG XL, which is a fairly future-proof new compression standard that can compress images to the same file size or smaller than regular JPEG while having massively higher quality.

However, JPEG XL support was removed from Google Chrome based browsers in favor of AVIF, a standalone image compression derived from the AV1 video compression codec that is decidedly not future-proof, having some hard-coded limitations, as well as missing some very nice to have features that JPEG XL offers such as progressive image loading and lower hardware requirements. The result of this is that JPEG XL adoption will be severely hamstrung by Google’s decision, which is ultimately pretty lame.

JPEG is getting old long in the tooth, which prompted the creation of JPEG XL, which is a fairly future-proof new compression standard that can compress images to the same file size or smaller than regular JPEG while having massively higher quality.

However, JPEG XL support was removed from Google Chrome based browsers in favor of AVIF, a standalone image compression derived from the AV1 video compression codec that is decidedly not future-proof, having some hard-coded limitations, as well as missing some very nice to have features that JPEG XL offers such as progressive image loading and lower hardware requirements. The result of this is that JPEG XL adoption will be severely hamstrung by Google’s decision, which is ultimately pretty lame.

Please be aware, Odysee was recently purchased by a Crypto company that also acquired an NFT company.

For more info, see my comment here: https://slrpnk.net/comment/9749921

I would not recommend investing any time or money into the platform, as it will inevitably crash and burn as the owners walk away flush with cash while everyone else is left holding the bag.

Peertube is not ideal, but it is currently the only alternative that isn’t tied to a shady crypto scheme.

ROCm is it’s own hell (unless they finally put some resources into it in the past couple years)