#dillo — Public Fediverse posts

#Dillo #Dillo3 #DilloBrowser #LinuxMint #LinuxMint22 #LinuxMintXFCE

#Dillo #Dillo3 #DilloBrowser #LinuxMint #LinuxMint22 #LinuxMintXFCE

⚙️ Instalei o navegador Dillo no Linux Mint 22.3 (Ubuntu 24.04 LTS) e funcionou!

📦 Arquivo de pacote obtido em: https://debian.pkgs.org/sid/debian-main-amd64/dillo_3.3.0-1_amd64.deb.html

#dillo #dillo3 #navegador #NavegadorWeb #browser

@dillo

⚙️ I installed the Dillo browser on Linux Mint 22.3 (Ubuntu 24.04 LTS) and it worked!

📦 Package file obtained from: https://debian.pkgs.org/sid/debian-main-amd64/dillo_3.3.0-1_amd64.deb.html

#dillo #dillo3 #browser #DilloBrowser

@dillo

⚙️ I installed the Dillo browser on Linux Mint 22.3 (Ubuntu 24.04 LTS) and it worked!

📦 Package file obtained from: https://debian.pkgs.org/sid/debian-main-amd64/dillo_3.3.0-1_amd64.deb.html

#dillo #dillo3 #browser #DilloBrowser

#Dillo 3.3.0 has been accepted in #Debian unstable (Sid). It will be available in testing (Forky) in a few days. 🥳

Thanks a lot to Nikolas Nyby who has stepped in as the new Debian package maintainer and got the new version packaged and accepted.

https://tracker.debian.org/pkg/dillo

#Dillo 3.3.0 has been accepted in #Debian unstable (Sid). It will be available in testing (Forky) in a few days. 🥳

Thanks a lot to Nikolas Nyby who has stepped in as the new Debian package maintainer and got the new version packaged and accepted.

https://tracker.debian.org/pkg/dillo

#Confession: It's slightly difficult to tell people not to use LLMs to summarize search results when actually dipping into a webpage for the information you need is so flipping painful and annoying. :/

Someone needs to write a searchbot kind of like #FrogFind that does a web search for you and presents you with a static html version of any usable results. Kind of like having a #Dillo front end to the web minus all of the typical JS nonsense.

#Confession: It's slightly difficult to tell people not to use LLMs to summarize search results when actually dipping into a webpage for the information you need is so flipping painful and annoying. :/

Someone needs to write a searchbot kind of like #FrogFind that does a web search for you and presents you with a static html version of any usable results. Kind of like having a #Dillo front end to the web minus all of the typical JS nonsense.

Well, I felt rather badly when I got a post in my stream from the official Fediverse account for dillo.

You see, I hadn't included it in my recent HowTo, a cookbook style tutorial on Browsers in Linux, or rather, how to install a boatload of them, and all kinds of them. I even went so far to include one produced and maintained by a company that I literally loathe (and even taught their official MCSE curriculum for them starting back in the mid 90's)...

But I left out dillo. I was tired, and truth be told, it really isn't easy authoring these types of technical publications - you literally need to go through each item on a VM you spin up and take it step by step to make sure that when a neophyte comes around and wants ot simply copypasta your instructions - they can do that, and it will work.

So anyway, the devs over at the dillo project posted on the Fediverse and I immediately was guilt-ridden for not including them. So I went and started to edit my earlier HowTo; I came out about 5k characters over count (and I think my server's already configured for 12K chars).

Anyway, long story short, here's one of my latest contributions to the #FOSS community, specifically, one that's published in the #Fediverse first and foremost. It includes almost every browser you've probably ever used, and certainly, many you probably haven't.

I had to Quote-Post my original so it's kinda kewl with an entry point starting with dillo. I think that's pretty awesome, and it quotes the original (part I if you will) that starts with Vivaldi.

I don't usually ask, but especially with respect to this HowTo/Tutorial, the more people that boost it, the further it will reach, and the more people it can benefit. Give it a gander and if you think others will find portions of it advantageous... well, feel free to boost it.

So without further ado, Here's the link to the Linux Browser HowTo

I hope you find it useful, and Enjoy! 🤗

#tallship #FOSS #Fediverse #Browsers #dillo #Microsoft_Edge #Firefox #Vivaldi #Brave_Browser #DuckDuckGo #Chromium #Opera #Chawan #Lagrange #Tor #Lynx #Elinks #Links #Nyxt #Epiphany #Falkon #Konqueror

⛵

Well, I felt rather badly when I got a post in my stream from the official Fediverse account for dillo.

You see, I hadn't included it in my recent HowTo, a cookbook style tutorial on Browsers in Linux, or rather, how to install a boatload of them, and all kinds of them. I even went so far to include one produced and maintained by a company that I literally loathe (and even taught their official MCSE curriculum for them starting back in the mid 90's)...

But I left out dillo. I was tired, and truth be told, it really isn't easy authoring these types of technical publications - you literally need to go through each item on a VM you spin up and take it step by step to make sure that when a neophyte comes around and wants ot simply copypasta your instructions - they can do that, and it will work.

So anyway, the devs over at the dillo project posted on the Fediverse and I immediately was guilt-ridden for not including them. So I went and started to edit my earlier HowTo; I came out about 5k characters over count (and I think my server's already configured for 12K chars).

Anyway, long story short, here's one of my latest contributions to the #FOSS community, specifically, one that's published in the #Fediverse first and foremost. It includes almost every browser you've probably ever used, and certainly, many you probably haven't.

I had to Quote-Post my original so it's kinda kewl with an entry point starting with dillo. I think that's pretty awesome, and it quotes the original (part I if you will) that starts with Vivaldi.

I don't usually ask, but especially with respect to this HowTo/Tutorial, the more people that boost it, the further it will reach, and the more people it can benefit. Give it a gander and if you think others will find portions of it advantageous... well, feel free to boost it.

So without further ado, Here's the link to the Linux Browser HowTo

I hope you find it useful, and Enjoy! 🤗

#tallship #FOSS #Fediverse #Browsers #dillo #Microsoft_Edge #Firefox #Vivaldi #Brave_Browser #DuckDuckGo #Chromium #Opera #Chawan #Lagrange #Tor #Lynx #Elinks #Links #Nyxt #Epiphany #Falkon #Konqueror

⛵

@dillo

Apologies! No sooner had I published, I realized that #Dillo, which was actually on the list, wasn't included in my tut.... Grrrrr!

So, this particular article wasn't published with the intention of being as ephemeral as a regular, standard #FediPost, but rather, as a cookbook style #HowTo to update occasionally and keeping it rather current.

I'm also considering expanding it with sections for other #Unices & Distros, with each one of the #browsers included again, but in the section for the particular #OS - whether it be #OpenBSD, #Slackware, Etc., and I've been doing a little work on that already.

Anyway, it's almost inconceivable that I published w/o Dillo. I was very tired when I did, and I recall thinking about Dillo when I writing up #Lagrange, since I've always believed that it's a sin to remove such tiny amounts of code to accommodate (Yes I'm talking to you Mozilla!) Gopher:// ftp://, Etc.; and for the more forward thinking folks, extending similar support for gemini:// and arguably others spawned from it that I didn't personally work with since the very beginning like I did with #Gemini, back at #SDF).

But I digress, and I'll get to the point.

Here is the update of my Linux Browser HowTo, Which includes dillo*. It was much too long to include by just appending to the original article by about 5000 characters,lolz, so I took the easy way out - I quote-posted it, lolz

That also implies that I'll have to swap hats a couple of times because some forums forced me to completely rewrite it to support #BBCode, and although the original looks nice in HIVE and on Dev, the Markdown is completely obliterated on Nostr (no graceful degradation there folks) - which I left as is because I think people need to see what not supporting Markdown looks like. I think it looks like shit on masto too, but masto isn't the #Fediverse, and it looks great on most other Fediverse platforms :)

I was getting tired again, but rushing to publish, so I know I misspelled various incarnations of privilege at least 3 different ways, and no, I'm not going to clean that up :p What I think I'm going to have to do though, Is publish the next volume on a proper website with some ActivityPub powered capabilities like WordPress, or Ghost, or WriteFreely / write.as, where I don't have to worry about the length of the article and I can continue to break it into pieces or chapters, etc., as it grows. There's other OSes and Linux distros I'd like to cover, but as you can see at the end, Slackware is going to be rather boring, considering how simple it is to install everything under the sun from source - and that is indeed a beautiful thing.

I hope what I've done today facilitates more people having access to dillo, since it's a good product, but seemingly out of reach for many n00bs, when it really doesn't need to be. Sure, setting up a Debian style repo with keys, etc., at Dillo-Browser.org would be ideal, but this is, after all, FOSS, and you've done so much already, maybe I can lend a hand at that at some point in the future, but....

Truth be told, there really isn't anything much simpler than doing a git clone to perform the initial installation, and simply performing a git pull, followed by the same build sequence later to affect any updates.

You have a wonderful day, and I hope I've helped bring some awareness and hopefully adoption by others of dillo, it really is deserving of that, much moreso than Microsoft Edge, which I also included in my HowTo (but mostly as a disparaging joke).

Kindest regards,

Bradley

#tallship #tut #HowTo #Browser_HowTo #dillo #FOSS

⛵

And now for dillo

## dillo browser (the honorable mention):

Now, this tutorial wouldn't be complete without one of the most determined browser projects of all to be included. Unfortunately for the user (and by user I mean the common, everyday n00b, joeuser), very little effort has been put into a one & done download/install procedure.

To be honest, dillo is a bit of a pain in the butt, because even though a lot of effort has been put into rescue of the intellectual property after the main author of the engine passed away and the original domain registration expired (to be picked up by a cybersquatter), rebuilding the forward facing public assets still leaves much to be desired for a simple joeuser - the folks we are all trying to ultimately serve and make things simple.

For example, Where you would almost universally expect to see a "Download dillo" link or button, you will indeed find a link, but it leads to their cgit repo. Even junior devs cringe when they first come across cgit, even though it really is arguably far superior to GitHub style facilities like Gitea, Forgejo (Codeberg), and SourceHut.

Although it's really only a matter of appearance, cgit was written by Jason A. Donenfeld, who also created Wireguard and Pass - the standard UNIX password manager, popular on Androids too (via F-Droid, requires installing OpenKeyChain too on Android).

But back to #dillo! You may be wondering why I placed it so far down the list, and the reason is twofold:

1. ) I brainfarted. Yup, I was really tired and literally forgot when initially publishing this first edition of the Browsers on Linux HowTo, and for that, especially to the dillo dev team, I apologize.
2. ) It may seem a bit complicated - but I assure you it is not, especially when compared to the #Tor_Browser, which immediately precedes the instructions for installing dillo.

I know that a lot of folks went through and endured the process of installing the Tor Browser, because it's such a popular utility in today's world, and since I'm figuring that you got through that okay, we can now turn our attention to dillo, without all of the hunting around on various git repo servers out there and web pages - just the bare bones simple cut and paste for you here...

So let's get to it, shall we?

NOTE: You should know by now that commands prefaced with ~$ are to be administered by you, the regular, unpriviliged user account; while commands prefaced with ~# mean that those commands are issued by "root". You have a choice in your terminal. The first is just to prepend the root commands with sudo, while the other option is to issue su - to root, then go into the directory the user was in and issue those commands. You may find it easier to just open a fresh tab in your terminal app so you have one user ($) shell and then in the other tab or window you have the root user's (#) shell.

The first thing we need to do is make sure that we have resolved all dependencies (prerequisites) for compiling dillo. We do that as root (or via sudo as I just mentioned above) like so:

~# apt install gcc g++ git git-all autoconf automake make zlib1g-dev libfltk1.3-dev libssl-dev libc6-dev libpng-dev libjpeg-dev libwebp-dev libbrotli-dev

Don't worry if some, or even most or all of those packages aren't installed, because some, many, or all of them may already be installed on your system, and invoking the install won't overwrite anything already installed.

Next, let's git (pundit there), er... get the source for dillo, and yes, we're going to use git. A mention now that doing it this way means that in the future your updates will be relatively simple and brainless. More on that later. We'll start by creating a directory (folder) to work from, a place where you can use in the future that doesn't clutter up your home directory with needless entries; then we'll download the source code, build it locally, and install it...

All you have to do is cut and paste each line, one by one, and wait for each step to finish before pasting the next line into your terminal.

~$ cd; mkdir -pv dev; cd dev
~$ git clone https://git.dillo-browser.org/dillo
~$ cd dillo
~$ ./autogen.sh
~$ mkdir build
~$ cd build
~$ ../configure --prefix=/usr/local
~$ make
~$ sudo make install
root@mylaptop:/home/joeuser/dev/dillo/build# make install

That's it! dillo has been installed!

Now, and because we're at the very end. I want to explain the $ and # stuff so it's clear. Notice that the dillo installation steps is the only place in this HowTo that I included a sudo command. The reason is that I believe that in most cases, sudo is a bad way to administer a machine. In classic, traditional UNIX administration, you su to root (the Superuser), do what you need to with thos elevated privs and then exit out of the root shell and back to your unprivileged user account.

So ~# is merely a shorthand in most Bash shells. typically, you're going to see something like username@hostname:/path/to/directory$ for a non-priviliged user, or for root, it will generally read as root@hostname:/path/to/directory#

Generally speaking when you issue a command from a particular directory as a non-privileged user, followed by a command by the superuser (root), you probably want to be in that same directory. So the final command above which was make install, would have been performed by the non-privileged user ($) using the sudo utility (or, doas on some OSes) or as root - but as root, you would have wanted to be in that same directory to run the make command to install the compiled binary in /usr/local on your machine. This is what it would look like had you decided (I recommend this practice in most cases) to 'su -' to root instead of using sudo:

joeuser@mylaptop:~/dev/dillo/build$ su - 
root@mylaptop:~# cd /home/joeuser/dev/dillo/build
root@mylaptop:/home/joeuser/dev/dillo/build# make install
root@mylaptop:/home/joeuser/dev/dillo/build# exit
joeuser@mylaptop:~/dev/dillo/build$ cd
joeuser@mylaptop:~$ which dillo
/usr/local/bin/dillo
joeuser@mylaptop:~$ dillo &

If you followed along with that last block of code, you'll see that we asked where our program (dillo) is, by using the which command. It told us that it's located /user/local/bin/dillo, in our default "path", so all we need to do (from anywhere) is just type in dillo & - the ampersand will release our shell so the process can run in the background. Just hit your "return" or "enter" key and you'll get your prompt back.

Have fun running dillo!

Well, I went into a lot of explantions that normally aren't covered, because basic navigation and what your prompts are going to look like are just assumed in most HowTo's and Tutorials, including mine. But it should be covered somewhere and this was a logical place.

There is just one more (optional) task to complete. Adding dillo to your menu panel - I'm going to leave that task up to you, it's worth learning, and honestly, I don't want to have to cover how to do this in KDE Plasma, Xfce, GNOME, Cinnamon, Mate, etc.... you get the idea; I have no idea what desktop environment you're running but it's an excercise that is worthwhile so you can configure your menus and desktop anyway, so do give it a go :)

There's really just one last thing folks....

Here's just a taste of what to expect with future updates to this HowTO:

~# sqg -p dillo && sbopkg -i dillo.sqf

"What?" You say? Yup! That's Slackware. Installing pretty much every single Browser in this article is as simple as doing a copypasta of that one liner with sbopkg...

But you'll have to wait for all of that funstuff :p

And remember: You can haz #Cheezburgerz! 🍔🍟

I hope that helps!

#tallship #FOSS #browsers #dillo #Microsoft_Edge #Firefox #Vivaldi #Brave_Browser #DuckDuckGo #Chromium #Opera #Chawan #Lagrange #Tor #Lynx #Elinks #Links #Nyxt #Epiphany #Falcon #Konqueror

⛵

RE: https://public.mitra.social/objects/019f49aa-b5c6-7372-b92d-68821dcad285

Sadly, the SVG library Nanosvg is now slop.

We embed a sane version in #Dillo to read Wikipedia math which will be kept LLM-free. Human-made changes will continue to be cherry-picked from upstream.

Sadly, the SVG library Nanosvg is now slop.

We embed a sane version in #Dillo to read Wikipedia math which will be kept LLM-free. Human-made changes will continue to be cherry-picked from upstream.

@jp @hyde

#Thunderbird's "Basic HTML" mode is honestly kinda nice. :D

Also #ClawsMail has (IIRC) #Dillo baked-in for a very basic HTML viewer.

@jp @hyde

#Thunderbird's "Basic HTML" mode is honestly kinda nice. :D

Also #ClawsMail has (IIRC) #Dillo baked-in for a very basic HTML viewer.

Tried Dillo out on my website and it mostly works, except for the navigation bar's fancy dropdown CSS and since it uses no JS, the Mario and Luigi images didn't move around but were stuck on the page so I need to add some JS to show them so they're hidden by default. My website had some HTML issues reported too, so hopefully I can track them down in the Jekyll theme I use. Dillo is really fast, surprisingly faster than Firefox even when not needing JS.

#Dillo #DilloBrowser

Tried Dillo out on my website and it mostly works, except for the navigation bar's fancy dropdown CSS and since it uses no JS, the Mario and Luigi images didn't move around but were stuck on the page so I need to add some JS to show them so they're hidden by default. My website had some HTML issues reported too, so hopefully I can track them down in the Jekyll theme I use. Dillo is really fast, surprisingly faster than Firefox even when not needing JS.

#Dillo #DilloBrowser

@piero @gumnos @dillo So in theory #Dillo could be embedded in, say, #Emacs, though I reckon it's less attractive for most users to swap EWW for Dillo instead of a more modern engine...
#Nyxt browser could then use it too, alas Nyxt doesn't even compile yet on OpenBSD...

You and me both my internet friend; I've built quite a few interesting sites using pure HTML which have run for years with very little maintenance, due to their almost static nature

@rl_dane

#Firefox #CPU #usage #Dillo #HTML #pure #nostalgia #browser #light #sh #bash

You and me both my internet friend; I've built quite a few interesting sites using pure HTML which have run for years with very little maintenance, due to their almost static nature

@rl_dane

#Firefox #CPU #usage #Dillo #HTML #pure #nostalgia #browser #light #sh #bash

The mistake you maybe making is that you consider Firefox to be a browser.

Firefox has stopped being a browser decades ago

A browser doesn't need hundreds and hundreds of Engineers to be maintained, a massive project with multiple use angles and cases does

Firefox does so many (bad) things you can almost consider it a mini operating system

A alpha level Operating System, riddled with security bugs

It's always fantastic to be able to go somewhere in dillo and just have fun, amazing yourself with a speed that pages load

@rl_dane

#Firefox #CPU #usage #Dillo #browser #light #sh #bash

The mistake you maybe making is that you consider Firefox to be a browser.

Firefox has stopped being a browser decades ago

A browser doesn't need hundreds and hundreds of Engineers to be maintained, a massive project with multiple use angles and cases does

Firefox does so many (bad) things you can almost consider it a mini operating system

A alpha level Operating System, riddled with security bugs

It's always fantastic to be able to go somewhere in dillo and just have fun, amazing yourself with a speed that pages load

@rl_dane

#Firefox #CPU #usage #Dillo #browser #light #sh #bash

• Open a website in firefox (a simple one, even)
• Hear the fans spinning up
• Copy url
• Close firefox
• Open #Dillo
• Paste url
• Read the same content, CPU is idle
• It ain't much, but it's honest work.jpeg

• Open a website in firefox (a simple one, even)
• Hear the fans spinning up
• Copy url
• Close firefox
• Open #Dillo
• Paste url
• Read the same content, CPU is idle
• It ain't much, but it's honest work.jpeg

Nouvelle petite fonctionnalité dans la version 3.3.0 de développement de #VenC qui m'a permit d'ajouter des correctifs dans la galerie principale de mon site, pour une meilleur compatibilité avec #dillo.

Les éléments qui déclenchaient l'affichage d'un carrousel renvoie maintenant vers une page statique avec tous les éléments multimédia qui auraient du apparaître dans le carrousel en Javascript.

#accessibilite #lowtech

Nouvelle petite fonctionnalité dans la version 3.3.0 de développement de #VenC qui m'a permit d'ajouter des correctifs dans la galerie principale de mon site, pour une meilleur compatibilité avec #dillo.

Les éléments qui déclenchaient l'affichage d'un carrousel renvoie maintenant vers une page statique avec tous les éléments multimédia qui auraient du apparaître dans le carrousel en Javascript.

#accessibilite #lowtech

I have prepared a directory of sites that work well with #Dillo with a focus on human crafted sites to help new users find useful content:

https://dir.dillo-browser.org/

There is A LOT of content to explore, so be mindful of the time when entering the rabbit hole.

You can also suggest new sites to be added at the end of the page.

I have prepared a directory of sites that work well with #Dillo with a focus on human crafted sites to help new users find useful content:

https://dir.dillo-browser.org/

There is A LOT of content to explore, so be mindful of the time when entering the rabbit hole.

You can also suggest new sites to be added at the end of the page.

#Surf l'UI est inexistante mais ça peut faire le job, je suis 145Mo de mémoire donc bof.

#Servo le rendu est plutot propre mais il manque des images. Niveau mémoire on est sur 900Mo pour une seule page donc c'est pas encore au point.

Conclusion je dirais soit #Dillo soit #NetSurf ou alors peut-être #Firefox sans Javascript

cc @IhoaNn

#Surf l'UI est inexistante mais ça peut faire le job, je suis 145Mo de mémoire donc bof.

#Servo le rendu est plutot propre mais il manque des images. Niveau mémoire on est sur 900Mo pour une seule page donc c'est pas encore au point.

Conclusion je dirais soit #Dillo soit #NetSurf ou alors peut-être #Firefox sans Javascript

cc @IhoaNn

Résultat de test de navigateurs web

#Dillo ça marche par contre pas de javascript et le css n'est pas supporté pleinement, même Wikipedia est difficilement utilisable car plein de boutons sont cassés. Avantage très léger donc va marcher sur des petites config sans problèmes. Je suis en dessous 1Mo de mémoire vive utilisé.

#Konqueror fonctionne parfaitement page tests 100% affiché correctement, mais pas du tout léger j'étais à > 400Mo de mémoire utilisé pour affiché une page.

cc @IhoaNn

Résultat de test de navigateurs web

#Dillo ça marche par contre pas de javascript et le css n'est pas supporté pleinement, même Wikipedia est difficilement utilisable car plein de boutons sont cassés. Avantage très léger donc va marcher sur des petites config sans problèmes. Je suis en dessous 1Mo de mémoire vive utilisé.

#Konqueror fonctionne parfaitement page tests 100% affiché correctement, mais pas du tout léger j'étais à > 400Mo de mémoire utilisé pour affiché une page.

cc @IhoaNn

@IhoaNn mmh j'ai #Dillo https://dillo-browser.org/ mais bon le support de certain site web va être très limité

@IhoaNn mmh j'ai #Dillo https://dillo-browser.org/ mais bon le support de certain site web va être très limité

J'arrête pas de rager en ce moment comme un énorme connard alors voilà une toute petite bonne nouvelle:

Dans un effort de contribution à un web plus accessible et #lowtech 🤡 j'ai corrigé quelques bugs de rendu sur mon blog qui ne s'affichait pas bien avec le navigateur #dillo

Certaines modifications ont été intégré à la prochaine version de #VenC vu que ça a mit en évidence que mon générateur de site n'aide pas toujours à mettre en oeuvre un site clean ...

J'arrête pas de rager en ce moment comme un énorme connard alors voilà une toute petite bonne nouvelle:

Dans un effort de contribution à un web plus accessible et #lowtech 🤡 j'ai corrigé quelques bugs de rendu sur mon blog qui ne s'affichait pas bien avec le navigateur #dillo

Certaines modifications ont été intégré à la prochaine version de #VenC vu que ça a mit en évidence que mon générateur de site n'aide pas toujours à mettre en oeuvre un site clean ...

War, climate among high priority topics at Davos meeting

#comic #unix_surrealism #linux #art #mastoart #computers #bash #dillo #lgbt #content_review

War, climate among high priority topics at Davos meeting

#comic #unix_surrealism #linux #art #mastoart #computers #bash #dillo #lgbt #content_review

@wyatt

Interesting, it appears for a second, and then gives me a 404 in firefox.

#Dillo can read it fine. XD

@wyatt

Interesting, it appears for a second, and then gives me a 404 in firefox.

#Dillo can read it fine. XD

Nachdem ich es endlich geschafft hatte, den lästigen #PGP Fehler bei jedem #Librewolf Update abzustellen, geht das jetzt wieder los.

Überlegte, zum #Zen-Browser zu wechseln, doch dafür soll ich ein veraltetes #ffmpeg installieren. Kommt nicht infrage.

Geht es also zurück zu #Vivaldi … ups, seit der Neuinstallation noch gar nicht wieder installiert. Dann erst mal schauen, wie die zum #KI-Müll stehen.

#Dillo #Dooble und #qutebrowser sind ja feine Werkzeuge, die immer mal wieder zum Einsatz kommen. Aber für den täglichen Gebrauch kann ich nicht auf die Informationen verzichten, die mir #uBlock und #uMatrix liefern.

(Und wenn mir jetzt Brave vorgeschlagen wird: MIT SICHERHEIT NIEMALS!)

@moses_izumi

lol that's some vintage 2000s cluelessness!!

XLinks could be my favorite web browser if only it had configurable keybinds.

Its movement keys make no sense at all. XD

Chawan has become my default, with Firefox + Vimium C as a backup. #Dillo still has a special place in my heart. ;)