m0xEE @m0xee@librem.one

#inPURRection #gattini #kittens

Finally #Gecko ESR 91 is rendering websites on #SailfishOS. I was getting worried it might never get there. All the gory details to follow. 🦎 🐟

New Forest Swords album dropped: https://forestswords.bandcamp.com/album/bolted
I've even signed up for the "listening party" — it's the BandCamp thing, when you listen to some new album and can interact with other fans and the artist while it plays
But slept through the most of it — no, the album isn't bad, I just fell asleep a couple of hours before if was supposed to start and forgot to set the alarm.
Matthew himself was reluctant whether to hold it with all the shit going on with BandCamp.
The album itself is quite good, especially the beginning, with bit of harsher than usual "industrial-like" sounds, but surprisingly it grew old on me really fast — which is surprising for FS album, I have most of his albums on CDs and usually spin them for days. Well, maybe it's just me, who listened to it too much for the past few days.

looking for something? 🔍
happy #caturday 😺

@iska

#cats #caturday

it's been almost completely forgotten that the 8086 was intended to be a Pascal machine. C was barely on the horizon when the 8086 was conceived.

which explains at least one apparently bizarre choice: segmented pointers are a whole lot less painful when "pointer" is its own type, and not compelled to behave like an integer

also explains why "ret N" increments the stack pointer after popping the return address; it's intended to pop the caller's parameters off the stack again, which is what Pascal-derived languages want (and the complete antithesis of C)

...of course, given that, it's ironic that the first high level language implemented on the 8086 was Forth, which is possibly the only language to be an even worse fit for segmented addressing than C. oh well

sierra my beloved

#kubernetes jokes

She is always stealing my spot. Mostly because it’s warm but sometimes I suspect it’s for the Internet.

#CatsofMastodon

#inPURRection #gattini #kittens

They be precious. #catsofmastodon

Crocs is taking a step beyond clogs and going western with cowboy boots. https://t.co/cICKX0O1dk

Cats! 😻

#cats #caturday

Today, we're announcing Proton CAPTCHA, the world’s first CAPTCHA with built-in censorship-resistant technologies to prevent bot and spam attacks.

We needed a tool that tells the difference between humans and automated bots, but also a CAPTCHA option that meets the high security and privacy standards you expect from us.

This is only the beginning. You can expect more innovation in this space.

More: https://proton.me/blog/proton-captcha

Another one of those furry critters.

#cat #catuesday

Not a good photo, but a reasonably good blep.

#cat #blep #bleptember

@Mina @KDWang @chris_e_simpson @rugk
This comment was more or less a joke, but okay, if there are those who take my words seriously, I'll make a longer writeup.

Technically yes, they are open, but Google controls the reference implementation. If you come up with your own implementation and they want it gone — they will accomplish it easily, they'll just start changing theirs breaking compatibility and you won't be able to keep up with them — you simply don't have their manpower.
If you start extending your implementation, no one will use it as the one used in Chrome doesn't support that.
So it's open in words only, de-facto they have complete control over it, you can't compare it to ARPA stuff — it's nothing close to that. US military can't exercise such control over the protocols we use today.
Their efficiency is also debatable: WebP offers about 10% better compression on average — it's not a game changer, hardly enough to justify new codec to be supported in every browser. Imagine yourself developing a completely new browser today, if everyone uses WebP, you will have to support it too. And you have two ways: implementing it from the ground up spending developer-hours on that or you can rely on Google's implementation — last week a vulnerability has been discovered in their implementation that was rated high severity even by Mozilla. Now we take a step back to the fact that it only offers a marginal advantage compression-wise over existing codecs and now supporting it doesn't seem reasonable at all 🤷
I think the sole purpose of its existence is making developing new browsers harder. KHTML, predecessor to WebKit has been developed by KDE project. Is something like that possible today? I don't think so — modern web browsers are too complex and adding more to that complexity strengthens our reliance on Chrome with Firefox and its derivatives being the sole alternative. Well, Safari too, but it's only available on Apple's platforms.
Of course 10% compression gain is still reasonable if you're Google as you serve petabytes of data — for everyone else it simply doesn't make sense, no one else has such numbers to justify implementing new codec for such a marginal gain.
All in all, WebP is beneficial for Google and no one else.

WebM is only a container, I don't think it's necessary either, but being relatively easy to implement, I don't have anything against it. Let us talk about VP9 though — everything said about WebP above still holds and more: I've seen videos on YouTube for which VP9 stream size was bigger than H264 in side-by-side comparison of equally specced streams: YT format 248 vs 137. So it's not even always better — not in all use cases. Even on Google's own YouTube! And yet, that is the codec they want you to use, it's used by default and, sorry, I don't have any examples at hand, but there are videos for which VP9 stream is available, but AV1 stream (codec also often associated with Google, but over which they have much less control) of same resolution and framerate isn't — and I think it's being done on purpose!

Of course, I might be biased here — I most probably am, as there are few things that I hate more than Google, but I'm not completely unreasonable and I believe that most of codecs and technologies related to web and developed by Google or in cooperation with Google are open on paper only and exist for the sole purpose of market lock-in. And I strongly encourage everyone not to use any of them: be it WebP, Brotli, VP9, QUIC-HTTP/2 or HTTP/3.

#Google #Web #WebP

@m0xee @FalconMarkSix

U vil eat ze JabbaScript and u vil like it

https://www.theregister.com/2023/09/25/gmail_basic_html_discontinued/