Applescript support in #ArcBrowser is pretty broken. One space, one window, three tabs open, but via Applescript it reports a list of 57 (!) dysfunctional Tab objects.
What do y'all fellow Firefox users think about this "Firefox on the brink" article? I know Chrome and Chromium browsers are pretty much standard a lot of places (sigh) and maybe Firefox is a niche thing, but I'd love to hear thoughts on this and what it might mean for the future.
"This article isn't specifically about #privacy issues only, it's about promises that are being broken, which might be about privacy. It is also about the lack of user freedom, as in the choice to enable or disable features, such as automatic updates, or forced usage of third party services, or software that the user generally is unaware of or don't have a say about."
Well, my code-level support ticket was picked up by Apple, and I think I have my answer — it looks like I'll have to sell my upcoming app Browser Actions outside the App Store after all.
If you do the final exercise, you will end up with a browser that speaks funny! 😀
Like the Rust in Android course, this is mostly relevant to the engineers who work on Chromium itself. Others are welcome to play along, but you should already know how to build Chromium.
Ci sono più motivi, alcuni più controversi di altri ma uno che mi sembra ugualmente condivisibile è questo: manteniamo per tutti la possibilità di scegliere.
So will Google's "Manifest v3" ad-blocker death spell for Chrome also go into #Chromium and other Chrome-based browsers like @Vivaldi and #Edge?
I see a nice Firefox revival on the horizon! 🎉
First #YouTube pushing people to better ad blockers & making them so much better, now #Chrome pushing users to #Firefox... #Google is doing a lot of good stuff for the web lately! 😜
Looking for a top-notch #browser for your #Mac? Look no further than #ArcBrowser. With its advanced Split Views and other impressive features, Arc is the perfect tool to help you improve your #macOS#web browsing experience. Plus, it's built on the #Chromium platform, so you can rest assured that it's fast, stable, and secure.
Just uploaded some WIP patches which close the missing gap to get hardware video decoding to work with the #Linux (not #ChromeOS) #Chromium#Wayland backend. Both #vaapi (only Intel) and #v4l2 (only stateless).
KTOWN: live ISO with Plasma6 Alpha. Also, chromium now supports HEVC/AC3 playback
I have uploaded a 5 GB ISO file containing a new KTOWN variant of Slackware Live. This is the KDE Plasma6 Alpha release. Play around with it and perhaps you will be able to contribute to an improved Beta by finding a
⚡ Google gives up on that API that looked more than a bit like DRM for websites
「 "We’ve heard your feedback, and the Web Environment Integrity proposal is no longer being considered by the Chrome team," the biz's Android team said on Thursday.
The Chrome team has thus submitted a commit to revert the project code that had made it to the corporation's browser 」
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.
Estoy muy contenta porque hoy he descubierto que alguien mantiene actualizada en Github una versión #legacy de #Chromium que funciona en ordenadores antiguos y esto me ha permitido abrir #Slack en mi MacBook Pro del 2008 (15 añitos ya de ordenador y aquí sigue, como un campeón).
Necesitaba Slack porque lo usa un cliente y aunque tengo un ordenador algo más nuevo (de 2014) que sí lo soporta, no quería cambiar de equipo.
Run on Debian 11
Me acostubre a este fork de l navegador de Google y corre bien pero...no se no se, ya mismo le meto el Debian 12 y a ver si Firefox me corre bien.
I do weekly updates (to stable-security and oldstable-security) of debian's chromium packages, and there's an average of like 10 CVEs each week.
The number of copies of #chromium embedded in other programs and toolkits that rarely get update is extremely worrisome. Like, hundreds of CVEs per library just sitting there, waiting to be exploited. Chromium devs want to use Rust for memory safety, which is great, but providing an actual stable API might do even more for improving overall security.
I'm testing something new now. Instead of running all kinds of horrible #Web#Electron#Chromium apps separately, I'll try running them all as pinned tabs in #Firefox. Let's see how this goes. I might even save some system resources, who knows.
@tedzanzibar I would actually urge you to disable to auto update for the #bitwarden extension. Looks like @bitwarden implemented #passkey support in a way that makes it unable to login using hardware tokens like the #yubikey or #nitrokey . If you already use those as passkeys, updating the extension will effectively lock you out of services where you need a passkey to login. Tested on #chromium, but I assume #firefox will behave the same.