Notices tagged with chromium, page 2

🍪 Sooo, Google’s sticking with third-party cookies in Chrome, but you don’t have to.

🛡️ If you haven’t already, then today might be the day to make the switch to our browser.

Don’t worry, you can easily bring all your bookmarks, extensions, and browsing history along for the ride.

https://vivaldi.com/download/

Btw, what do you think about their plan? We want to read your thoughts! 👇🏻

#google #Chrome #Chromium #Cookies #privacy #tech #Technology #browser

+1 reason why you must stop using Chrome and, if possible, Chromium browsers

(Upd: link to a post in Fediverse describing details https://fedi.simonwillison.net/@simon/112757810519145581)

#Privacy #Tech #Technology #Browser #Chrome #Chromium #Firefox #Google #BigTech

ただ #Chromium というか #Blink 一強は良くない

I use FireFox, yes sometimes it isn't perfect, neither is the current big fish, and by a lot. Sure there are a lot of #Chromium based browsers out there but so are #FireFox based browsers.
If one needs #HDR or other still chromium exclusive features, sure use it I would as well, but FireFox(#Gecko) is arguably the last competing browser engine.
This paired with FireFox being 99+1% on pair with Chromium should be more than enough of a reason to give it a shot once in a while IMHO.

#Chromium (and #Chrome) begins phasing-out Manifest v2.

https://blog.chromium.org/2024/05/manifest-v2-phase-out-begins.html

This means, among other things, that uBlock Origin is about to be disabled in Chrome. Google will choose a different extension to recommend but it can not be as effective as #uBlock Origin.

Following #Google's example, may I instead recommend you switch to #Firefox.

Firefox will continue to support Manifest v2, and consequently uBlock Origin and other extensions that can not be implemented with Manifest v3.

Happy browsing.

There was a time when #Firefox was the choice in creating a new browser. It ended after #Chromium came into the picture.

I don't know why, I can't find information about it, but if I'll take a guess:
1. Something changed in Firefox that it's no longer a good choice to fork and create new browsers.
2. Chromium made it very easy to build a new browser on top of it.

The only remaining Firefox forks are #Palemoon, #Waterfox, #LibreWolf, #フロープ ( #Floorp ), #Basilisk, GNU IceCat, and Tor Browser.

So, what happened, really? Anyone with the knowledge? Was it really as simple as #2 (see above)?

Did you know that the #Snap version of #Chromium (included by default in #Ubuntu) saves all your #passwords as plain text? 🤦
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1996267
#Linux #Security

@aral There are currently only 3 major web browser engines:

blink: Google #chromium, Google Chrome, Falkon, Brave, Vivaldi, Opera, ungoogled-chromium, Microsoft Edge, …

#webkit Apple Safari, Konqueror (webkit is a fork of discontinued KHTML), GNOME Web (Epiphany), Midori, qutebrowser, surf, …

gecko: Mozilla #Firefox, SeaMonkey, GNU IceCat, Waterfox
goana: is a fork of gecko

If AI shows up in newer versions of Firefox, I will be going into about:config and turning it off.

LibWeb: #Ladybird

LOL. Found another craziness with #Chromium which #Firefox got right the first time.

`@-supports selector(:lang(\*-latn)` is the only one that works in Chromium. However, none works for wildcard `:lang(\*-C)`.

Firefox accepts `(\*-latn)`, `("*-latn")`, and `("\*-latn")` for both.

Here's a sample code:
```
/**
* NOTES:
*
* @supports selector()
* - :lang(*-latn) = Firefox:no || Chromium:no
* - :lang(\*-latn) = Firefox:yes (insensitive) || Chromium:yes (insensitive)
* - :lang("*-latn") = Firefox:yes (insensitive) || Chromium:no
* - :lang("\*-latn") = Firefox:yes (insensitive) || Chromium:no
*
* :lang(C)
* - :lang(*-latn) = Firefox:no || Chromium:no
* - :lang(\*-latn) = Firefox:yes (insensitive) || Chromium:no
* - :lang("*-latn") = Firefox:yes (insensitive) || Chromium:no
* - :lang("\*-latn") = Firefox:yes (insensitive) || Chromium:no
**/
@supports selector(:lang(\*-latn)) {
:lang(\*-latn) {
color: magenta !important;
}
}
```

1. Firefox and Chromium-based browsers will pass the `@supports selector` check.
2. However, only Firefox will process `:lang(\*-latn)`. To this day, Chromium doesn't support wildcard `:lang(\*-latn)`.

To ensure Chromium-based browsers gets filtered out, use:

```
@supports selector(:lang("\*-latn"))
```

Chromium doesn't know what to do with the wildcard `:lang(\*-C)` selector. It supports one method in `@supports selector()` but not none in `:lang(C)`. The lack of wildcard support in `:lang(C)` selector has been that way for years as well.

#Mozilla Firefox devs really know what they're doing to make the #web better. While Chromium is proving to be the new #IE6, holding us back.

(P.S. I stopped filing bugs to Chromium years ago because they love to shut down people with “no one uses it” and “there's a workaround” so “not fixing”. Why even bother if that's their culture?)

#webdev #CSS

Another thing I really hate about #Chromium (-based browsers) is their implementation of #CSS #ruby. #Firefox did the right thing in its CSS ruby implementation.

Learn from #Mozilla.

It's 2024 and #Chromium still lack support for “:lang(C, C)” and “:lang(\*-C)” which #Mozilla #Firefox has for years now.

The only reason we still have a loooong “:lang(C)” #CSS code is because of Chromium (as usual?).

*shrugs*

#i18n #multilingual #webdev

#DataPrivacyWeek Day 5

Since #privacy online became a broader concern, #BigTech companies now attempt to appear privacy-oriented while just changing the way they spy on their users.

Such is the case with #Google disabling third-party cookies in #Chrome and developing technologies such as #FLoC or #Topics, both of which we've opposed from the very beginning.

Yes, our browser is based on #Chromium, but we do a lot of modifications to the code and take special measures to always protect our users and their privacy.

Read more: https://vivaldi.com/blog/news/alert-no-google-topics-in-vivaldi/

Commentary: Will #Firefox rise like phoenix from the ashes in 2024? https://www.ghacks.net/2024/01/07/will-firefox-rise-like-phoenix-from-the-ashes-in-2024/ "The unlocking of full add-ons support in Firefox for Android may be the fire-starter that Mozilla needed." I wonder how many users will notice Manifest v3. I've used Firefox on PC for 20 years, but on Android I use Kiwi, a Chromium browser that blocks ads and supports many add-ons. #Android #Chromium

Use a Browser That Blocks #Tracking

https://themarkup.org/gentle-january/2024/01/04/use-a-browser-that-blocks-tracking

#privacy #brave #chromium #foss

@jrballesteros05@social.linux.pizza I worry about this too. While #Firefox is free and open source software, meaning anyone can take over maintenance theoretically, the source is also a huge mess which is getting increasingly hard to figure out what's where, and why things work a certain way. Back when they had an IRC channel they actively refused to explain how certain things worked either, which didn't really help in spreading the knowledge to keep Firefox going into the indefinite future.

Sadly, #Chromium is only acting on the whims of #Google and therefore cannot be trusted as a reasonable competitor, and I don't expect any new browser engines to be made given how ridiculously complex the web has been made.

Sometimes I think it'd be better to just give up and use #Gopher instead, but the world won't just move with me and I'd still be forced to use a regular web browser for many things, such as banking or dealing with the government.

@hexaheximal@blob.cat @esm @hexaheximal@wetdry.world
You may call me a #minimalism evangelist but

everytime something that could've been barely Megabytes as an #AppImage, #FlatPak, #Snap or Kilobytes as a #CLI tool instead shoves yet another entire half gig copy of the #Bloatware-#Browser that is #Chromium onto the Desktop despite using not even 0,1% of it's featureset

I call this a systemic failure in Software Architecture.

Browsers are the most attacked applications on #Linux beyond CMSes and Webservers...

A lot of people seem to have opinions on browser cores.

We built one. From scratch. We know what it takes to do, also knowing that big tech does its best to create incompatibilities.

Presto was, IMHO, the best browser engine, but that was more than 10 years ago. I wish development had not been halted and it would not have been halted if I had had anything to say about it.

Now we build Vivaldi on Chromium and we do feel it was the best we could do. We can build a great browser based on Chromium. I hope you are all enjoying Vivaldi. If you have not tried it, please do.

#Windows #Linux #macos #Android #Google #Gecko #Chromium @Vivaldi

Fast 80% der User verwenden ein Browser, der auf #Chromium basiert.
Chromium gehört #Google und damit einem großen Werbenetzwerk.

Nun möchte Google eine Technik in Chromium Pushen, die Werbeblocker aushebeln kann.
Außerdem wird Firefox auch auf #YouTube benachteiligt um die User noch mehr zu Chrome zu Pushen.

Das ganze kommt mir schon sehr nach dem Ausnutzen einer Marktbeherschenden Stellung vor.

:BoostOK:

Three days ago, the 4th of November, would've been #KHTML 25 year anniversary. 🥳

Hoorrray!

WTF is KHTML?

Chances are you are kind of using it, because #WebKit and #Blink rendering engines are all forked from this open-source project originally intented for the browser of the KDE window environment.

That basically makes #Opera, #Safari, #Chrome, #Chromium and #Brave (and possibly others) all *siblings*.

KHTML is *literally* the mother of all browsers.

"KHTML is dead - long live KHTML!" 😀