After reading this, checked my existing styling as processed through autoprefixer, found the vendor prefixes that had been added, and manually added them to my styling — so it now doesn’t require any additional tools for cross-browser compatibility.
After a search in the NetBSD packages for lightweight web browsers, the winners are: vimb, dillo, luakit and netsurf.
Dillo's new release 3.1.0 still hasn't landed, so no HTTPS there. Luakit is very neat, extremely lightweight, minimal, has vim-like bindings and would be perfect if it weren't for the constant white flashing between each pageload when using a custom, darker CSS. NetSurf is also quite neat, with tab support for heavier sessions.
The winner for me is vimb, which although leaving tabs to the window manager, has vim-like bindings, is pretty minimal and does not cause flashing when switching between pages on a custom darker CSS setting.
Honor mention to Arctic Fox, a Pale Moon clone that hits peak nostalgia with the pre-omnibar Firefox look. No theming, not as lightweight, but going strong at 29.5k commits since 2018.
I'm trying to figure out the best browser combination for my needs. Generally, Firefox covers almost everything I need, but it's slow on Android and drains a lot of battery. I've tried Vivaldi, Chrome, and Brave. Of these, only Brave has the features I need, like full history sync (not just typed URLs), and the ability to send tabs to other devices. However, with its focus on crypto and AI, it seems too hype-driven for me. Also, none of them work on FreeBSD without using a Linux jail.
I use Firefox Focus to open all links by default. It does a great job of deleting everything after it's closed so I don't have to worry about cookies or trackers.
I use Firefox when I want to open a website I need to login to or have cookies for, which happens a couple of times a day. It's synchronised with my desktop. I swipe it away when I'm done so it doesn't keep running in the background.
After several years of warning after warning after advisory after advisory and calls to repeatedly update or remove andNOT USE CHROME by the Department of Homeland Security, it should be inconceivable that anyone does - but they do.
Sometimes these are patched with automatic updates before horrific and catastrophic results occur, sometimes not. To be frank, part of the problem stems from the fact that Chrome is the largest attack surface out there where browsers are concerned, but notwithstanding it being the fav target are also serious privacy concerns that aren't shared by other chromium based browsers.
To be fair, many exploits are indeed shared by other chromium based browsers, but not most, while some are related to other browser capabilities, like WebRTC, but it's still best to just ditch Chrome and never look back.
Here's more coverage on vulnerabilities issued less than a month ago. It took 3 seconds to bring this up, and no, not using Google, which didn't reveal this when I tried that search engine in a subsequent search, lolz. Why would they return SERPs that poo poo their own product?
There's truly only one way to ensure safety - unplug. But there's a lot of simple things you can do to exact a reasonable level of security, so why not observe some of those best practices? It's not like it will cramp your style.
Anyway, that's my two cents. h/t to @darnell for raising awareness of this latest brokewell. Make sure you take the time to visit the link he's provided for you too.
There are plenty of #Browsers that run on #Android (to name a few, alphabetized):
Brave Browser
Chromium
DuckDuckGo
Firefox
Kiwi
Vivaldi
IMO, No one should be running Chrome - Desktop or otherwise. It's a privacy nightmare even when there aren't CERT warnings circulating.
Decided to test some browser fingerprinting this morning via the Cover Your Tracks tool by @eff. @brave, @librewolf, and (no surprise) @torproject all performed (or appeard to perform) better than @mullvadnet.
Dunno. I like uBlock Origin a lot but disabling scripts per site is not something that feels very comfortable for me. With LibreJS it can be quite a hassle but I’m already quite used to that, and on the way I kind of learn things. Like that blocking scripts about Apple and Google logins at Twitter with LibreJS helps with clutter free reading and not being asked to login.
How does this work exactly. I get it can see a fair amount of stuff on my browser, but if I close the page and then reopen the visit doesn’t go to 2 and I don’t see the signature I added. Does this mean it cannot fingerprint my setup?
Edit: I also tried this on my fairly vanilla firefox installation with ublock origin and I see that the visit count will go up as I return to the page—so I suppose the fingerprinting is working on that setup. On my iPad with adguard each visit appears to be unique.
"The early results come after the EU's sweeping Digital Markets Act, which aims to remove unfair competition, took effect on March 7, forcing #bigtech companies to offer mobile users the ability to select from a list of available web #browsers from a #choicescreen."
I really made a mess...
Because I tried to disable the Linux keyring, I deleted something that made web browsers unable to save the logins/passwords, so I have to log in every time I go in.
Me stupid... #Linux#Vivaldi#Browsers#Internet#passwords#Mints