#tallship — Public Fediverse posts

@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

⛵

The BitchX is Back!

No, not the Elton John song from the seventies - The #IRC client (considered the most popular before #Irssi and #weechat) back in the late 90's on #DALnet and into the 2000's.

But there's a twist, this is an entirely revamped beast, kinda like finding an old Model A Ford that's so rusted out even the axles are seized up and the doors are paper thin with shattered windows, and plenty of bullet holes in the body...

... and then restoring it back to factory showroom floor condition. Except for the engine - a rusted hunk of metal that was replaced with a brand new Chevy 454 Big Block V8; something really contemporary that you might not expect. I'll leave you to discover what that is by visiting the link where the maintainer explains everything :)

And remember, you too can once again be Too Lame to run BitchX!

#tallship #BitchX #ncurses #TUI #FOSS #ANSI_Art

@tedu

Yup. And some time ago too, I might add. The ability to take what works so well and complicate it to the point of absurdity never ceases to amaze.

#Margaret_Hamilton put two men on the moon with 4K of memory. 8K if you're counting the additional RAM on the Columbia's #AGC.

Well if you ever figure out how to lookup your NIC-HANDLE, as they're officially called (or rather, were), I'm BT-74 👋🤠

Yeah, that goes back to the days of "Direct Assignment" when #SRI also operated under the auspices of NIC.DDN.MIL.

Welcome to the club of unhappilly disenfranchised #NIC_handles 😥

#tallship #Apollo #software_engineer #NIC #NetSol #WHOIS

ASP, Intranet, and other mostly forgotten terms of trends harkening back to the ghost of Internet past. Yeah, how 'bout that?

But one of my favs, "BSOD", experienced an overnight resurgence in the lexicon over the breakfast table yesterday.

Even after most folks had long since forgotten this NT phenomenon's affectionate derision, it remained a commonly recognized "oopsie" not resulting from operator failure, yet regardless, one that evokes shuddering waves of guilt within the user.

Have you been Microsoft'd lately? Does your bum hurt? We've been telling you so for decades yet you just continue bending over and begging for it.

"What we've got here is... failure to communicate. Some men you just can't reach. So you get what we had here last week, which is the way he wants it... well, he gets it. I don't like it any more than you men."

#tallship #Linux #FOSS #AYBABTU @eloy

⛵

.

RE: https://hsnl.social/users/eloy/statuses/112818128697453981

An excellent expose on one of the most prolific and creative minds in the #Fediverse, and as the following article by @sean eludes to, far far beyond.

https://wedistribute.org/2024/03/activitypub-nomadic-identity/

@mike 's contributions to #FOSS and #DeSoc go back much further than just the #ActivityPub portions of the Fediverse, well over a decade in fact, as the creator of #Mistpark, now #Friendica, and also #Zot6 and #Nomad, which promises to be a show changer for identity in the world of Social communications.

#tallship

⛵

@onepict

> On any online space, you should consider who you give power to. Who has the control over who you choose to associate with?

I concur 100% with this assertion.

> All that the instances who sign the fedipact are doing is signalling to some of us that somewhere is safe for folk who don't want to engage with Facebook at all.

I don't think that's all, and actually, What those instances may (inadvertently) be signalling is that they will take it upon themselves to remove the Freedom of Association from the user themselves, without prior expectation or consultation.

I don't know where "Freedom of Speech" entered the conversation, but the notion of "Freedom of Association" has indeed been taken from those who have chosen to excercise those privileges belonging to the users themselves. Waking up and realizing that you can no longer communicate and share recipes with grandma, without evern having been consulted, is an affront to the Freedom of Association - it's inclusive of an even larger issue surrounding the reasons that *smolweb and single-user and self-hosted platforms are protective of such principles Freedom of Association.

Further, it serves to create an environment (especially when so many platforms now support migration ingress) where one's Fediverse accounts are considered ever more transient, as the realization that having an account on a silo based Fediverse instance is the antipathy of #Fediverse and #DeSoc philosophies.

It also erodes the trust between the average user and administrators that you thought you could entrust with respecting your freedom of association with.

> This is a Freedom of Association issue, ...

it is indeed, and a betrayal of trust for anyone who realizes that it is the overreach by someone else to decide that you should not have the Freedom of Association that likely brought most folks to the Fediverse in the first place.

I did a little non-scientific, anecdotal survey by contacting people I know on many of the instances that arbitrarily decided to remove those freedoms from their users overnight, and discovered that many have already migrated to other instances, or are contemplating it - the interesting thing? Many of my acquaintances had already decided to, or even configured their accounts to block #Threads; but to have someone else tell them what they're allowed, or not allowed to do, is a violation of someone's freedom to choose for themselves by despot personalities who dismiss the relevance of a right to choose for oneself.

It's a simple matter, to block instances, at the domain level, from one's own user account, and on most Fediverse platforms, there's actually an announcement utility (usually only used to beg for donations) whereby administrative staff can inform their user base of their own ability to control how they themselves choose to exercise their own preferences with respect to #Freedom_of_Association.

Ironically, when perusing the stats, it's the very largest (deprecated, monolithic silo oriented) Fediverse instances (in terms of the # of user accounts and MAU) that have chosen NOT to trample upon the individual user's Freedom to Associate with whom they themselves decide.

NOTE to Fediverse instance admins: Please take under consideration the trust that has been placed in you with respect to the freedoms all individuals are entitled to determine for themselves - reach out to your user base, deploy surveys, collect votes, whatever, but please don't just decide for someone else what you decide is good for people who are NOT YOU.

Subjugation and assimilation into the Borg Collective goes both ways folks.

#AYBABTU (All Your Base Are Belong To Us)

#tallship #despotism #dystopian #authoritarianism

⛵

.

https://zotum.net/item/6e940e3d-9d58-4ce1-8f91-faa7cb392365

https://zotum.net/item/d169fbb2-c6e8-4067-bacc-88d730dc7e53

Really now, why do people stubbornly adhere to the belief that Government entities require warrants to determine anything about you - like, where you are at this particular moment or the GPS coordinates of your location last Tuesday at 17:42hrs UTC? ... And pretty much anything else you can dream up about yourself: The content of conversations with others, everything you've purchased at anytime, what you are likely to eat for dinner this coming Friday, your medical records; you name it!

All without a warrant, even for local law enforcement.

And why would they bother, when they can just buy it from the #privacy_mining companies that you already gave it to for free?

#tallship #industrial_surveillance #privacy_farming #AYBABTU #Subjugation

⛵

.

RE: https://fosstodon.org/users/RTP/statuses/112018299149948961

@RTP

This is really messed up stuffs...

I call it despotic overreach via subjugation through state sponsored industrial surveillance systems.... It has nothing to do with capitalism but rather, that thing that Thomas Jefferson gave us... you know, the thing.

Been to a grocery store lately? You've been complaining for decades now, that they artificially inflate the prices of items so that they can offer you steep discounts on a rotating list of them - If, and only if, you consent to being a "club member". Personally, I've consented many a times; Rite-Aid, Albertson's, Wallgreens, CVS,Von's, and many others, as Brittney Spears, Charles Manson, Joseph Stalin, and even John Rambo, another obvious #nom_de_guerre to combat what would follow as spam but worse, industrial surveillance and privacy mining (of course, you also need to use a fake phone number and a /dev/null email addy).

Have you tried to buy things at Jack in the Box or 7/11 or Mcdonald's lately? ... They have an app for that. Why do you suppose that is? They could just as easily and more efficiently deliver their content via PWS/webapps through your regular browser experience (they don't want to be counter-measured with uBlock Origin or integrated anti-tracking measures on the more sensible web browsers).

They're working really hard to deliver you to evil. I walked into a Smart & Final the other day and saw an unbelievable price for a 30 pack of Natural Light Beer - you had to use a "digital coupon" (just like you do at 7/11 to pay the regular, competitive price for an item). I asked the cashier where in their weekly rag the "digital coupon" was located, and she informed me that one needs to install an app to be eligible for the discount. Fuck that noise. Homey don't play dat.

China has WeChat ... Resistance is Futile.

When you install an app, it's a whole different ballpark of invasiveness, intrusions, data farming, and privacy mining, it's like it's your first day in #Pelican_Bay and you announce that you're going to drop the soap as you shower.

So the next time someone says, "Thank you for shopping at Walmart!", or synonymously, "Go Fuck Yourself", just smile, and offer, "Yes, there's an app for that".

What follows below in the #boost I've shared, that so inspired me to address this issue, is not a simple inconvenience - it's a new beginning :p In #Communist_Red_China, you do everything on your #WeChat app - you submit your elementary school homework, you buy stuffs at the local market, you inform on yourself and your friends to their state equivalent of the #Stazi, and you tell them exactly where to come and arrest, perhaps even disappear you. #Falun_Gong? Healthy? awesome! Now your a live organ donor too - you can thank #Meg_Whitman for that one.

You have been assimilated 🖖

All Your Base Are Belong To Us

#tallship #Sunnyvale_Syndrome #Industrial_Surveillance #Privacy_Mining #Data_Farming #Tracking #Despotism #AYBABTU h/t to @gabriel for bringing this to us via his #LibreSolutions_Network

⛵

.

RE: https://mk.gabe.rocks/notes/9qreb3vsod

@lsn

@alex Like..... Exactly 200?

Not, 186, or 217, or 2000?

Well, at least a kewl round number means it's obviously Scientism, lolz.

https://yewtu.be/watch?v=qItugh-fFgg

#tallship #scientism #nice_round_numbers_mean_it_is_for_realz #ROFLMAOPMP #AYBABTU

⛵

.

@mgorny

#lolwut

You've completely lost me with that assertion.

You prolly don't remember when we did #Gentoo installs from "Stage 1,2,3" tarballs, or when one of the oldest Linux Distros, "Sorcerer Linux" spawned other source based distro forks like #SourceMage, and #Lunar_Linux, yet I fail to glean what the heck your referring to when you relate these to SystemD... I mean.... Huh?

#tallship #FOSS #Slackware -current #Debian_Trixie (Testing) #Arch_Linux

http://sorcerer.silverice.org/

⛵

@tinker @andre
I miss https://github.com/gigablast/open-source-search-engine

No real info on what precipitated its vaporization earlier this year after so long valiantly serving the community:
https://en.wikipedia.org/wiki/Gigablast

I suspect it may have been somehow related to the fiasco with freenode and Crown Prince Andrew Lee, but that's a reach.

#tallship #GigaBlast #search_engines #FOSS

⛵

.

@merchantHelios Who’s that guy in the picture?

Oh! WAIT!

He’s my friend -my very first one way back when we could all pimp our profiles.

BTW, you haven’t heard from him coz #Tom is too busy traveling the world taking shitty photographs as part of his hobby, not having to care about woke bolsheviks and other inconsequential nonsense.

Go Tom, go! You rock!

#tallship #Myspace #frivolity

⛵

.

@bravegpt @adam

Here's a little ditty that might interest a few folks out here in the Wild, Wild, #Fediverse...

It's a Brave Search add on for your browser of choice - i.e., #Vivaldi, #Chromium, #Firefox, #Edge, #Brave, #Opera, and more (oddly enough, I didn't see #Kiwi on the list).

It's called #BraveGPT and after installing it whenever you choose to use #Brave_Search it includes a sidebar with your search results from #ChatGPT along with the regular #SERPs you expect.

https://github.com/kudoai/bravegpt

It's pretty new, and there's also links to other projects like a similar facility for #DuckDuckGo too.

But there's another question that this raises for myself - what happened to userscripts and greasemonkey?

Lemme know what you think, k?

#tallship #FOSS #search #search_engines

⛵

.

@graciegato and @dancinyogi

You should give the soundtrack a good listen too - it's marvelous!

I never saw the movie, but learned the whole story from my parents who used to play that album all the time.

https://invidious.fdn.fr/watch?v=QNIl3Jm51Uo&local=true

#tallship #zorba

⛵

.

@kravietz @mkljczk @rdarmila @xaphanpl Well I really don’t see what the big deal is.

There’s an old saying that goes something like this:

“Fuck ‘em if they can’t take a joke, and choke ‘em if they can’t take a fuck”

My tendencies over the past few decades, when receiving an organized flurry of complaints effectively dog piling some unwitting (and probably innocent) user, has been, as an admin, to summarily delete, deactivate or ban the accounts of all the offending, socalled “activists”.

I don’t need that shit in my life, and i don’t like punk assed sissy bitches… Add nobody likes a snitch! If s user has a problem with you, then the first thing they should do is block or mute you. Problem solved, they no longer have to see it hear from you anymore. If they see bring stalked and continue to be so after blocking someone, then that’s what admins and moderators are for.

But when they get in their little social warrior gang of pussies and try to take down people because they don’t like the way those other people think it speak, it becomes clear that they are there cancerous rot - so…

Boom Shakalaka BOOM 💥 Banhammer time 🔨

I don’t know why I derive such entertainment from that sort of action, but it’s really funny to know that those pussies just lost their ability to spread their bigotry and hatred towards anyone who doesn’t agree to think along their “approved” narrative, and the best part, is that they can’t even complain to anyone about it because they effectively no longer have an account.

Here’s basically the same ToS/AUP that I’ve been using since around 1999 or so…

1. ) Don’t be a Meany!
2. ) No doxing, trolling, stalking, harassment, defaming, threats, or unwanted advances of any kind.
3. ) No ad hominem (adhere to the principles of civil discourse).
4. ) No other behavior we consider inappropriate in a professional setting.
5. ) When in doubt, please kindly refer to rule # 1.

• If you don’t understand the 5 rules above, this may not be a good match for you, and you may wish to consider another project instead.
• We are “Bofh”: Enforcement of these rules are arbitrary, there is no appeal process, and we kick/ban without prior notice.
• This is THE warning.

Very simple. Just five little rules that anyone but a complete moron will understand lolz.

#tallship #Bofh #ToS #CoC #AUP #wokesters #punk_ass_sissy_bitches #cowards #banhammer #God_of_Thunder #AYBABTU

#You_can_haz_Cheezburgerz! 🍔

I hope that helps!

⛵

.

A hearty welcome goes out to all of the refugees coming over from the deprecated, legacy monolithic silo over at #Twatter.

With some easy listening music too...

#AYBABTU

https://youtu.be/8fvTxv46ano

#tallship

🤘🤡🤘

.

Actually, the mention I made in that Fediverse servers list in my previous post doesn’t do #Quanta any justice at all.

This is really an amazingly powerful #Enterprise Fediverse server platform and you really should breakout the popcorn 🍿 pizza 🍕 and 🍺🍻 beers, and watch just observe the potential in #federated corporate computing systems.

https://www.youtube.com/channel/UCxK-ZvGX7B1nCy8Zva_uc7w/playlists

It’s no longer just shitposting in 500 characters or less, lolz. Oh no no no kiddies! This is real #Top_Fuel, #Supercharged horsepower in #Fediverse powered business computing, but light on resources, easy to deploy and self-host as a #Docker or #Podman container, and you can even leverage the management of this business beast on the desktop deploying dozens of “Quanta Web Application Servers” in a matter of seconds with a few clicks using standard management tools like #Portainer and #Nginx_Proxy_Server, or #Yacht with #Kubernetes integration.

Or… As your personal home based Fediverse and #website_server. It’s truly an evolutionary step in ActivityPub-centric platform communication.

And yes, you can just use it for #shitposting.

You can haz #Cheezburgerz 🍔

Apologies for posting unsanitized YouTube links without the safety of using #Invidious, but it’s a whole queue.

#tallship #FOSS #Boom_Shakalaka_Boom 💥 #Enterprise_Fediverse_Server_Platform @ademalsasa @clay @tallship @tallship

⛵

.