#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

⛵

@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

⛵

@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

@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

@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

#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

#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

#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

#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

@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

@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

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

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

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

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

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

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

⛵

@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

⛵

@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

⛵

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

⛵

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

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

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

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

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

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

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

⛵

@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

⛵

@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

⛵️

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

⛵️

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

⛵