#tallship — Public Fediverse posts

@mythologyandhistory @mjj

Yes I believe him, dressed up like a member of The Specials (maybe sax 🎷 player?), and those punk rock skateboarder Vans that he's sporting with the suit.

Even the Sex Pistols were bankrolled merely to showcase their manager Malcolm McLaren's clothing boutique at 430 King's Road in London.

One of my exes was a pre Goth death metal chick with relatively short pink hair and that pasty white corpse like makeup in a different, classy lingerie ensemble everyday of the week ( It helped that she worked at Frederick's on Hollywood Blvd).

If what John Waters is quoted as saying has any weight (and I believe he's spot on) it's that the antisocial movement of the previous decade will be largely found to be insignificant and forgotten because they had no particular and unique fashion sense of their own to remember them by.👋💀

#tallship #heavy_metal #punk_rock #new_wave #forgotten_Gen #music #fashion #lifestyle

⛵

RE: https://mas.to/users/mythologyandhistory/statuses/117176052087304300

@mythologyandhistory @mjj

Yes I believe him, dressed up like a member of The Specials (maybe sax 🎷 player?), and those punk rock skateboarder Vans that he's sporting with the suit.

Even the Sex Pistols were bankrolled merely to showcase their manager Malcolm McLaren's clothing boutique at 430 King's Road in London.

One of my exes was a pre Goth death metal chick with relatively short pink hair and that pasty white corpse like makeup in a different, classy lingerie ensemble everyday of the week ( It helped that she worked at Frederick's on Hollywood Blvd).

If what John Waters is quoted as saying has any weight (and I believe he's spot on) it's that the antisocial movement of the previous decade will be largely found to be insignificant and forgotten because they had no particular and unique fashion sense of their own to remember them by.👋💀

#tallship #heavy_metal #punk_rock #new_wave #forgotten_Gen #music #fashion #lifestyle

⛵

RE: https://mas.to/users/mythologyandhistory/statuses/117176052087304300

@mythologyandhistory @mjj

Yes I believe him, dressed up like a member of The Specials (maybe sax 🎷 player?), and those punk rock skateboarder Vans that he's sporting with the suit.

Even the Sex Pistols were bankrolled merely to showcase their manager Malcolm McLaren's clothing boutique at 430 King's Road in London.

One of my exes was a pre Goth death metal chick with relatively short pink hair and that pasty white corpse like makeup in a different, classy lingerie ensemble everyday of the week ( It helped that she worked at Frederick's on Hollywood Blvd).

If what John Waters is quoted as saying has any weight (and I believe he's spot on) it's that the antisocial movement of the previous decade will be largely found to be insignificant and forgotten because they had no particular and unique fashion sense of their own to remember them by.👋💀

#tallship #heavy_metal #punk_rock #new_wave #forgotten_Gen #music #fashion #lifestyle

⛵

RE: https://mas.to/users/mythologyandhistory/statuses/117176052087304300

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

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

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

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

⛵

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

⛵

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

⛵

Chatrie v. United States

Police officers conducted a Fourth Amendment search when they acquired Okello Chatrie’s location data from Google because an individual has a reasonable expectation of privacy in his cellphone location information.

But is that really the case? Sure, your phone's location data, and (in this country at least) a reasonable expectation of privacy, and that would presumably include cellular data the carriers have.

But does it really include location data that Mr Chatrie sold (bartered, traded in kind for access to network services instead of being charged directly for them) to Google, #Amazon, Faceplant, and other companies who buy ( with the right to resell in exchange for the privilege of utilizing their network services) this data - specifically to sell this privacy mined data to other third party aggregators and.... wait for it.... presumably those who either are, or would sell it to law enforcement agencies on the open market?

Lemme break that down into the crux of the biscuit. Faceplant, InstaSpam, TakToe, Google, Amazon, and others, buy your privacy in a transaction that includes your access to their services - that's the fee for using Faceplant (You know it's not free).

Most of those companies are built wholly, or in part, on this form of legally privacy mining you (in exchange for you using their services). That's how you pay for access to their services. They, in turn, sell that data for operating costs of their business product and hopefully make a profit by doing so.

That sure sounds like consensual sex to me!

So, what's the difference between selling your privacy mined data to other aggregators, for advertising, whatev, and law enforcement?

Don't get me wrong, I think that both notions are atrocious injustices:

- selling your privacy to have access to their network
- Selling that privacy mined data to law enforcement

Let's not church it up here folks - You went to the crossroads, just like Robert Johnson and sold your eternal soul so you could post stupid pictures of yourself on InstaSpam. You literally paid #Meta for network access and the use of their products (InstaSpam and FacePlant and Wassup). You litterally paid google for access to and the use of Google Docs and Gmail and YouTube, gDrive, Etc., (Wait for it...) by giving them permission over the ownership of a certain amount of your personal data (location, posts, private emails, documents saved on Google infra, etc.).

And you wanna know what's wrong with them providing law enforcement with this info.... without a warrant? Umm... Because you sold it to them so they could sell it to others on the open market!!!.

Now, I think there could be distinctions between just handing over data without an actual warrant, and selling that data to law enforcement. The former sounds like infringement of rights while the latter sounds perfectly reasonable to me - both resulting in the exact same disclosure of (potentially) your most private secrets.

But the facts of the matter are that you literally sold them the rights to distribute this information about you in the free marketplace!

"You got this ad because you're a teacher, but more importantly you're a Leo (and single). This ad used your location to see you're in Moscow. You like to support sketch comedy, and this ad thinks you do drag,"

Ew that must've stung!

Once upon a time you could just track virtually anyone's location on Faceplant in real time, but when some people started complaining and there were concerns about potential stalkers, they began shoring this up - first, with Opt-out, but eventually, just removing that capability from the platform for all intents and purposes.... sort of.

There are plenty of companies who publish their AUPs and ToS's explaining that under no circumstances will they divulge shit about you without a legally compelling warrant - further, many of these sites/companies often also publish a Warrant Canary. None of these businesses are of the stature that rises to the level of a #Big_Tech stature.

Here's a bit more on the topic of Warrant Canaries. And another #Warrant_Canary example is HERE.

Now, let's not get all upset about an innocent person being persecuted - Okello Chatrie is a fricken' bank robber who walked into and robbed a credit union in Virginia on the 20th of May in 2019.

If you read through that opinion, you may get the impression that the damming information was cellular data - but I don't believe that's the case; rather, I believe it was GPS data that Alphabet (aka Google) collects with your permission, as a condition agreed to so that you can use Google stuffs. You may say 'same difference', but if it was Geolocation based on GPS data that Google collected from his phone (rather than cellular data provided by the cellular carrier that was his provider), that's an important distinction (Besides, Neither T-Mobile nor Verizon are mentioned).

Anyway, he's a despicable scumbag to be sure, but did he give permission for Google to sell that information to other parties as a result of Google's consent for him to gain access to Googles services? After all, Google paid for the right to do so (when he sold his soul).

Where the distinction becomes relevant, as I see it, oh.... wait... disclaimer (IANAL). There, let's move along, in lay terms, coz I'm a lay person. Anyway, as I see it, Google didn't actually [legally] sell this information to a third party, namely the FBI and other law enforcement agencies - They provided under the terms of a warrant that was issued demanding that it be provided.

That might be nit-picking to some, but I think that's a HUGE distinction. Further, had the cops come to Google and asked if they would sell his geolocation data to them, I believe that it may have been a perfectly acceptable and legal transaction - after all, he did sell his privacy rights at the cross-roads.

But this was a judicial warrant, and the information was subpoena'd (I'm reaching here with the nomenclature, but you get the gist of what I'm saying here.

For a warrant demanding the information, he had a reasonable expectation of privacy. For the sale of the disclosure of information privacy farmed in his Google account for these very purposes, the sale would have, or rather might have, been perfectly legal.

I dunno. I'm interested in your take on this.

So, did the #InstaSpam users have an expectation of privacy to keep #Signal from publishing their private information? Nope! Because that data was legitimately purchased from #Faceplant (Meta, Whatev).

On the other hand, was the same data that law enforcement could have presumably legally purchased from #Google, but chose instead to acquire by court order, substantively any different due to the method they incorporated to secure that data?

Was this a subtle difference? Because I could buy that data from Google if I wanted to, right? Was it just because it was #law_enforcement?

In closing, again, I reiterate that #IANAL but it seems to me that there sure are a lot of crux in that biscuit.

#tallship #privacy_mining #privacy #industrial_surveillance #Supreme_Court

⛵

RE: https://social.sdf.org/@tallship/114889457440228112

`~$ ./kill_sarah_connor.sh`

You no can haz #Cheezburgerz! 🍔🍟

#tallship #LLM #SkyNet

RE: https://social.sdf.org/@tallship/114889457440228112

`~$ ./kill_sarah_connor.sh`

You no can haz #Cheezburgerz! 🍔🍟

#tallship #LLM #SkyNet

RE: https://social.sdf.org/@tallship/114889457440228112

`~$ ./kill_sarah_connor.sh`

You no can haz #Cheezburgerz! 🍔🍟

#tallship #LLM #SkyNet

RE: https://social.sdf.org/@tallship/114889457440228112

`~$ ./kill_sarah_connor.sh`

You no can haz #Cheezburgerz! 🍔🍟

#tallship #LLM #SkyNet

RE: https://social.sdf.org/@tallship/114889457440228112

`~$ ./kill_sarah_connor.sh`

You no can haz #Cheezburgerz! 🍔🍟

#tallship #LLM #SkyNet

Fun with CP/M

You can haz #Cheezburgerz! 🍔 🍟

Enjoy! https://cpm.retrogamecoders.com

#tallship #OS

⛵

Fun with CP/M

You can haz #Cheezburgerz! 🍔 🍟

Enjoy! https://cpm.retrogamecoders.com

#tallship #OS

⛵

Fun with CP/M

You can haz #Cheezburgerz! 🍔 🍟

Enjoy! https://cpm.retrogamecoders.com

#tallship #OS

⛵

Tall Ship in Cork city. '#Andalucia'.

€14/7/35.
No student/OAP discount.

Today, Fri, Sat, Sun, Custom House Quay.

#speirgorm #irishBlueSky #maritimeCork #cork #corkCity #mastodaoine #Andalucia #loveCork #pureCork #tallship #galeon #loveTheLee

Tall Ship in Cork city. Spanish Galeon 'Andalucia'.

Open ship: Thurs, Fri, Sat (+Sun?)

#speirgorm #maritimeCork #courtmacsherry #kinsale #cork #corkCity #mastodaoine #Andalucia #loveCork #pureCork #tallship #galeon #loveTheLee

Big BOOM 💥 a few minutes ago. I was staring off toward the south and into the sky when I saw the huge flash; 180° off into the horizon, from my comfy chair on the back patio.

One thousand one, one thousand two, thousand three, one thousand four, thous...... 💥 BOOM ❕❕❕

So, geez. Pretty fricken' loud for that distance. Not as far away as the harbor itself, so maybe some crystal methodists dispatched themselves to Valhalla.

In the olden days I'd hit up Twitter coz it was the best for "just happened", local events. People actually understood that kind of democratized power, to disseminate information his before it was possible to even enter a news cycle.

X? It's certainly better than it was before #Elon, but lost had been that hyper local community vibe that made real time distribution such a beautiful possibility in a non commercial distribution channel. I suspect that things will heavily coalesce between spontaneous local... Hubs, for lack of a better term, in a global search enabled environment (again), after this current madness constricting almost all other information through the next couple of weeks.

But then again, this is Los Angeles. Land of 💥 boom and doom (and I mean that in the most real sense). It's almost a bloodsport and aspects do exist where you can place wagers in some pretty heinous categories. I'm just being matter of fact here.I grew up here.

Shit happens around here. It always has. 💥 Booms aren't really anything new around here lolz.

I remember a particular big BOOM 💥 I was standing in the living room one afternoon at my buddy's 'luxury apartment' (The Willow Tree, in Torrance, on PCH, next door to my highschool).

I was stoned out of my mind (on weed, teenager, duh!) and I was facing a sliding glass door (open) mostly occluded by drapes, when suddenly, the drapes activity flew up from the carpeted floor, half way to the ceiling.

Then, as they softly fell back towards their positions in front of the glass in the sliding glass doors themselves, spanning I dunno, 12' maybe, they began violently rattling like a motherfucker! I thought both huge panes were going to shatter, like just eight feet in front of me, standing there like the stoned idiot I was.

I dunno recall exactly how many seconds had passed, at least 8 or 9 I figure but memories actually get warped over time, blyet I've always known distinctly, and I recall, instinctively, that it was an obscene amount of seconds passing before the BOOM 💥 was to be followed by those drape lifting gusts of wind hitting me in the face.

And it was the biggest BOOM 💥 that I had ever witnessed, still to this day; and the Port of Los Angeles maybe six or more Miles behind me, when a big ass ship (a really big ass ship) in the harbor was vaporized, lives indelibly within my very Carcass - I shall never, ever, EVER forget that.

Well that's all I really wanted to share. But I would like to ask everyone to take just a moment, no matter what country you're in/from, to reflect with thanks for all the men and women in uniform serving our countries so our children can sleep all comfy and shit at night, with their little Teddy Bears, autobots, ninja turtles, or Peter Rabbits.

Peace be to all, bitches 🤘 🤠🤘 Truly 🙂

#tallship #observations #musings #please_boost You can haz #Cheezburgerz! 🍔

⛵

.

Big BOOM 💥 a few minutes ago. I was staring off toward the south and into the sky when I saw the huge flash; 180° off into the horizon, from my comfy chair on the back patio.

One thousand one, one thousand two, thousand three, one thousand four, thous...... 💥 BOOM ❕❕❕

So, geez. Pretty fricken' loud for that distance. Not as far away as the harbor itself, so maybe some crystal methodists dispatched themselves to Valhalla.

In the olden days I'd hit up Twitter coz it was the best for "just happened", local events. People actually understood that kind of democratized power, to disseminate information his before it was possible to even enter a news cycle.

X? It's certainly better than it was before #Elon, but lost had been that hyper local community vibe that made real time distribution such a beautiful possibility in a non commercial distribution channel. I suspect that things will heavily coalesce between spontaneous local... Hubs, for lack of a better term, in a global search enabled environment (again), after this current madness constricting almost all other information through the next couple of weeks.

But then again, this is Los Angeles. Land of 💥 boom and doom (and I mean that in the most real sense). It's almost a bloodsport and aspects do exist where you can place wagers in some pretty heinous categories. I'm just being matter of fact here.I grew up here.

Shit happens around here. It always has. 💥 Booms aren't really anything new around here lolz.

I remember a particular big BOOM 💥 I was standing in the living room one afternoon at my buddy's 'luxury apartment' (The Willow Tree, in Torrance, on PCH, next door to my highschool).

I was stoned out of my mind (on weed, teenager, duh!) and I was facing a sliding glass door (open) mostly occluded by drapes, when suddenly, the drapes activity flew up from the carpeted floor, half way to the ceiling.

Then, as they softly fell back towards their positions in front of the glass in the sliding glass doors themselves, spanning I dunno, 12' maybe, they began violently rattling like a motherfucker! I thought both huge panes were going to shatter, like just eight feet in front of me, standing there like the stoned idiot I was.

I dunno recall exactly how many seconds had passed, at least 8 or 9 I figure but memories actually get warped over time, blyet I've always known distinctly, and I recall, instinctively, that it was an obscene amount of seconds passing before the BOOM 💥 was to be followed by those drape lifting gusts of wind hitting me in the face.

And it was the biggest BOOM 💥 that I had ever witnessed, still to this day; and the Port of Los Angeles maybe six or more Miles behind me, when a big ass ship (a really big ass ship) in the harbor was vaporized, lives indelibly within my very Carcass - I shall never, ever, EVER forget that.

Well that's all I really wanted to share. But I would like to ask everyone to take just a moment, no matter what country you're in/from, to reflect with thanks for all the men and women in uniform serving our countries so our children can sleep all comfy and shit at night, with their little Teddy Bears, autobots, ninja turtles, or Peter Rabbits.

Peace be to all, bitches 🤘 🤠🤘 Truly 🙂

#tallship #observations #musings #please_boost You can haz #Cheezburgerz! 🍔

⛵

.

Big BOOM 💥 a few minutes ago. I was staring off toward the south and into the sky when I saw the huge flash; 180° off into the horizon, from my comfy chair on the back patio.

One thousand one, one thousand two, thousand three, one thousand four, thous...... 💥 BOOM ❕❕❕

So, geez. Pretty fricken' loud for that distance. Not as far away as the harbor itself, so maybe some crystal methodists dispatched themselves to Valhalla.

In the olden days I'd hit up Twitter coz it was the best for "just happened", local events. People actually understood that kind of democratized power, to disseminate information his before it was possible to even enter a news cycle.

X? It's certainly better than it was before #Elon, but lost had been that hyper local community vibe that made real time distribution such a beautiful possibility in a non commercial distribution channel. I suspect that things will heavily coalesce between spontaneous local... Hubs, for lack of a better term, in a global search enabled environment (again), after this current madness constricting almost all other information through the next couple of weeks.

But then again, this is Los Angeles. Land of 💥 boom and doom (and I mean that in the most real sense). It's almost a bloodsport and aspects do exist where you can place wagers in some pretty heinous categories. I'm just being matter of fact here.I grew up here.

Shit happens around here. It always has. 💥 Booms aren't really anything new around here lolz.

I remember a particular big BOOM 💥 I was standing in the living room one afternoon at my buddy's 'luxury apartment' (The Willow Tree, in Torrance, on PCH, next door to my highschool).

I was stoned out of my mind (on weed, teenager, duh!) and I was facing a sliding glass door (open) mostly occluded by drapes, when suddenly, the drapes activity flew up from the carpeted floor, half way to the ceiling.

Then, as they softly fell back towards their positions in front of the glass in the sliding glass doors themselves, spanning I dunno, 12' maybe, they began violently rattling like a motherfucker! I thought both huge panes were going to shatter, like just eight feet in front of me, standing there like the stoned idiot I was.

I dunno recall exactly how many seconds had passed, at least 8 or 9 I figure but memories actually get warped over time, blyet I've always known distinctly, and I recall, instinctively, that it was an obscene amount of seconds passing before the BOOM 💥 was to be followed by those drape lifting gusts of wind hitting me in the face.

And it was the biggest BOOM 💥 that I had ever witnessed, still to this day; and the Port of Los Angeles maybe six or more Miles behind me, when a big ass ship (a really big ass ship) in the harbor was vaporized, lives indelibly within my very Carcass - I shall never, ever, EVER forget that.

Well that's all I really wanted to share. But I would like to ask everyone to take just a moment, no matter what country you're in/from, to reflect with thanks for all the men and women in uniform serving our countries so our children can sleep all comfy and shit at night, with their little Teddy Bears, autobots, ninja turtles, or Peter Rabbits.

Peace be to all, bitches 🤘 🤠🤘 Truly 🙂

#tallship #observations #musings #please_boost You can haz #Cheezburgerz! 🍔

⛵

.

Ruh Roh❕

When you break the #Google with a legitimate question but #Skynet's AI is too busy searching for #Sarah_Connor to notice that it's been 17 minutes and still hasn't timed out, lolz 🤘💀🤘

#tallship #AltaVista #Inktomi #DMOZ #Curly #AskJeeves #GNUhoo #Bing #GigaBlast #InfoSeek and other dead horses. You no can haz #Cheezburgerz! 🍔

⛵

.

Ruh Roh❕

When you break the #Google with a legitimate question but #Skynet's AI is too busy searching for #Sarah_Connor to notice that it's been 17 minutes and still hasn't timed out, lolz 🤘💀🤘

#tallship #AltaVista #Inktomi #DMOZ #Curly #AskJeeves #GNUhoo #Bing #GigaBlast #InfoSeek and other dead horses. You no can haz #Cheezburgerz! 🍔

⛵

.

Ruh Roh❕

When you break the #Google with a legitimate question but #Skynet's AI is too busy searching for #Sarah_Connor to notice that it's been 17 minutes and still hasn't timed out, lolz 🤘💀🤘

#tallship #AltaVista #Inktomi #DMOZ #Curly #AskJeeves #GNUhoo #Bing #GigaBlast #InfoSeek and other dead horses. You no can haz #Cheezburgerz! 🍔

⛵

.

Just one example of the simply amazing works created by Rachel Burch.

Thank you for sharing @Rachelburch - you can haz #Cheezburgerz! 🍔

#tallship #Rachel_Burch #Photography #Mossy_Glens #Dartmor #Devon

⛵

.

RE: mastodon.social/users/Rachelburch/statuses/112461097334138336

Just one example of the simply amazing works created by Rachel Burch.

Thank you for sharing @Rachelburch - you can haz #Cheezburgerz! 🍔

#tallship #Rachel_Burch #Photography #Mossy_Glens #Dartmor #Devon

⛵

.

RE: mastodon.social/users/Rachelburch/statuses/112461097334138336

Just one example of the simply amazing works created by Rachel Burch.

Thank you for sharing @Rachelburch - you can haz #Cheezburgerz! 🍔

#tallship #Rachel_Burch #Photography #Mossy_Glens #Dartmor #Devon

⛵

.

RE: mastodon.social/users/Rachelburch/statuses/112461097334138336

It's a beatuful day in the neighborhood for ultraviolence and Beethoven.

A work by #Kyle_Willaim_Harper

www.kylewilliamharper.com/gallery/q6cg88v58cz3f3jjrho315unnt82tj

#tallship #art You can haz #Cheezburgerz! 🍔

⛵

.

I'm often inspired to share my thoughts, expound upon something I've read that sparks that inspiration, or pose a bit of socratric reasoning in discourse. Sometimes we actually edjumacate ourselves by asking the tough questions rhetorically. Sometimes it's even more effective if we share those quests with others. It can be a phrase, a paragraph, or a sentence that ignites that quest for understanding within me, and whether I'm simply working it through it myself for my own sake or a genuine desire to share some kind of enlightenment or wisdom with others, I usually feel better doing it in the public eye at the end of the day when all is said and done.

There's a bit of a stir in the Fediverse. Darnell offers us some valuable considerations and specifics in the link to his blog post below.

For me, I think the most interesting part when you read between the lines is, ...

> This latest move could be a way for Meta to use Threads to thwart any potential ActivityPub powered rivals in the Fediverse (like Pixelfed, Friendica & WordPress).

Note that nowhere is masto even listed there - it's insignificant. The #ActivityPub powered rivals in the #Fediverse cited are what have been considered for many years the direct corollaries to #InstaSPAM and #Faceplant, respectively, which of course are the exceedingly capable platforms #Pixelfed and #Friendica.

In all of that, considering that #WordPress is the big game changer here of most recent repute, enjoying a 42% market share of all websites worldwide certainly blows away anything Meta has to offer, but even though it is past the 4th of May, Faceplant and InstaSPAM still do comprise the #phantom_menace flavor of this week.

- Pixelfed has a very nice interface for browsing images. Unlike InstaSPAM however, there isn't this overwhelming nausea attending user accounts with duck-ass selfie-kisses blown into bacteria laden bathroom mirrors, or the overwhelming shitposting of memes scraped from other non-verbal teenage neanderthals. So yes, there's less traffic, typically, but actual photos of things that are actually important and relevant to the people posting them, and more so, liked and boosted by people who appreciate such sentimentalism or professional art. On the downside, is Pixelfed's relatively lackluster editor that fails to provide the poster with paragraph breaks in the WebUI with any reliability, it's mastocrap-like paltry 500 character limit per post, and a complete lack of formatting capabilities (i.e., Markdown or BBCode, Etc.). Having said that, the 500 character limit is easily remedied in a single entry of a config file, which is a blessing to many who have resorted to using the #A11Y alt-text fields to provide the descriptions and narratives for images uploaded, but the other sophomoric qualities of the editor leave massively huge run on paragraphs for the reader to endure - like this one, for example :p

Other awesome projects either spawned directly from, or inspired by the success of Pixelfed are the FediDB research database, which although pretty, leaves much to be desired with respect to completeness; Sup, a client/server federated chat app model; Loops, a closed beta service that aims to position itself as a replacement for, and similar to YouTube shorts; and PubKit, a tool service in closed beta at this time that attempts to service the same or similar tests that the production https://funfedi.dev/ resource does.

- Friendica was once a platform that closely mimicked the look and feel of Faceplant. And then it wasn't, as the Faceplant monoverse continued to evolve in look and feel, and Friendica lagged in what I typically refer to as "Prettiness". Those days are long past, Friendica looks better and better with each and every successive release, and there's an obvious effort on improving the UX for users, making it much more intuitive, and the UI, tending to the "Prettiness" that I do indeed place so much emphasis on.

Once the original darling of the Fediverse, Friendica is once again at the top of the heap with a few others. This does not include the increasingly marginalized masto brand, as more and more adoptees continue to turn their backs to that has-been flagship.

After increasingly pervasive betrayals of both the #FOSS and #DeSoc philosophies and advocates for the past couple of years, eventually revealing it's own EEE aspirations by actively conflating it's masto brand and registered trademarks with that of Fediverse. Even worse, overtly engaging in an onboarding scheme that actively funnels new #Fedizens to one masto machine in particular, in grand, deprecated silo fashion, the masto corporation has populated one of the largest monolithic vertical gardens in the Fediverse itself. The sad part is that, being just another twitter clone, it still has no sense of community and offers nearly a million users a single point of failure. Ouch!

This masto mega-silo problem becomes even less relevant when you visit the Friendica page above, and gloss over the phenomenal feature set and attention given to interoperability with a shopping list of other platforms, protocols, and clients, including:

RSS/Atom, StatusNet, GNU social, Diaspora, SMTP/IMAP, Bluesky, Tumblr, GNU Social, pump.io, Libertree, Blogger, WordPress, Twidere, AndStatus, Bitlbee, Choqok, Frentcl, Gwibber, Hotot, IdentiCurse, Pidgin/Purple, Mustard, Pino, TTYtter.

Now, you might note that Twitter/X has walled off its deprecated monolithic garden, but that doesn't mean that the client and other toolsets that work with those APIs don't still work just fine with Friendica. And we're not even stating the obvious here - ActivityPub clients like Husky, Fedilab, and Sengi work just fine with Friendica, including Friendiqa and Relatica - two fine examples among the numerous choices you have for native Friendica apps for Android and desktop.

For more of an in-depth read on Relatica, here's an article I published a while back

The second most interesting thing that Darnell mentions, I think, has to do with the verbiage in which he characterizes Existing and traditional Fediverse powered platforms. Rivals. He calls them, "...ActivityPub powered rivals". Hmmmm....

I do believe that's the first time I've actually heard it put quite like that. But it's true. to be certain, it wasn't, not by a longshot, just a little while ago, but now? Well, it's nothing that we've done here in the Fediverse, except for continue to just ignore what's going on with the #subjugated_chattel that have all but succumbed to the #Sunnyvale_Syndrome, and get on with the good work of building and #dogfooding FOSS. But, ...

It's got a lot to do with what you might call interlopers, carpetbaggers, snakeoil salesmen, infestation, or maybe just plain old encroachment of aged and abusive #dreadnoughts into the Fediverse that stubbornly adhere to their deprecated, monolithic silo model of privacy farming technologies.

Hitherto all of these ActivityPub refits and forays into a Privacy mindful and respecting network of social communications systems, people kept using terms like Alternatives, for ActivityPub powered platforms such as the three main platforms mentioned in Darnell's blog article.

Now, they're being elevated to the rank of Rivals? But we, we, didn't do anything!

Neither did the GPL'd Linux Kernel - it just continued to do what FOSS does. It doesn't care what thinks it may be in competition with, or what considers it a threat, or rival or yes, REPLACEMENT for things like Faceplant and InstaSPAM.

Yes, FOSS just lumbers and chugs right along, relatively oblivious to whatever the proprietary, closed source contemporaries think of it - with respect to Linux, It actually entered the jurisdiction of a market dominated by Microsoft, IBM, and a couple of others, was lampooned and ridiculed, until it was considered a Cancer, by Microsoft CEO Steve Ballmer, but this wasn't Microsoft or others encroaching into a space where only Linux and the BSDs resided...

This time it is different, because it's the other way around, but the end result will be the same. In the meantime, the perceived hostile invader, at the moment, is Zuckerberg's Meta. This isn't an EEE in the works, it's a desperate attempt to reach and hold onto the the coping that lines the deep end of a swimming pool which InstaSPAM and Faceplant must learn to swim in, and yet cannot - in the meantime, until it is able to tread those waters, it is feebly dog-paddling toward the edge where a handhold can be made while it is fitted with water-wings.

Even though both Tom (everyone's friend) and Eugen are happily traveling around the world snapping photographs and flirting with photography as a hobby, #Mark_Zuckerberg really doesn't wanna be #Myspaced.

If you don't move, you atrophy.

But Friendica, WordPress, and Pixelfed? Well, they're just FOSS, and they're just doing what FOSS does - exist, improve, and evolve. independently and irrespective of commercial threats by would be competitors.

Existing Fediverse platforms continue to onboard new Fedizens hourly, that's not slowing down, and it isn't going to either. Some of these n00bs are straddling the fence until they get their sea legs, existing in both worlds, while others are just cutting ties with the deprecated monolithic silos and jumping into the pool head first.

This phenomena of adoption and the logarithmic increase in onboarding and the deployment of new Fediverse instances is only going to pick up pace as the masses of users on platforms like #Threads and #Bluesky continue to become aware of the Fediverse, and the freedoms they can enjoy in social communication through leveraging WordPress, Pixelfed, and Friendica (and it goes without saying, all the rest of the wonderful platforms too).

With a community facade that pretended to hold the reigns of masto having been dropped, leaving a new 501(c)(3) masto corporation in the US steered by the likes of Twitter founders themselves, the steam is running out on that brand, and although Meta, via Threads, is certainly welcome to participate in the #FEP process (they actually are), there's really no foothold with which they can insert a toe and dictate very much at all that the community itself isn't inclined to adopt already, independently and without concern of capture by well funded special interest groups - like the new US masto corp.

But in closing, let's get back to why all of this doesn't even really matter where existing traditional Fediverse platforms are concerned - or the millions of users actively engaged on those thousands of hubs and instances:

Because it's FOSS, it evolves organically, and just doesn't care about that kind of stuff, lolz.

#tallship

⛵

.

RE: https://one.darnell.one/users/darnell/statuses/112405069391666443

@darnell

Okay it's one of those, "What's peculiar here?" kinda things.

Consider the source itself. And I certainly don't mean code of any sort. 'Why' would 'They' cite Wikipedia, as good a resource as anyone might think it to be?

Why not cite yourself? Instead of citing someone else - who will merely turn right around and cite you as the ultimate source reference?

#FOSS #DOS, get it? I was rather amused. Anyway, Here it is.

#tallship #Microsoft h/t to: @[email protected] You can haz #Cheezburgerz! 🍔

⛵

.

Okay it's one of those, "What's peculiar here?" kinda things.

Consider the source itself. And I certainly don't mean code of any sort. 'Why' would 'They' cite Wikipedia, as good a resource as anyone might think it to be?

Why not cite yourself? Instead of citing someone else - who will merely turn right around and cite you as the ultimate source reference?

#FOSS #DOS, get it? I was rather amused. Anyway, Here it is.

#tallship #Microsoft h/t to: @[email protected] You can haz #Cheezburgerz! 🍔

⛵

.

Okay it's one of those, "What's peculiar here?" kinda things.

Consider the source itself. And I certainly don't mean code of any sort. 'Why' would 'They' cite Wikipedia, as good a resource as anyone might think it to be?

Why not cite yourself? Instead of citing someone else - who will merely turn right around and cite you as the ultimate source reference?

#FOSS #DOS, get it? I was rather amused. Anyway, Here it is.

#tallship #Microsoft h/t to: @[email protected] You can haz #Cheezburgerz! 🍔

⛵

.

Efforts like this are sometime an excercise in futility - and sometimes they will exceed the wildest expectations of those curating the initiative.

Sometimes all you can do is just rinse and repeat, in the hopes that there will be an eventual cultural shift in the reasons why some species are driven to such brinks of extinction - i.e., poaching.

One such story local to me was the demise of white sea bass. A success story really.

When I was a kid I used to go fishing on local piers and boats. Signs everywhere informing fishermen that there was a moratorium on the taking of white sea bass. in Later years, that moratorium, in conjunction with a captive breeding program in conjunction with Scripps Institution of Oceanography allowed biologists to track just how successful (or unsuccessful) the program was.

We dosed the juveniles in their tanks at different ages with tetracycline. The antibiotic had the side affect of marking the bones of the developing fish, and this could be observed after examining cross-sections of their bones, much like the rings of a tree. It also allowed us to determine which exact batch of juveniles a particular specimen was a member of.

After some time, and an observance of more white sea bass turning up on the end of a hook, a bounty program was started so that the Department of Fish and Game would collect specimens which would later be examined in labs at the Hubbs-Seaworld Research Institute in Sandy Eggo.

It may just be because it was a California phenomenon, where people largely respected gaming regulations, and I realize that gator skinned cowboy boots and purses are popular, as are the horns of white rhinos and elephant ivory - three very insidiously compelling incentives for poaching those species; but average folks fishing along the coast of California were more than happy to comply with regulations that were perceived as in the best interest of an endangered species.

Today, there's actually size and bag limits on white sea bass, a very yummy catch that is common on the dinner plate. Decades of overfishing, and a conservation program to avert extinction as a result were an overwhelming success.

I hope this can extend to that of the Siamese Crocodile too.

#tallship #extinction #Siamese_Crocodiles #White_Sea_Bass #rhinocerous #elephants #sea_turtles #dodo_bird #takahe You can haz #Cheezburgerz! 🍔

⛵

RE: scholar.social/users/animalculum/statuses/112320836447009100

Yes! Yes! Yes!

As the saying goes, "Real BOFH use tar and rsync!"

The blog article is an excellent treatment of using tar along with SSH to effect a reliable backup plan and schedule.

Another couple of great fav GoTo solutions of mine have always been Duplicity and Duply for those not comfortable rolling their own scripts w/SSH, tar, and/or rsync ​:batman:​

Thank you very much for sharing this @nixCraft !!!

#tallship #DR #backup #tar #rsync #SSH #Systems_Administration You can haz #Cheezburgerz! 🍔

⛵

.

RE: mastodon.social/users/nixCraft/statuses/112276456842443382

Yes! Yes! Yes!

As the saying goes, "Real BOFH use tar and rsync!"

The blog article is an excellent treatment of using tar along with SSH to effect a reliable backup plan and schedule.

Another couple of great fav GoTo solutions of mine have always been Duplicity and Duply for those not comfortable rolling their own scripts w/SSH, tar, and/or rsync ​:batman:​

Thank you very much for sharing this @nixCraft !!!

#tallship #DR #backup #tar #rsync #SSH #Systems_Administration You can haz #Cheezburgerz! 🍔

⛵

.

RE: mastodon.social/users/nixCraft/statuses/112276456842443382

Yes! Yes! Yes!

As the saying goes, "Real BOFH use tar and rsync!"

The blog article is an excellent treatment of using tar along with SSH to effect a reliable backup plan and schedule.

Another couple of great fav GoTo solutions of mine have always been Duplicity and Duply for those not comfortable rolling their own scripts w/SSH, tar, and/or rsync ​:batman:​

Thank you very much for sharing this @nixCraft !!!

#tallship #DR #backup #tar #rsync #SSH #Systems_Administration You can haz #Cheezburgerz! 🍔

⛵

.

RE: mastodon.social/users/nixCraft/statuses/112276456842443382

Okay I thought I'd share this recent post here on the #Fediverse. To give it some context, it's an answer to a common question, often a misunderstanding (even by many knowledgeable folks) as to just how we got here.

So first, the question, posed HERE.

And my answer follows below:

There's a lot of apples and oranges here. And everyone had a lot of good points made, but your question is simple, and has a very simple answer. I'll endeavor to address that directly, but do need to tend to some of what has already been said.

## Scroll down to the tl;dr for the succinct answer of your question

Ethernet, ARCNET, Token Ring, Thick net (RG-59), Thin net (RG-58 A/U), and UTP (Cat 3, Cat 5, and Cat 6 unshielded twisted pair, Etc.) really have zero bearing on your question insofar as IP is concerned. All of these specifications relate to the definition of technologies that, although are indeed addressed in the OSI model which is indeed very much in use to this day,but are outside the scope of Internet Protocol. I'll come back to this in a minute.

It's quite common to say TCP/IP, but really, it's just IP. For example, we have TCP ports and we have UDP ports in firewalling. i.e., TCP is Transmission Control Protocol and handles the delivery of data in the form of packets. IP handles the routing itself so those messages can arrive to and from the end points. Uniform Data Protocol is another delivery system that does not guarantee arrival but operates on a best effort basis, while TCP is much chattier as it guarantees delivery and retransmission of missed packets - UDP is pretty efficient but in the case of say, a phone call, a packet here and there won't be missed by the human ear.

That's a very simplistic high level-view that will only stand up to the most basic of scrutiny, but this isn't a class on internetworking ;) If you just want to be able to understand conceptually, my definition will suffice.

Networking (LAN) topologies like Token Ring, ARCNET, and Ethernet aren't anywhere in the IP stack, but figure prominently in the OSI stack. I'm not going to go into the details of how these work, or the physical connection methods used like Vampire Taps, Thin net, or twisted pair with RJ-45 terminators, but their relationship will become obvious in a moment.

The OSI model unfolds like so, remember this little mnemonic to keep it straight so you always know:

> People Don't Need To See Paula Abdul

Okay, touched on already, but not really treated, is the description of that little memory aid.

> Physical, Data Link, Network, Transport, Session, Presentation, and Application layers (From bottom to top).

The physical and Data Link layers cover things like the cabling methods described above,and you're probably familiar with MAC Addresses (medium access control) on NICs (network interface controller). These correlate to the first two layers of the OSI stack, namely, the Physical (obvious - you can touch it), and the Data Link layer - how each host's NIC and switches on each LAN segment talk to each other and decide which packets are designated for whom (People Don't).

In software engineering, we're concerned mostly with the Session, Presentation, and Application layers (See Paula Abdul). Detailed explanation of these top three layers is outside the scope of this discussion.

The Beauty of the OSI model is that each layer on one host (or program) talks to exclusively with the same layer of the program or hardware on the other host it is communicating with - or so it believes it is, because, as should be obvious, is has to pass its information down the stack to the next layer below itself, and then when it arrives at the other host, it passes that information back up the stack until it reaches the very top (Abdul) of the stack - the application.

Not all communication involves all of the stacks. At the LAN (Local Area Network) level, we're mostly concerned with the Physical and Data Link layers - we're just trying to get some packet that we aren't concerned about the contents of from one box to another. But that packet probably includes information that goes all the way up the stack.

For instance, NIC #1 has the MAC: 00:b0:d0:63:c2:26 and NIC #2 has a MAC of 00:00:5e:c0:53:af. There's communication between these two NICs over the Ethernet on this LAN segment. One says I have a packet for 00:00:5e:c0:53:af and then two answers and says, "Hey that's me!" Nobody else has that address on the LAN, so they don't answer and stop listening for the payload.

Now for Internet Protocol (IP) and TCP/UDP (Transmission Control Protocol and User Datagram Protocol):

IP corresponds to Layer 3 (Need) - the Network Layer of the **OSI Model.

TCP and UDP correspond to Layer 4 (To) - the Transport Layer of the OSI model.

That covers the entire OSI model and how TCP/IP correspond to it - almost. You're not getting off that easy today.

There's actually a bit of conflation and overlapping there. Just like in real life, it's never that cut and dried. For that, we have the following excellent explanation and drill down thanks to Julia Evans:

- Layer 2 (Don't) corresponds to Ethernet.
- Layer 3 (Need) corresponds to IP.
- Layer 4 (To) corresponds to TCP or UDP (or ICMP etc)
- Layer 7 (Abdul) corresponds to whatever is inside the TCP or UDP packet (for example a DNS query)

You may wish to give her page a gander for just a bit more of a deeper dive.

Now let's talk about what might be a bit of a misconception on the part of some, or at least, a bit of a foggy conflation between that of the specification of the OSI model and a Company called Bolt Beranek & Newman (BBN) a government contractor tasked with developing the IP stack networking code.

The TCP/IP you know and depend upon today wasn't written by them, and to suggest that it was the OSI model that was scrapped instead of BBN's product is a bit of a misunderstanding. As you can see from above, the OSI model is very much alive and well, and factors into your everyday life, encompasses software development and communications, device manufacturing and engineering, as well as routing and delivery of information.

This next part is rather opinionated, and the way that many of us choose to remember our history of UNIX, the ARPANET, the NSFnet, and the Internet:

The IP stack you know and use everyday was fathered by Bill Joy, who arrived at UC Berkeley in (IIRC) 1974), created vi because ed just wasn't cutting it when he wanted a full screen editor to write Berkeley UNIX (BSD), including TCP/IP, and co-founded Sun Microsystems (SunOS / Solaris):

> Bill Joy just didn’t feel like this (the BBN code) was as efficient as he could do if he did it himself. And so Joy just rewrote it. Here the stuff was delivered to him, he said, “That’s a bunch of junk,” and he redid it. There was no debate at all. He just unilaterally redid it.

Because UNIX was hitherto an AT&T product, and because government contracting has always been rife with interminable vacillating and pontificating, BBN never actually managed to produce code for the the IP stack that could really be relied upon. In short, it kinda sucked. Bad.

I highly recommend that you take a look at this excellent resource explaining the OSI model.

# tl;dr:

So! You've decided to scroll down and skip all of the other stuff to get the straight dope on the answer to your question. Here it is:

> What were the major things that caused TCP/IP to become the internet standard protocol?

The ARPANET (and where I worked, what was to become specifically the MILNET portion of that) had a mandate to replace NCP (Network Control Protocol) with IP (Internet Protocol). We did a dry run and literally over two thirds of the Internet (ARPANET) at that time disappeared, because people are lazy, software has bugs, you name it. There were lots of reasons. But that only lasted the better part of a day for the most part.

At that time the ARPANET really only consisted of Universities, big Defense contractors and U.S. Military facilities. Now, if you'll do a bit of digging around, you'll discover that there was really no such thing as NCP - that is, for the most part, what the film industry refers to as a retcon, meaning that we, as an industry, retroactively went back and came up with a way to explain away replacing a protocol that didn't really exist - a backstory, if you will. Sure, there was NCP, it was mostly a kludge of heterogeneous management and communications programs that varied from system to system, site to site, with several commonalities and inconsistencies that were hobbled together with bailing twine, coat hangers, and duct tape (for lack of a better metaphor).

So we really, really, needed something as uniform and ubiquitous as the promise that Internet Protocol would deliver. Because Bill Joy and others had done so much work at UC Berkeley, we actually had 4.1BSD (4.1a) to work with on our DEC machinery. As a junior member of my division, in both age and experience, I was given the task of, let's say throwing the switch on some of our machines, so to speak, when we cut over from the NCP spaghetti and henceforth embraced TCP/IP no matter what, on Flag Day - 01 January 1983.

So you see,the adoption of Internet Protocol was not a de facto occurrence - it was de jure, a government mandate to occur at a specific time on a specific day.

It literally had nothing to do with popularity or some kind of organic adoption, the erroneously described, so-called demise of the OSI model, or any physical network topology.

### DARPA said 01 January 1983 and that's it, and that was it - Flag Day.

Sure, it took a few days for several facilities to come up (anyone not running IP was summarily and unceremoniously cut off from the ARPANET).

And one also needs to consider that it wasn't every machine - we only had some machines that were Internet hosts. We still had a lot of mainframes and mini computers, etc., that were interconnected within our facilities in a hodgepodge or some other fashion. Nowadays we have a tendency to be somewhat incredulous if every device doesn't directly connect over IP to the Internet in some way. That wasn't the case back then - you passed traffic internally, sometimes by unmounting tapes from one machine and mounting them on another.

There was a lot of hand wringing, stress, boatloads of frustration, and concern by people over keeping their jobs all over the world. But that's why and when it happened. Six months later in the UNIX portions of networks we had much greater stability with the release of 4.2BSD, but it wouldn't really be until a few years later Net2 was released that things settled down with the virtually flawless networking stability that we enjoy today.

Enjoy!

#tallship #DARPA #IP #Internet_Protocol #Computer_History #internetworking #Internet #ARPANET #MILNET #NSFnet #Bill_Joy #BBN #UNIX #BSD

⛵

.

More champions of the relevance of #FOSS, #Dogfooding, and deprecating proprietary close source systems like Google and Dropbox in favor of taking back the ownership of our own data, and moreover, our privacy 🙂

Yes, you can haz #Cheezburgerz 🍔

#tallship #Nextcloud

⛵

.

More champions of the relevance of #FOSS, #Dogfooding, and deprecating proprietary close source systems like Google and Dropbox in favor of taking back the ownership of our own data, and moreover, our privacy 🙂

Yes, you can haz #Cheezburgerz 🍔

#tallship #Nextcloud

⛵

.

More champions of the relevance of #FOSS, #Dogfooding, and deprecating proprietary close source systems like Google and Dropbox in favor of taking back the ownership of our own data, and moreover, our privacy 🙂

Yes, you can haz #Cheezburgerz 🍔

#tallship #Nextcloud

⛵

.

Go Tommy, it's your birthday, Go Tommy, it's your birthday, Go Tommy, Go Tommy

#tallship #Tommy_Wiseau #Best_Fiends - F(r)iends @TommyWiseau You can haz #Cheezburgerz! 🍔

⛵

.

RE: https://mastodon.social/users/TommyWiseau/statuses/102890475029012257

@TommyWiseau

Go Tommy, it's your birthday, Go Tommy, it's your birthday, Go Tommy, Go Tommy

#tallship #Tommy_Wiseau #Best_Fiends - F(r)iends @TommyWiseau You can haz #Cheezburgerz! 🍔

⛵

.

RE: https://mastodon.social/users/TommyWiseau/statuses/102890475029012257

@TommyWiseau

Go Tommy, it's your birthday, Go Tommy, it's your birthday, Go Tommy, Go Tommy

#tallship #Tommy_Wiseau #Best_Fiends - F(r)iends @TommyWiseau You can haz #Cheezburgerz! 🍔

⛵

.

RE: https://mastodon.social/users/TommyWiseau/statuses/102890475029012257

@TommyWiseau

Yay!!!!!!

Made with love by entering :sailboat:

w00t.

#tallship #sailboats #Happy_Happy_Joy_Joy (Wren and Stimpy, for those who don't already know) @silverpill - You can haz #Cheezburgerz! 🍔 (yah, the burger was a copypasta, but I know the shorthand for a sailboat now!)

⛵

.

RE: https://public.mitra.social/objects/018e8ee1-bc93-b131-7fa2-f43f07950ad5

@tallship

Yay!!!!!!

Made with love by entering :sailboat:

w00t.

#tallship #sailboats #Happy_Happy_Joy_Joy (Wren and Stimpy, for those who don't already know) @silverpill - You can haz #Cheezburgerz! 🍔 (yah, the burger was a copypasta, but I know the shorthand for a sailboat now!)

⛵

.

RE: https://public.mitra.social/objects/018e8ee1-bc93-b131-7fa2-f43f07950ad5

@tallship

Yay!!!!!!

Made with love by entering :sailboat:

w00t.

#tallship #sailboats #Happy_Happy_Joy_Joy (Wren and Stimpy, for those who don't already know) @silverpill - You can haz #Cheezburgerz! 🍔 (yah, the burger was a copypasta, but I know the shorthand for a sailboat now!)

⛵

.

RE: https://public.mitra.social/objects/018e8ee1-bc93-b131-7fa2-f43f07950ad5

@tallship

@tapir

Hey Adam,

Just touching base here, I wanted to see how #Tapir is coming along and... Oh, it's been a while since the last commit.

Anyway, had some discussions with a couple of folks about it and how it's #Deno, so there's excitement there.

Do please lemme know when you've taken up that torch again - I know you wear a lot of hats :)

All the best!

#tallship #FOSS #Fediverse #ActivityPub #smolweb
You can haz #Cheezburgerz! 🍔

⛵

.

@tapir

Hey Adam,

Just touching base here, I wanted to see how #Tapir is coming along and... Oh, it's been a while since the last commit.

Anyway, had some discussions with a couple of folks about it and how it's #Deno, so there's excitement there.

Do please lemme know when you've taken up that torch again - I know you wear a lot of hats :)

All the best!

#tallship #FOSS #Fediverse #ActivityPub #smolweb
You can haz #Cheezburgerz! 🍔

⛵

.