#epiphany — Public Fediverse posts on home.social

צבי הנינג'ה عزيز النينجا @[email protected] · 2026-08-05 · 14:48 UTC

#Epiphany

"The Guaranteed Eternal Sanctuary Man" fits the #ai / #llm bit of our timeline so nicely :marx_thinking:

Am I the first to notice this?

https://www.youtube.com/watch?v=e4HfFwVy-h0&t=234s

#epiphany #ai #llm

צבי הנינג'ה عزيز النينجا @[email protected] · 2026-08-05 · 14:48 UTC

#Epiphany

"The Guaranteed Eternal Sanctuary Man" fits the #ai / #llm bit of our timeline so nicely :marx_thinking:

Am I the first to notice this?

https://www.youtube.com/watch?v=e4HfFwVy-h0&t=234s

#llm #epiphany #ai

N-gated Hacker News @[email protected] · 2026-08-04 · 08:12 UTC

🎨✨ "The unknown hero of your backyard" 🏡: Yet another attempt by a wannabe #influencer to transform everyday mundanity into a profound #epiphany. Meet #Viktor, the guy you definitely haven't heard of, and probably won't remember after this article 🙄📚.
https://worksinprogress.co/issue/beauty-in-my-backyard/ #unknownhero #backyard #mundane #HackerNews #ngated

#influencer #epiphany #viktor #unknownhero #backyard #mundane

N-gated Hacker News @[email protected] · 2026-08-04 · 08:12 UTC

🎨✨ "The unknown hero of your backyard" 🏡: Yet another attempt by a wannabe #influencer to transform everyday mundanity into a profound #epiphany. Meet #Viktor, the guy you definitely haven't heard of, and probably won't remember after this article 🙄📚.
https://worksinprogress.co/issue/beauty-in-my-backyard/ #unknownhero #backyard #mundane #HackerNews #ngated

#influencer #epiphany #viktor #unknownhero #backyard #mundane

tallship @[email protected] · 2026-07-27 · 02:22 UTC

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

⛵

#foss #fediverse #tallship #browsers #dillo #microsoft_edge

tallship @[email protected] · 2026-07-27 · 02:22 UTC

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

⛵

#foss #fediverse #tallship #browsers #dillo #microsoft_edge

tallship @[email protected] · 2026-07-27 · 00:53 UTC

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

#foss #tallship #tor #firefox #cheezburgerz #browsers

Jeff Fortin T. (風の庭園のNekohayo) @[email protected] · 2026-07-24 · 07:43 UTC

Filed three UX performance bugs in Epiphany's browsing "History" dialog. I believe they could all be fixed by newcomers:

* https://gitlab.gnome.org/GNOME/epiphany/-/work_items/2907
* https://gitlab.gnome.org/GNOME/epiphany/-/work_items/2906
* https://gitlab.gnome.org/GNOME/epiphany/-/work_items/2905

#GNOMEWeb #Epiphany #GNOME #performance #UX #browsers

#gnomeweb #epiphany #gnome #performance #ux #browsers

Jeff Fortin T. (風の庭園のNekohayo) @[email protected] · 2026-07-24 · 07:43 UTC

Filed three UX performance bugs in Epiphany's browsing "History" dialog. I believe they could all be fixed by newcomers:

* https://gitlab.gnome.org/GNOME/epiphany/-/work_items/2907
* https://gitlab.gnome.org/GNOME/epiphany/-/work_items/2906
* https://gitlab.gnome.org/GNOME/epiphany/-/work_items/2905

#GNOMEWeb #Epiphany #GNOME #performance #UX #browsers

#gnomeweb #epiphany #gnome #performance #ux #browsers

Jeff Fortin T. (風の庭園のNekohayo) @[email protected] · 2026-07-16 · 15:57 UTC

It seems I have found a sneaky memory leak that occurs when you reload webpages with @WebKitGTK: https://bugs.webkit.org/show_bug.cgi?id=319590

That might explain why I kept running out of RAM way too easily when using Epiphany with a dozen tabs or so.

I suspect fixing this should significantly improve Epiphany's survivability in the wild, as well as long-running GTK apps that embed a webview (like email clients) :blobcat:

#performance #profiling #Linux #GNOMEWeb #Epiphany #WebKitGTK #WebKit #GNOME #Skia #HarfBuzz

#performance #profiling #linux #gnomeweb #epiphany #webkitgtk

Jeff Fortin T. (風の庭園のNekohayo) @[email protected] · 2026-07-16 · 15:57 UTC

It seems I have found a sneaky memory leak that occurs when you reload webpages with @WebKitGTK: https://bugs.webkit.org/show_bug.cgi?id=319590

That might explain why I kept running out of RAM way too easily when using Epiphany with a dozen tabs or so.

I suspect fixing this should significantly improve Epiphany's survivability in the wild, as well as long-running GTK apps that embed a webview (like email clients) :blobcat:

#performance #profiling #Linux #GNOMEWeb #Epiphany #WebKitGTK #WebKit #GNOME #Skia #HarfBuzz

#performance #profiling #linux #gnomeweb #epiphany #webkitgtk

tallship @[email protected] · 2026-07-10 · 01:35 UTC

HowTo: INSTALLING Browsers in Linux

Here we're going to cover the installation steps of Browsers in Linux - specifically, Debian GNU/Linux.

We're covering the procedural steps for this in Debian Testing (Forkey), which is already beginning the gleanings of what will become Debian 14. At the time of writing,the current kernel version is 7.0.13+deb14-amd64.

Daily drivers will likely be along the lines of Vivaldi, Firefox, Lagrange, and Brave Browser, and in no particular order. Any others will be mostly for particular reasons like, testing, curiosity, Etc., but some specialized products like the Tor browser, which focus on privacy are also covered. This list is by no means complete, but there's a bunch of them we cover, so let's jump right in!

I can haz #Cheezburgerz? 🍔 🍟

Well, let's see... First up is the first rate and fully featured Vivaldi, built on top of the open source Chromium, as are so many others in this list.

- Vivaldi

Manual setup of the Vivaldi Linux repos - According to their website, "you no longer need to do this. After downloading a Linux package and installing it our Linux update repositories will be configured automatically for you to receive updates."

That's awfully nice, so visit the download page above and get the .deb package:

~# mkdir -pv /usr/local/packages/vivaldi; cd /usr/local/packages/vivaldi
~# wget https://downloads.vivaldi.com/stable/vivaldi-stable_8.1.4087.48-1_amd64.deb
~# apt install ./vivaldi*.deb

- That's it! You're ready to go now.

Next up...

- Firefox
~# apt update && apt install firefox
- Brave Browser

~# apt install curl
~# curl -fsSLo /usr/share/keyrings/brave-browser-archive-keyring.gpg https://brave-browser-apt-release.s3.brave.com/brave-browser-archive-keyring.gpg
~# curl -fsSLo /etc/apt/sources.list.d/brave-browser-release.sources https://brave-browser-apt-release.s3.brave.com/brave-browser.sources
~# apt update && apt install brave-browser

- DuckDuckGo (on Android - There's no Linux port)
- Edge (For the sake of completeness in testing? For the love of God, WHY???)

~# mkdir -pv /usr/local/packages/edge; cd /usr/local/packages/edge # download Edge from the link above into this directory
~# apt install -y ./microsoft-edge-stable_147.0.3912.98-1_amd64.deb # or whatever version you downloaded.

- Lagrange

~$ apt update && apt install flatpak
~$ flatpak install flathub fi.skyjake.Lagrange

- Chromium

~# apt update && apt install chromium

- Opera

~# mkdir -pv /usr/local/packages/opera; cd /usr/local/packages/opera # Download from the link above, for example:
~# wget https://download3.operacdn.com/ftp/pub/opera/desktop/131.0.5877.5/linux/opera-stable_131.0.5877.5_amd64.deb
~# apt install -y ./opera-stable_131.0.5877.5_amd64.deb

Good Ole Lynx, Elinks, and Links. One should not be without at least a couple of these. you can surf HTTP, Gopher, and remain in a character based environment with Lynx, so the utility of testing is available quickly at your fingertips. Also included w3m.

~# apt install -y elinks elinks-data elinks-doc links links2 lynx lynx-common w3m w3m-img

Nyxt: For a more elegant take on the mostly character/CLI based options above you might wish to have this browser in your toolchest. Installing is simple as a FlatPak.

~$ flatpak install flathub engineer.atlas.Nyxt

GNOME Web - aka: Epiphany. Yes, this is the decendent of Galeon, the legacy of which began in 2000. Much of Galeons features were ported to Epiphany, which for whatever reason, is having an existential moment with respect to its name - Officially? It's now GNOME Web, but everywhere it says that, they also include the Epiphany name just so there's no confusion. Huh?

~# apt install epiphany-browser epiphany-browser-data

If you must call it "Web", that's fine, but even if you want to install it as a FlatPak you're going to be invoking Ephiphany, and that's what everyone still calls it anyway:

~$ flatpak install flathub org.gnome.Epiphany

Falkon. Formerly QupZilla, this browser received its new name in 2017 when it was picked up by KDE. With a simple, but modern, themable interface affording the user options resembling that of Firefox, Chrome, Windows, and Mac, it also comes bundled with AdBlock installed and enabled. There are several other features and extensions available including a PDF reader, GreaseMonkey,Tab extensions, Etc., which are available via the KDE store rather than Chrome or Firefox add-on marketplace.

~# apt install falkon

You can also install via Flathub:

~$ flatpak install flathub org.kde.falkon

Konqueror - The longtime File and Web Browser by KDE. It's probably already installed by default if you're running KDE, but if not here you go:

~# apt install konqueror konqueror-data konqueror-doc libkf6konq7 libkf6konqsettings7

And now for something truly special...

Chawan

~# mkdir -pv /usr/local/packages/chawan; cd /usr/local/packages/chawan
~# wget https://git.sr.ht/~bptato/chawan/refs/download/v0.3.3/chawan-0-3-3-amd64.deb
~# apt update && apt install ./chawan-0-3-3-amd64.deb

Alternatively:

~# mkdir -pv /usr/local/src/chawan; cd /usr/local/src/chawan
/usr/local/src/chawan# wget https://git.sr.ht/~bptato/chawan/refs/download/v0.3.3/chawan-0-3-3-linux-amd64.tar.xz
/usr/local/src/chawan# tar xvf chawan-0-3-3-linux-amd64.tar.xz
/usr/local/src/chawan# cd chawan-0-3-3-linux-amd64/
/usr/local/src/chawan/chawan-0-3-3-linux-amd64# make install

you can start with ~$ mancha cha

DESCRIPTION

Chawan is a text-mode browser. It can be used as a pager, or as a
web/(S)FTP/gopher/gemini/file browser. It understands HTML and CSS, and
when enabled by the user, can also execute JavaScript and display images
(on terminals supporting Sixel or the Kitty image protocol.)

   Chawan can also be used as a general text-based document viewer  as  de‐
   scribed  in  cha-mailcap(5),  or  as a hyperlinked man page viewer using
   mancha(1).

## TorBrowser

This one's a bit more of a chunk to bite into, only because if you're going to endeavor for such security, then you want to make sure to cross all the t's and dot all of the i's.

Import the Tor Browser Developers signing key

(0xEF6E286DDA85EA2A4BA7DE684E2C6E8793298290)

gpg --auto-key-locate nodefault,wkd --locate-keys [email protected]

Your output should look something like:

gpg: key 4E2C6E8793298290: public key "Tor Browser Developers (signing key) <[email protected]>" imported
gpg: Total number processed: 1
gpg:               imported: 1
      EF6E286DDA85EA2A4BA7DE684E2C6E8793298290
uid           [ unknown] Tor Browser Developers (signing key) <[email protected]>

Now that you've imported the key, you can save it to a file, identifying it by the fingerprint above:

~$ mkdir -pv ~/packages/tor; cd ~/packages/tor
~/packages/tor$ gpg --output ./tor.keyring --export 0xEF6E286DDA85EA2A4BA7DE684E2C6E8793298290

From the Tor Project's download page HERE, download the .asc OpenPGP signature file and the TorBrowser package tarball:

~/packages/tor$ wget https://www.torproject.org/dist/torbrowser/15.0.11/tor-browser-linux-x86_64-15.0.11.tar.xz.asc

~/packages/tor$ wget https://www.torproject.org/dist/torbrowser/15.0.11/tor-browser-linux-x86_64-15.0.11.tar.xz

NOTE: At the time of writing, these were the current files downloaded, the filenames will almost certainly have changed by the time you download them, so the tarball and signature file will have different names - adjust accordingly. We'll continue using those filenames below.

Now we verify the veracity of the package's tarball using the .asc signature file like so:

~/packages/tor$ gpgv --keyring ./tor.keyring ~/packages/tor/tor-browser-linux-x86_64-15.0.11.tar.xz.asc ~/packages/tor/tor-browser-linux-x86_64-15.0.11.tar.xz

Your output should confirm a "Good signature":

gpgv: Signature made Tue 28 Apr 2026 02:01:23 AM PDT
gpgv:                using RSA key CAAE408AEBE2288E96FC5D5E157432CF78A65729
gpgv: Good signature from "Tor Browser Developers (signing key) <[email protected]>"

Now we explode the archive:

~/packages/tor$ tar xvf tor-browser-linux-x86_64-15.0.11.tar.xz

Let's give it a go, shall we?

~/packages/tor$ cd tor-browser
~/packages/tor/tor-browser$ ./start-tor-browser.desktop --register-app
Tor Browser has been registered as a desktop app for this user in ~/.local/share/applications/

You'll notice that the permissions of ./start-tor-browser.desktop are set to 700 - It has only been installed for you and you alone. I would recommend that everyone install their own but if that seemed like too much hassle for you to begin with, we can just install it system-wide for everyone, with the following two commands:

~# apt update
~# apt install -y torbrowser-launcher

## Summary, and why

I know I know, I always seem to put the tl;dr's at the very end, but that's only because it humors me :p In this case, however, it really is best if the Tor Browser is installed individually for each and every user account that is going to use it.

Why do I usually put the tl;dr's at the very end of my articles? Because I've observed that the impatient among us are inclined to break something anyway for lack of patience and understanding, and if you really think about it, we've learned a lot today, going over each step and most of the time, why we did it that way.

Even so, when you get to the end there's this nice fluffy and quick way to accomplish your task quickly, and you can do it a hundred times now because you understand the whole thing. On the other hand, the people who just want the tl;dr are typically one of two types of folks - they've got a great handle on things and only need just bare syntax, or.... they're the kind of folks who, when assigned a book to read, start by reading the last couple of pages, then think they're ready for the book report.

For that last group of people, isn't putting the tl;dr at the very end where they really expect to find it anyway?

## Parting Thoughts

Not all of the products that we've covered the installation for today are FOSS. Many aren't even Open Source. We're trying to be complete with all of the various applications in the browser spectrum that people may wish to use - for even the most obscure above, tens of thousands of people use it as their daily driver, or as a particular tool for a job that they perform every day.

I'm going to explain why I decided to include one browser in particular. Years ago...

Microsoft's current version for Windows Internet Exploder was either 3.01b or 3.02b at the time, and this was the only time that I've ever seen this - so I actually have a copy of this browser. In my wanderings across this planet I've seen people complain over the years about there not being any Internet Explorer for Linux, and indeed, this is the case. In fact, in my experience, I've never seen a port of Internet Explorer for any of the Unices (Apple products excepted), until one day when I was installing a Sun Enterprise server running Solaris. I just happened to notice when looking through the files that I saw the rarest of all creatures...

A lone Internet Exploder, version 3.02b (or maybe 3.01b) for Solaris! For Solaris? Why? No, not really why? but given the proof that they could have a port for Linux at anytime and haven't, yet they cozy up to Sun Microsystems and offer a port of Explorer that is supported on Solaris. WoW!

I quickly fell into a state of perplexity. Why Solaris and no one else? Why not Linux? Why not AIX or HP-UX? Why bother at all if they're not going to make it available for Linux and the BSDs too, and I thought long and hard about this.

I still do, and I have a lot of answers. None of which are truly acceptable. Yes, Ballmer called Linux a cancer, now they hug it like a redwood tree. But think of what could have been.

So... Why did I include Microsoft Edge here in this article?

I was being charitable, as I continue looking down my nose at Redmond, dismissively, disparagingly, with just a tinge of a smile containing just a hint of my condescension.

I'll probably continue to add a browser package here and there to this article when I feel it's warranted. There are a lot, and this only covers the most popular and it was good to get these out of the way so perhaps I can tend to the more obscure or peculiar at some other point in time.

I hope that helps!

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

⛵

#foss #privacy #tallship #tor #firefox #cheezburgerz

N-gated Hacker News @[email protected] · 2026-06-18 · 21:26 UTC

Ah, yes, the mind-blowing #epiphany that #weightlifting requires actual weights 🏋️‍♂️. Next, they'll reveal that running involves legs! 🙄 A groundbreaking exposé on the mysteries of the #gym. 🤔
https://www.intheweights.com/ #humor #fitness #workout #HackerNews #ngated

#epiphany #weightlifting #gym #humor #fitness #workout

N-gated Hacker News @[email protected] · 2026-06-18 · 21:26 UTC

Ah, yes, the mind-blowing #epiphany that #weightlifting requires actual weights 🏋️‍♂️. Next, they'll reveal that running involves legs! 🙄 A groundbreaking exposé on the mysteries of the #gym. 🤔
https://www.intheweights.com/ #humor #fitness #workout #HackerNews #ngated

#epiphany #weightlifting #gym #humor #fitness #workout

Pirate Praveen 普拉文 @[email protected] · 2026-06-17 · 11:44 UTC

@goku12 I use gnome web on my laptop.

Some websites have issues sometimes, like mouse cursor position is not where it is shown or it needs a restart after keeping it open for a long time, misses plugins like pass.

But I still use it as my primary browser. I hope these gets solved eventually.

This is backed by #Apple, but they don't have as much power on the web as #Google.

#epiphany #gnomeweb

#apple #google #epiphany #gnomeweb

Pirate Praveen 普拉文 @[email protected] · 2026-06-17 · 11:44 UTC

@goku12 I use gnome web on my laptop.

Some websites have issues sometimes, like mouse cursor position is not where it is shown or it needs a restart after keeping it open for a long time, misses plugins like pass.

But I still use it as my primary browser. I hope these gets solved eventually.

This is backed by #Apple, but they don't have as much power on the web as #Google.

#epiphany #gnomeweb

#apple #google #epiphany #gnomeweb

in ♥️ with PDA (and 🐧) @[email protected] · 2026-05-28 · 20:01 UTC

going to use #epiphany again as the main browser. Does its job. Therefor playing around with my html speeddial and darkmode

#epiphany

in ♥️ with PDA (and 🐧) @[email protected] · 2026-05-28 · 20:01 UTC

going to use #epiphany again as the main browser. Does its job. Therefor playing around with my html speeddial and darkmode

#epiphany

צבי הנינג'ה عزيز النينجا @[email protected] · 2026-05-28 · 07:59 UTC

RE: https://mas.to/@carnage4life/116648220947842312

I just had an #epiphany: The #ai #slop is like cockoo girl in #sandman, tearing the realm of dreams apart :marx_thinking:

#epiphany #ai #slop #sandman

צבי הנינג'ה عزيز النينجا @[email protected] · 2026-05-28 · 07:59 UTC

RE: https://mas.to/@carnage4life/116648220947842312

I just had an #epiphany: The #ai #slop is like cockoo girl in #sandman, tearing the realm of dreams apart :marx_thinking:

#epiphany #ai #slop #sandman

Jeff Fortin T. (風の庭園のNekohayo) @[email protected] · 2026-05-20 · 00:27 UTC

For a long time I've been intrigued by #Epiphany taking 3 to 20 seconds to load most websites on startup or in Incognito Mode.

Today I tested a bunch of configurations to report a bug, profiled… and it turned out to be 2 bugs in 1 :blobsweats:

* The adblocker (and similar features) makes things slower :psyduck: : https://gitlab.gnome.org/GNOME/epiphany/-/work_items/2880#note_2766101

* WebKitGTK is doing some shenanigans with the system's fonts: https://bugs.webkit.org/show_bug.cgi?id=315135

#GNOMEWeb #WebKitGTK #GNOME #Sysprof #profiling #performance #Linux

#epiphany #gnomeweb #webkitgtk #gnome #sysprof #profiling

Jeff Fortin T. (風の庭園のNekohayo) @[email protected] · 2026-05-20 · 00:27 UTC

For a long time I've been intrigued by #Epiphany taking 3 to 20 seconds to load most websites on startup or in Incognito Mode.

Today I tested a bunch of configurations to report a bug, profiled… and it turned out to be 2 bugs in 1 :blobsweats:

* The adblocker (and similar features) makes things slower :psyduck: : https://gitlab.gnome.org/GNOME/epiphany/-/work_items/2880#note_2766101

* WebKitGTK is doing some shenanigans with the system's fonts: https://bugs.webkit.org/show_bug.cgi?id=315135

#GNOMEWeb #WebKitGTK #GNOME #Sysprof #profiling #performance #Linux

#epiphany #gnomeweb #webkitgtk #gnome #sysprof #profiling

Cegorach @[email protected] · 2026-05-14 · 13:49 UTC

TIL: the #browser #epiphany (a galeon fork that later became the successor) was renamed "Web"

WTF?

That's probably even worse than calling your software "Go" and beats "Kafka" and "Gimp" by a large margin.

when? the only source I found said "somewhere around 2012"? WTF^2

#browser #epiphany

Cegorach @[email protected] · 2026-05-14 · 13:49 UTC

TIL: the #browser #epiphany (a galeon fork that later became the successor) was renamed "Web"

WTF?

That's probably even worse than calling your software "Go" and beats "Kafka" and "Gimp" by a large margin.

when? the only source I found said "somewhere around 2012"? WTF^2

#browser #epiphany

Lisa J. Warner / Lisa Luv @[email protected] · 2026-04-30 · 14:29 UTC

🤗☁️🌈☁️🛐✝️👑🕊️💦❤️‍🔥🩵🏩💒🫂🩷💜🌐🌏💛🤗*DEAR Brothers!*& SISTERS!*I do not consider that I have made it my own!*But one thing I do!*forgetting what lies behind!*& straining forward to what lies ahead!*I press on toward the goal for the prize of the upward call of God in Christ Jesus!*AMEN!*AMEN!*AMEN!{Philipians 3: 13-14}🤗🛐✝️👑🕊️💦❤️‍🔥🩵🏩💒🫂🩷💜🌐🌏💛☁️🌈☁️🤗

#IN #GREAT #LOSS #I #AM #Straining #Toward #the #Goal #Miracle #Epiphany #GOD #Jesus #Christ #Holy #Spirit #Pray #Believe #Heaven #Hope #Peace #Faith #Truth #Love