fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

9.8K
active users

#chromium

21 posts20 participants0 posts today

It's funny and kinda frustrating how almost no one acknowledges the role #KDE played in forming the Web we see today.

It's KDE who created #KHTML, which was then in 2001 forked by Apple to create their #WebKit engine, and which was then used in #Chromium until version 28, when Google replaced WebKit with their own fork of it called #Blink.

And the only reason Apple forked KHTML and not #Gecko was because of Netscape's extensive and, as later admitted by Mozilla themselves,[1] often unnecessary usage of XUL/XPCOM, which Apple thought resulted in software bloat.[2]

So yes, almost every browser currenty existing uses an engine which is a direct or indirect descendant of KDE's KHTML.

And I'd bet my house that if there was no KHTML, and Apple were unhappy with Gecko, they'd probably create their own proprietary engine, and Google would follow.

So I'm kinda glad things ended up how they did, and there are no proprietary browser engines around.

Thanks KDE!

[1] - arstechnica.com/information-te
[2] - web.archive.org/web/2012102501

Ars Technica · Ars Technica sits down with Scott Collins from Mozilla.orgBy Jorge O. Castro
Replied in thread

@phantomkitty@tech.lgbt @phantomkitty@furry.engineer

You raised my doubt; so i checked:

Brave is Chromium-based, so Blink-based:
"#Blink is a browser engine developed as part of the free and open-source Chromium project. Blink is by far the most-used browser engine, due to the market share dominance of Google Chrome"
en.wikipedia.org/wiki/Blink_(b

en.wikipedia.orgBlink (browser engine) - Wikipedia

Что делать, когда истёк TLS-сертификат на ТВ-приставку

Chromecast второго поколения 9 марта 2025 года владельцы медиаприставок Chromecast второго поколения и Chromecast Audio столкнулись с неожиданной проблемой — все устройства прекратили работать . Как потом выяснилась, проблема была в просроченном TLS-сертификате . Это новая причина, по которой оборудование может выйти из строя в 21 веке.

habr.com/ru/companies/globalsi

ХабрЧто делать, когда истёк TLS-сертификат на ТВ-приставкуChromecast второго поколения 9 марта 2025 года владельцы медиаприставок Chromecast второго поколения и Chromecast Audio столкнулись с неожиданной проблемой — все устройства прекратили работать . Как...
#SSL#TLS#Chromecast
Replied in thread

Here are comments on the evolution of browser share in a year.
(The three samples are heavily skewed to English-speaking higher eds.)
Last year results: techhub.social/@estelle/112047
You may still answer in the previous toot.

3/4 Fediverse members use #Firefox proper. Same as last year.
We welcome other parts of the Firefox family (any browser with Gecko inside):
• The share of Librewolf mentions doubled since last year.
• The share of other Gecko-based forks mentions also doubled since last year. (Even though some Waterfox usage is not logged because i did not list it.)

The shares of Chrome and Vivaldi were stable for the first thousand answerers (maybe more IT inclined) but doubled with the later thousand (in the last 24 hours).

The share of the last line (Opera-Blink-Brave mentions) decreased since last year.

#browsers#webDev#poll

🚩 Chromium 135.x Turns Off Manifest V2 Extensions

It finally happened to me. I allowed my Chromium Web browser to update to version 135.0.7049.42 (Official Build) (64-bit) and it turned off a group of my older Manifest V2 extensions. Fortunately, using the Extensions page, I was able to re-enable them all... but I believe I read at some point in the future, this re-enablement feature will be removed.

Anyone remember the time when Chrome was considered a resource hog (mostly because it had better isolation between tabs)
I feel is worse now. I run too but firefox does seem to deteriorate more than
Having had firefox get killed by the OS I've just done a "swapoff -a; swapon -a" to make the system more responsive again 🙄