#tallship — Public Fediverse posts

@tubetime @FunkyBob

That was a great video. Thanks @Tube🍂Time! I found myself continually unforgivably, dismissively muttering, "So what? So what? So what?" (Recalling that I still have 3 tube testing machines) until you got to the ESD and especially EMP - one might wonder why much of our defense industries settled entirely on LSI, then VLSI, etc., etc., instead of backup primary systems incorporating this "In between" manufacturing technology that you pointed out, which would certainly have benefited from advances in microminiaturization just the same - mostly, anyway.

But then there's that dialog that for some reason just came to me from "White Squall" where the Captain of the Cuban warship smashes the binnacle compass with his rifle butt and Jeff Bridges exclaims in Spanish, "Real sailors need only the stars overhead to navigate".

That was a really kewl project you built. How do you source the parts nowadays for things like nuvistors? There's very few Electronics surplus/liquidator type stores out there anymore.

I'm still trying to suss out whether Chister the Molister in the pic below is a villainous deer in the headlights of having his superspy cover blown, or if he's the inspiration for that other cartoon character of scandalous nature.

#tallship #nuvistor

16.0 Alpha 1 has arrived...

People ask me how come I often don't know these things... It's simple really. I'm on kernel-generic-7.2.4-x86_64-1 running #Slackware -current and don't actually bother to look up from the work I'm doing cause 16 is just a distro's version number, but 7.2.4 is a kernel. Officially, Slackware 16.0 Alpha is available w/the Linux huge 6.18.x kernel while 7.2.4 is in /testing.

Me, I'm just rolling along in production as I have been for close to 30 years now w/ Slackware - current looking back on the next upcoming release like it's something from yesterday lolz.

I do the same thing on #Debian (14/Testing/Forky) I just upgraded my kernel to 7.1.12+deb14-amd64 - so I'm not running that far behind the ultra-bleeding edge of Slackware, or what Arch and Gentoo users are either.

Anyway, you're going to hear more about the upcoming Slackware 16 release as the weeks go on and if there's one thing I can advise you of it's don't get caught up in the guessing game bullshit - Patrick will release it matter-of-factly w/o any fanfare and pretty much all bets will be wrong. The most you can do is to ask, "Is it soup yet?".

So here's the thread, and Patrick's response to the OP (who's running 7.3-RC1)

#tallship #FOSS #Linux #distros
⛵

@cwebber

Christine, maybe not the most popular personality in some circles of our FOSS world, but I received an email 3 days ago from Drew Devault with a link to a diff, with the subject line of Changes to the SourceHut terms of service to limit LLM use that I found to be quite boldly admirable, and I'm sure it's already generating controversy there. It's a tough topic.

Just two little lines in that diff. Nothing magnanimous, no pontificating, very plainly "Nope. Allow it in your project and you'll be evicted".

I was very impressed (He's a major Git provider), but not really surprised. But whatever your thoughts, he does put his money where his mouth is, unlike so many others that have caved in the past to enshittification.

#tallship #FOSS #git #vibe_is_jive
~$ ./kill_sarah_connor.sh #SourceHut

⛵

@nixCraft

Thanks for the referral. I've got a couple of folks I went ahead and sent recommendations to.

On the surface it looks pretty good (bad, actually, because it looks like Windows), for those who are intransigent about abandoning windows, but underneath it's good ole stable Debian GNU/Linux...

And that, with the lightweight Xfce should carry the n00bs right on into the 22nd century (or at least the 4th Decade of the 21st Century).

Very impressive how they kept it simple and focused on just a few major components that everyone can expect and prominently promoting their support for them too.

#tallship #FOSS #Linux #Xfce #Distros

#FediArt52 35. Ship

"All I ask is a tall ship and a star to steer her by." -John Masefield

Reference image: https://jooinn.com/images/ship-59.jpg

#MastoArt #drawing #sketching #ship #TallShip #nautical

@Rachelburch

Children's Hide & Seek Rules Explained

👧 Peek a Boo! 🐮 (You can't see me)

👧 I see you! 🐄 (No you don't. I'm invisible behind this tree)

🐄 (Marco....) 👧❓❓❓

👧 Polo?? 🐮(Marco...) 👧 Stop it! I see you

🐄 (No you don't. I'm invisible. Peek a Boo!)

#tallship #peekaboo #cow #mossy_tree #Stubborn_cow

⛵

RE: https://mastodon.social/users/Rachelburch/statuses/117180493625637970

Interesting new protocol usage?

I actually don't have enough time to play with THIS but maybe some of you do?

Lemme know what you're impressions are!

Apache and MIT licenses...

#tallship #FOSS #music

Here's a quick look at Captain Drew's World, newly compiled and edited by W. H. Bunting, my favorite living maritime historian:

https://ericbender.co/history-of-the-harbor/

If you're interested in maritime and/or late 19th-century history, find a copy!

#history #Boston #maritime #sailing #tallship #biography

@b0rk @quixoticgeek

The ssh-copy-id command is very handy, and suffered a shortcoming until a few years back where it didn't easily accommodate servers listening on non-standard ports (port numbers other than 22). It's especially handy if you're working with more than a single key, and As far as I'm concerned, editing /etc/ssh/sshd_config so that your SSH server is listening on a non-standard port is actually standard operating procedure.

Today let's say your server is listening on port 51555. to add a (default) key you would invoke it like so:

~$ ssh-copy-id -p 51555 [email protected] - copies your default pubkey over.

It will initially ask you for your (b0rk's) password. If you don't supply the username it will use the logged in user. Following successful login, the magic happens, permissions are set and the public key is copied in to ~/.ssh/authorized_keys. The permissions that should be set are equivalent to:
~/.ssh (700)
~/.ssh/authorized_keys (600)

As soon as your public key is copied over, you're logged out and you are instructed to log in again. If you're using your SSH agent then you just see your shell prompt on the remote box after providing the passphrase for the key.

Since you probably had an id_rsa.pub or an id_ed25519.pub and you wanted to use your id_ecdsa.pub on the remote machine instead, then you probably want to alter your copy command to:

~$ ssh-copy-id -p 51555 -i ~/.ssh/id_ecdsa.pub [email protected]

The correct syntax in this instance is to have a space between `-p' and the actual port number, but in practice, whenever you login in the future you'll just enter:

b0rk@local_box:~$ ssh jvns.ca -p51555 (no space before the port number)

Taking this one step further, I recommend having an active trigger of some sort listening on port 22 that simply "null routes" hosts trying to knock on that door. I like null routes because it drops everything before the firewall, but at least use ipsets so you don't use up memory on maintaining huge lists of those who have scanned your machine for an open SSH port. People will recommend things like fail2ban or SSHGuard, but out of the box those are temporary bans and honestly, I'm just not that charitable with second chances towards people who scan for open ssh ports on my boxes.

I actually like to ban entire countries right off the bat, so you too may enjoy incorporating something like this.

#tallship #ipset #null_route #SSH

⛵

The GIMP Is No Slouch

The GNU Image Manipulation Program emerged from UC Berkeley 30 years ago, continues to dominate the graphic arts industry at the forefront of professional FOSS adoption in the industry and is completely cross-platform supporting most major contemporary operating systems.

Poised for some major advances during the next few releases, including additional capabilities supporting proprietary legacy software and a new file format, there's many new bleeding edge innovations leading the industry that need mention and are included in this latest announcement.

#tallship #FOSS #GIMP #GNU #GPL

⛵

Taken this day, 2019, pirate raiders off the shores of Porty!!
https://www.flickr.com/photos/woolamaloo_gazette/48618591148/in/photostream/lightbox/

Stand by to repel boarders!!

#PortobelloEdinburgh
#Edinburgh #Edimbourg #photography #photographie #Portobello #ship #bateau #TallShip #FirthOfForth #Sea #mer #BlackAndWhitePhotography #Pirates

And now a reminder - WriteFreely instead of...

- The overhead you may not be wanting to inherit with #WordPress
- The #Freemium model constantly pressuring you to subscribe to hosted #Ghost

For super serious #ActivityPub powered publishing those two seem to be the only options that come to mind. Certainly, masto is and always has been little more than a joke in that regard, although many have tweaked it to introduce certain improvements; and Between Ghost and WordPress there's truly very little in the way of serious options beyond the #Fediverse where you push out monolithic or RSS syndicated blogs in the world of FOSS.

As many of you are actually aware, #WriteFreely has, in their own words, been there since the beginning. But for some reason, it often seems to slip the mind of the people it most serves to deliver for.

Since it costs nothing to get started, let's begin by changing that and spin ourselves up an instance, shall we?

You can #self_host or be #freely_hosted, and yes, if you later opt for a subscription based, competently managed, hosted solution you are directly contributing to the development team and future progress of the project.

A Fantastic place to start is HERE

#tallship #FOSS #Publishing #Blog Write.As @updates

⛵

.

RE: https://write.as/api/posts/ul3ls9vpogr02t68

@dilmandila

Since you're an author who seems to insist on No DRM (that's a good thing, too), Have you considered:

1. ) Smashwords
2. ) Draft2Digital

I believe these may be the two resources that enable you to deliver your works to the reader at the most affordable prices.

On the other hand, if I'm mistaken and you (or anyone else) knows of better resources that handle publishing & distribution at better price points please do let me know.

#tallship #publishing #Smashwords #epub

⛵

Fresh out of the oven folks. Today, 01 August 2026 - NetBSD 11.0

https://blog.netbsd.org/tnf/entry/netbsd_11_0_released

#tallship #FOSS #NetBSD #UNIX

⛵️

Fresh out of the oven folks. Today, 01 August 2026 - NetBSD 11.0

https://blog.netbsd.org/tnf/entry/netbsd_11_0_released

#tallship #FOSS #NetBSD #UNIX

⛵️

Fresh out of the oven folks. Today, 01 August 2026 - NetBSD 11.0

https://blog.netbsd.org/tnf/entry/netbsd_11_0_released

#tallship #FOSS #NetBSD #UNIX

⛵️

Fresh out of the oven folks. Today, 01 August 2026 - NetBSD 11.0

https://blog.netbsd.org/tnf/entry/netbsd_11_0_released

#tallship #FOSS #NetBSD #UNIX

⛵

The world's first social network?

I think the following block will suffice to speak for itself. Most of you reading this will have no idea what's going on, and that's a shame, really.

Anyway, when you 'finger' it out, feel free to finger me at SDF.org or tilde.team ⛵

From [email protected] Mon Feb 19 21:32:35 1990
Received: from cayuga.cs.rochester.edu by sol.cs.rochester.edu (4.0/q) id AA13568; Mon, 19 Feb 90 21:32:33 EST
Received: from Sail.Stanford.EDU by cayuga.cs.rochester.edu (5.59/q) id AA20402; Mon, 19 Feb 90 21:32:26 EST
Message-Id: [email protected]
Date: 19 Feb 90 1831 PST
From: Les Earnest [email protected]
Subject: re: Greetings...
To: [email protected]
Status: R

[In reply to message sent Mon, 19 Feb 90 16:02:17 EST.]

I'm glad that you are enjoying the C3 articles. I need to write another
one soon.

Here is a response to your conjectures, mostly regurgitated from an
article that I posted on Human-nets in 1985. Feel free to forward it to
alt.forklore.computers, or I can post it there if you prefer. I haven't
been reading that newsgroup, but a quick look indicates that maybe I
should.

Finger was named for the act of pointing. I recall that sometime after it
became popular I received a message from a system administrator who
thought that it should be renamed so that users would not have to use a
"dirty" word. I gave his request all the consideration that it deserved.

I created Finger around 1971 to meet a local need at the Stanford
Artifical Intelligence Lab. People generally worked long hours there,
often with unpredictable schedules. When you wanted to meet with some
group, it was important to know who was there and when the others would
likely reappear. It also was important to be able to locate potential
volleyball players when you wanted to play, Chinese food freaks when you
wanted to eat, and antisocial computer users when it appeared that
something strange was happening on the system.

The only tool then available for seeing who was running on our DEC-10
computer was a WHO program that showed IDs and terminal line numbers for
people who were logged in. There was no information available on people
who were not logged in. I frequently saw people running their fingers
down the WHO display saying things like "There's Don and that's Pattie but
I don't know when Tom was last seen." or "Who in hell is VVK and where
does line 63 go?"

I wrote Finger and developed the supporting database to provide this
information in traditional human terms -- real names and places. Because
I preferred to talk face to face rather than through the computer or
telephone, I put in the feature that tells how long the terminal had been
idle, so that I could assess the likelihood that I would find them there
if I walked down the hall.

The program was an instant hit. Some people asked for the Plan file
feature so that they could explain their absence or how they could be
reached at odd times, so I added it. I found it interesting that this
feature evolved into a forum for social commentary and amusing
observations.

Finger was picked up by a number of other groups with DEC-10 computers
that were connected to Arpanet -- software flowed in all directions around
the net in those days. It later migrated to Un*x, probably via U.C.
Berkeley. Somewhere along the line the idea arose to provide a network
Finger service. I don't remember who suggested that but it seemed like a
good idea at the time so I stuck it in. Some other anxious people wanted
to be able to verify that their mail was delivered to specific addressees,
so the Mail feature was also added.

While I was somewhat surprised by the popularity of Finger, it has not
been as successful as an earlier program that I invented -- the spelling
checker. It too was created to fill a personal need that many others
apparently share. We didn't think about commercial development and
software protection in those days, but if we had we probably could have
made something out of it. On the other hand, I enjoyed the comradery
of those gentler times and have no regrets.

-Les Earnest ([email protected])

tl;dr: Yeah, in case you're wondering, and would like to kick the tires and take it for a spin, on Debian it's as simple as:

# apt update
#apt install finger

if you want to play with the daemon, that would be available to you by installing either efingerd or cfingerd. For #Slackware users, finger is already installed HERE, and the daemon is just #fingerd; finger listens on port 79.

Enjoy! 👋🤠

#tallship #FOSS #finger #social_networking

This image for me resonates with both history and tragedy, though I wasn’t thinking about this when I took the photo. This is the prow of the Portuguese ship Sagres, docked at the Brooklyn waterfront. The figurehead represents Prince Henry the Navigator, who in the 1400s pioneered advances in sailing that turbocharged the Age of Exploration and the expansion of colonial empires. A century later, the first European ship reached the island of Mannahatta. 1/3

#SchiffSamstag #shipsaturday #tallship

More photos from the Portuguese ship NRP Sagres.

My previous posts on the tall ships at NYC’s Parade of Sail:

https://ohai.social/@bluejay/116901402575615422

https://ohai.social/@bluejay/116940483672519140

https://ohai.social/@bluejay/116980232344811388

https://ohai.social/@bluejay/116902384606163849

More thoughts in the comments.

#photography #schiffsamstag #shipsaturday #ship #ships #tallship

#SchiffSamstag #ShipSaturday

The Portuguese tall ship NRP Sagres, docked at the Brooklyn waterfront. This is the last of the four ships that I was able to tour when the international tall ships came to town last month for New York’s Parade of Sail. I’ll post more photos of the Sagres in the comments, as well as links to previous posts about the other ships and some general thoughts.

#photography #ship #ships #tallship #brooklyn #nyc

#FotoVorschlag

“'Im Hafen” (In the harbor)

#photography #ship #tallship #reflection

Tall’ship me to the Moon! #illustration in #ATC format. This one is better than yesterday’s because it has purpose. I should’ve been working but… #drawing #ACEO #artisttradingcards #mastoart #mastodonart #handdrawn #TraditionalArt #markers #tallship #moon

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

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

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

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

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

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

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

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

I hope you find it useful, and Enjoy! 🤗

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

⛵

@dillo

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

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

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

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

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

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

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

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

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

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

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

Kindest regards,

Bradley

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

⛵

And now for dillo

## dillo browser (the honorable mention):

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

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

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

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

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

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

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

So let's get to it, shall we?

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

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

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

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

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

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

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

That's it! dillo has been installed!

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

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

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

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

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

Have fun running dillo!

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

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

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

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

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

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

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

And remember: You can haz #Cheezburgerz! 🍔🍟

I hope that helps!

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

⛵

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

#SchiffSamstag #ShipSaturday

The tall ship INS Sudarshini from India, recently docked at the Brooklyn waterfront after participating in New York’s Parade of Sail.

#photography #monochrome #blackandwhite #ship #tallship #tallships #brooklyn #nyc

Let's get Politcal - Join the Party!

- All is file
- You've got one job
- Make it simple
- Be clear - NOT Clever
- No news is good news
- Plain text is universal
- Write once - Run everywhere
- Connect with others

You can do it right, or you can do it twice

Go here and join the party!

#tallship #FOSS #UNIX #42 #OpenSource

⛵

@evacide

Eva, I'm not sure whether I believe that's a dedicaed privacy mining funnel.

After attempting to jump through all of the hoops with the crazy KYC-like requirements, including the reliance of IIRC, https://gov.com logon and not until the very end of the verification that I was who I said I was it went and required me to provide a DID (that's a phone number, for those of you who do not already know) that it liked.

I'm sorry (NOT) but there was way more than enough divulged, including my existing Gov.com creds, to believe that California was privacy mining for the sake of tracking their subjugated chattel.

Thanks, great idea and thank you also for your public service, but I don't even know if I"m going to bother to go look again - I FELT REALLY VIOLATED

#tallship #privacy #privacy_mining #fingerprinting #industrial_surveillance

⛵

.

Backport Wisdom

"The reason is that they don’t buy the IBM answer as the only answer. The saying in the US is “nobody ever got fired for picking IBM.” That’s not a saying in Europe."
~Doug Michels, January 1987

#tallship #Microtimes #SCO #Logica #IBM #XENIX

⛵

.

Pride of Baltimore II entering Halifax Harbour during Tall Ships 2009. #photography #sailing #baltimoreclipper #prideofbaltimore #sailingphotography #tallship #topsailschooner #halifaxnovascotia #sailingvessel #blackandwhite #blackandwhitephotography

Reflection of the brig #StLawrenceII alongside in Lunenburg at dusk on Saturday. #tallship #reflectionphotography #reflection #lunenburgnovascotia #maritimephotography #sailingvessel #brig

I'm a few days late posting this. Certain projects and utilities I try to showcase as soon as they come out of the oven, but lately I've been tending to other, more pressing matters since my move back to #SuperSunnySouthernCalifornia - like chillin' at the #beach, #spearfishing, and of course, bangin' it out with girlfriends I haven't been able to hangout with for over six years.

Life is awesome - and so is #VaultWarden!

https://github.com/dani-garcia/vaultwarden/releases/tag/1.29.0

#tallship #FOSS #security

⛵

.

Complete and utter bullshit.

Host your own email as a matter of principle. You can receive mail from anywhere and those (very few) that can’t receive yours don’t deserve acknowledgement.

Plain and simple. Any other conclusion makes you a punk assed sissy bitch and a piece of fucking shit.

Legally, and IOW, any mails not received from a correctly configured MTA with corresponding correctly configured DNS is a defective SMTP service subject to that distinction in court.

tl;dr If your shit is set up correctly, then the recipient is responsible for not having received your legitimate email communications (keep your logs kiddos, it will give you a win in court).

Fuckin’ idiots. I swear!

#tallship #MTAs #FOSS #SMTP #DMARC #SPF #DNS #OpenDKIM

• It’s always your responsibility to assure that your services are RFC compliant

• If you can’t receive industry compliant emails then YOU are the negligent party.

⛵

.

RT: https://fedi.pawlicker.com/objects/4bac49fa-87e2-4983-9d41-68a0c33f6fb2

@david @plehegar

Umm, Not UNIX based, and I'm having a little trouble recollecting, (maybe at @yarmo 's "Delightful" site?), But I do know there's a #Fediverse CLI client, and I think it uses the Mastodon API - I just can't think of it right now. #SMJ over at #SDF ported #commode to #NetBSD so I see no reason why you couldn't do this, and think it's a great idea!

#Lain put #Gopher support in #Pleroma, but set the default to a funky port - it works with #Lynx & #Elpher too.

#tallship

⛵

.