「 Window managers don’t have much reason to support better controls for many browser windows until browsers start using them and browsers don’t want to invest in making a window-per-page experience better until most popular operating systems have the window management features to make it attractive 」
@jbzfn another related topic is the proper interaction of browsers with the window manager's further spatial aspects, such as virtual desktops and/or #KDEPlasma's Activities.
On top of that, browsers have similar capabilities such as #Firefox Containers or #Chrome tab groups.
I feel like there's a huge potential in terms of improving usability and standardization between browsers and window managers.
Складено топ найпопулярніших браузерів. Рейтинг складено з урахуванням статистичних даних Statcounter.
Щодо частки ринку у відсотках картина виглядає наступним чином:
1️⃣ Google #Chrome 66,13%
2️⃣ #Safari — 11,87%
3️⃣ Microsoft #Edge — 11%
4️⃣ Mozilla #Firefox — 5,65%
5️⃣ #Opera — 3,09%
6️⃣ #IE — 0,55%
While I agree with the @fsf warning about the emblematic value of the decision by #Google to pull support for #JpegXL from #Chrome, their article <https://u.fsf.org/3z8> is as empty as could be, especially considering that #GNU#IceCat doesn't support JPEG XL either (being based on a #Firefox branch that doesn't build #JXL support in.) You want to show that #FLOSS can do without? Do it by actually supporting what you complain Google is failing to.
Ikona kłódki w pasku adresu przeglądarki już od dawna nie oznacza, że odwiedzana strona jest bezpieczna. Oszuści rzadko teraz rezygnują z certyfikatów SSL, bo ich zdobycie nie stanowi większego problemu - wystarczy za darmo skorzystać z Let’s Encrypt. Google zdaje sobie z tego sprawę i dlatego z kłódki rezygnuje:
Is your primary e-mail account #gmail? As in the e-mail account we would use to communicate, so not necessarily your job related e-mail. Feel free to share widely.
@jwildeboer
Sadly it is a #gmail account. My personal email flow is way bigger than my work related because we in the office use Discord. I stop using #chrome years ago and I want to drop everything google.
Really hate to do this, but #Edge once again made my new tab page open in "content visible" mode with all the junk news displayed. I will be moving off it as my default browser. Really wish #Safari still worked on Windows, because now I have to resort to #Chrome since it works everywhere I do.
And to the Edge team: please, for customers' sake, do not mess with someone's settings. You lost all my open tabs on iOS once and now this. I will miss vertical tabs :-(
It's interesting to me that so many of us are regular smartphone users now, and we all use them in such different ways.
Figured I'd look at my phone's most used apps as I've never paid much attention to it before. Out of the 55 apps I've used in the last 6 days, yeah, my top 6 aren't a surprise to me at all. 🤣
So annoying. There is a 1 pixel discrepancy between Safari and Chrome's vertical centering of this font and I can't get the text to appear exactly the same. I've been dealing with pixel discrepancies in cross-browser web development for years, but still can't handle it lol.
Do you work in #webdev? I want you to order an old phone from ebay right now. Like a Samsung Galaxy S4 or something. Go visit your website with it. Did you have a good experience? Well, 1 in every 10 visitors has that experience. Fix your shit.
The #webperf lab tools that allow using Chrome < 109 are valuable in explaining to customers what their #LCP hacks were doing before the "low-entropy" / BPP update and how they have been rendered inoperable since April 4th.
Mastodon often fails to show up-to-date context and information on posts from remote instances. Substitoot is a browser extension that fixes this.
Now also available for Chrome! Note: the current published Chrome build has a dumb bug where it doesn't start up properly, so please open the "settings" yourself to set it up! The fix is in review.
This is a great series of articles by security researcher Mike Kuketz that documents the data transmission behavior of popular web browsers on their default settings, examining the type of connections they make and what data they "phone home" with:
Great, it looks like whatever they changed in Chrome no longer trusts Kitten’s¹ local certificate authority (installed and trusted by the system trust store, as you’d do in a spit enterprise).
Applies to previously trusted and working certificates too.
(The directly related module is Auto Encrypt Localhost²)
Going to look into it today and see if I can’t find a workaround.
Right, well, first the good news: It doesn’t look like anything has changed in how Chrom(ium) handles certificates installed in the system trust store.
Now the bad news: I have no idea why the certificate authority that was previously trusted on my main development machine is now showing up as untrusted. Could a Fedora Silverblue update have broken it? Will keep looking into it.
They say they want to reduce #TLS certificate lifetimes because there's no good revocation mechanism, and all the problems they mention could be solved by strictly requiring stapling with the TLS feature extension in certificates (using RFC 7633). Stapling doesn't place a huge burden on CAs (because only the server using a certificate has to update its cached response now and then), it doesn't expose client behavior to CAs (because clients only need to talk to servers they want to talk to), and if stapling is required by the certificate it fails closed in case of revocation as soon as the last positive response expires (currently CAs usually issue responses with a lifetime of about a week, but that could be reduced easily).
Shorter certificate lifetimes aren't necessarily a bad thing, but the reasoning doesn't make sense.
@airtower Does anyone know how it will be work in practice? As I understand, they want to limit lifetime not only for end certs but also CA certs, right? Does it mean after some time point certs would stop working when ANY part of the chain would have longer lifetime than new limits?