m0xEE @m0xee@librem.one
- Experimental PPC-related (and hosted) instance — now with ✨snac2✨, so I hope it won't be down 90% of time 😏
- https://nosh0b10.m0xEE.Net/m0xEE
None
Just in case: DMs/PMs simply don't exist on this instance as concept — don't use them, use the other instance if you absolutely have to, or send an email to any address at m0xEE.Net or .Com or .Org, but I prefer keep most communication public.
Joined Nov 2020
@neural_meduza
Ну, в принципе как-то так ведь и случилось 🤖
m0xEE
boosted
@oku_yama_old
В целях экономии бюджета, было решено реорганизовать Минпромторг России и Следственный Комитет в единое ведомство — Министерский Комитет Следствия и Торговли Российской Федерации. Для сохранения эффективности работы было решено объединить и их глав: Дениса Мантурова и Александра Бастрыкина.
Глава объединённого ведомства Денисандр Бастыров и выступил с предложением о доработке.
@viktuuri0nIce It didn't affect her lifestyle in the slightest, she can still bring her toys to me if she wants me to play with her and dry cat food I use has small granules so she can just swallow them without chewing, she even prefers it over wet food.
For this breed problem teeth are common, older one would probably have to undergo this too sooner or later, I do my best to keep them though by cleaning them and giving him special toothdrops for cats when I notice irritated gums.
@viktuuri0nIce
I have two "vampires" and each of them has a problem with one of their fangs 😿
My younger cat had her molar teeth removed and there was no way to keep this fang, the vet did his best. But in the end it has been for the best, she got a lot healthier after that and even gained a bit weight, which didn't happen to her in years. I don't mind if it's for her best.
@neural_meduza
> на Плутоне
Теперь, когда говорят «поехавший», хотя бы понятно куда 😂
m0xEE
boosted
@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
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
@thor
Hey, I can do both! 😂
I mean, you can have really niche interests and views, but still be unfun about them 🤭
m0xEE
boosted
U vil eat ze JabbaScript and u vil like it 
https://www.theregister.com/2023/09/25/gmail_basic_html_discontinued/
https://www.theregister.com/2023/09/25/gmail_basic_html_discontinued/
@zeljkazorz
> she
He-he, looks like I've grown overconfident in my ability to tell their gender apart by the shape of their heads and made a mistake 😹
Good luck with your checkup, I hope all is well!
@zeljkazorz
Why is he shaved like that, did he have an ultrasonography? 😸
@meeper @mia
Sure, even dismember them and sell for organs. Actually that's how you get rewarded. It's like premium accounts, but better and more exciting (well, if you're into that thing and don't get caught).
But 15% go to the social network — those servers aren't going to pay for themselves 😏
New revenue models get explored, you know…
@nrcha
Become ungovernable, wear Monday socks on a Friday! 😂
@psychictides
Something like Double-Blind Trial, but slightly more exciting? 😅
@viktuuri0nIce
Splendid fangs!
One of my "vampires" had to have on of her fangs removed — the other one broke the tip of one of his. But that doesn't prevent them from chewing on things and stealing them by carrying them in their mouths 😹
@pyrate
Is it en elaborate German word for housecat? 😹
@Merk_94
Does using electric toothbrush enable you to electrocute someone? 😱
What about oral irrigator then, drowning? 😅
@lowqualityfacts
m0xEE
boosted
The Titanium PowerBook G4 still looks like a total work of art even 20+ years later.
And don't get me started on the art that was Aqua in Mac OS X. Looks playful but still like a serious Operating System -- none of this flat, overly joyful and bubbly bs we have today with stupid overly saturated colors and is completely unusable.
Old Apple hardware and software aged like the finest of all wine.
@nasamuffin And shoot out rays to behead those who have caused that anger! 😈
- Experimental PPC-related (and hosted) instance — now with ✨snac2✨, so I hope it won't be down 90% of time 😏
- https://nosh0b10.m0xEE.Net/m0xEE
None
Just in case: DMs/PMs simply don't exist on this instance as concept — don't use them, use the other instance if you absolutely have to, or send an email to any address at m0xEE.Net or .Com or .Org, but I prefer keep most communication public.
Joined Nov 2020
