Search
1000 results for “tallship”
-
I keep telling others that over and over, even over at WHT and other industry forums.
Start with at least a half rack (full being 42U) and 100A. You can buy two or three identical (I prefer Proliants, but refurb'd Dells are just as good) 1U servers for your #Proxmox VE cluster for less than $400 each on #eBay (typically 384GB RAM each and several populated SAS bays) including shipping, straight to you or your data center of choice, an inexpensive managed layer 3 switch can be picked up for under $200 and half of the colo sites will throw in a PDU at no charge.
A full rack can be had with 200A, XC, and unmetered blended gigabit transport for under a grand per month (less than .002ms from One Wilshire here in Los Angeles), so your average half rack will be a little more than half that w/100Mbps or better.
If you have your own IP block they'll announce and route for free with a letter of agency from you and with a full rack they should be willing to throw in a /19 included in those price points gratis.
Pro Tip: wait until the last week of any month BEFORE speaking with ANY sales reps. They'll sell their own mothers to get their end of month bonuses - you can save really big coz all they care about is closing and getting that bonus check.
If you're still not sure, let me quote you...
We're being taken for a ride.
Renting is not working out. It's time to OWN the means of federation!
I couldn't agree more
#federation #Fediverse #FOSS #self_hosted #Colo
#tallship⛵
-
Man, livin' at home is such a drag
Now your mom threw away your best porno magw/ Slayer’s Kerry King on guitar 🤘 💀 🤘
https://www.youtube.com/watch?v=eBShN8qT4lk
#tallship #metal #Rick_Rubin #No_Fucking_Sleep_Till_Brooklyn
⛵
.
-
Man, livin' at home is such a drag
Now your mom threw away your best porno magw/ Slayer’s Kerry King on guitar 🤘 💀 🤘
https://www.youtube.com/watch?v=eBShN8qT4lk
#tallship #metal #Rick_Rubin #No_Fucking_Sleep_Till_Brooklyn
⛵
.
-
Man, livin' at home is such a drag
Now your mom threw away your best porno magw/ Slayer’s Kerry King on guitar 🤘 💀 🤘
https://www.youtube.com/watch?v=eBShN8qT4lk
#tallship #metal #Rick_Rubin #No_Fucking_Sleep_Till_Brooklyn
⛵
.
-
@rl_dane @msdropbear42 @MsDropbear42
Hey R.L. Dane,
as per your OP in this thread, I've been using #Remmina for years. X2Go, RDP, WhatEv really floats yer boat ⛵ , it's there.
Uh, oh, I feel a tangent coming on... Okay not to hijack your thread, but maybe you can offer a bit of your perspective on flatpak vs appimage alternatives, since I don't prefer either, and usually will go out of my way to create a native package for WhatEv distro I'm using if it doesn't exist, or just compile from source rawdawg if need be like I did with #Zed (which only impresses me because of Git integration and Vim bindings; and it's Rust) - Jury's still out on that one though.
Anyway, I just broke down and installed a flatpak for the #LaGrange browser because I got a bit lazy and didn't wanna make the .deb for myself.
Okay, back to your situation...
Remmina HERE is pretty comprehensive with the native package managers with ready to go .deb's for #Forky & Sid, #SlackBuild for #Slackware, #FreeBSD & #OpenBSD ports, #Devuan, #Gentoo, #Guix, and #Kali just to name some.
It's pretty straight-forward and a single package to accommodate a plethora of methodologies so you can use it as your Varsity first string go-to in a pinch most of the time.
Even better, is the fact that they don't have an ewb00ntew maintainer, lolz... Coz frinds don't let frinds run ewb00tew :p
-
@rl_dane @msdropbear42 @MsDropbear42
Hey R.L. Dane,
as per your OP in this thread, I've been using #Remmina for years. X2Go, RDP, WhatEv really floats yer boat ⛵ , it's there.
Uh, oh, I feel a tangent coming on... Okay not to hijack your thread, but maybe you can offer a bit of your perspective on flatpak vs appimage alternatives, since I don't prefer either, and usually will go out of my way to create a native package for WhatEv distro I'm using if it doesn't exist, or just compile from source rawdawg if need be like I did with #Zed (which only impresses me because of Git integration and Vim bindings; and it's Rust) - Jury's still out on that one though.
Anyway, I just broke down and installed a flatpak for the #LaGrange browser because I got a bit lazy and didn't wanna make the .deb for myself.
Okay, back to your situation...
Remmina HERE is pretty comprehensive with the native package managers with ready to go .deb's for #Forky & Sid, #SlackBuild for #Slackware, #FreeBSD & #OpenBSD ports, #Devuan, #Gentoo, #Guix, and #Kali just to name some.
It's pretty straight-forward and a single package to accommodate a plethora of methodologies so you can use it as your Varsity first string go-to in a pinch most of the time.
Even better, is the fact that they don't have an ewb00ntew maintainer, lolz... Coz frinds don't let frinds run ewb00tew :p
-
@rl_dane @msdropbear42 @MsDropbear42
Hey R.L. Dane,
as per your OP in this thread, I've been using #Remmina for years. X2Go, RDP, WhatEv really floats yer boat ⛵ , it's there.
Uh, oh, I feel a tangent coming on... Okay not to hijack your thread, but maybe you can offer a bit of your perspective on flatpak vs appimage alternatives, since I don't prefer either, and usually will go out of my way to create a native package for WhatEv distro I'm using if it doesn't exist, or just compile from source rawdawg if need be like I did with #Zed (which only impresses me because of Git integration and Vim bindings; and it's Rust) - Jury's still out on that one though.
Anyway, I just broke down and installed a flatpak for the #LaGrange browser because I got a bit lazy and didn't wanna make the .deb for myself.
Okay, back to your situation...
Remmina HERE is pretty comprehensive with the native package managers with ready to go .deb's for #Forky & Sid, #SlackBuild for #Slackware, #FreeBSD & #OpenBSD ports, #Devuan, #Gentoo, #Guix, and #Kali just to name some.
It's pretty straight-forward and a single package to accommodate a plethora of methodologies so you can use it as your Varsity first string go-to in a pinch most of the time.
Even better, is the fact that they don't have an ewb00ntew maintainer, lolz... Coz frinds don't let frinds run ewb00tew :p
-
Modula-2, UCSD P-System, and the birth of Scala
I stumbled across this tidbit from Hacker News.
I never liked that #Borland stuffs. And used to program in #Pascal in #UCSD P-system (my alma mater). When I got to the US Department of Defense they wanted me for my #C and #COBOL skills and then they sent me to an Air Force School where I studied Modula-2 and Ada.
I did a lot of work in Modula-2, which doesn't exist anymore. Modula-3 does, but in the meantime Scala was in the works. #Ada is still actually a thing. We didn't want clever, like those one liner #Perl challenges that folks use to put in their signature lines to demonstrate how clever they thought they were through obfuscation.
Clever is bad. Clever opens up a whole universe of unexpected behavior and potential vulnerabilities. Maybe that's why #Rust became so organically popular - because it's safe by design and nowadays it's included in the Linux kernel more and more.
When you're designing software for missle guidance systems you most certainly do not want clever. The job is simple and ambiguity is potentially catastrophic in warfare.
Anyway, I really enjoyed this interview, I can identify with the #Timex_Sinclair - my dad bought me one and that membrane keyboard was horrendous, but I was persistent and eventually I was writing code in cutting edge languages on mainframes and #Vaxen.
Many of the stories about how one thing or another came about were through frustrations; like the impetus for #Linus the #Linux kernel coz #MINIX just didn't cut it, and who wants to trodge through snow drifts in #Helsinki to the computer lab when you can be warm and cozy, drinking beers in your dorm room?
This story is kinda like that too, which I can really appreciate, even though I've never played with #Scala.
I hope you enjoy it too.
https://www.artima.com/articles/the-origins-of-scala
#tallship #FOSS #Modula_2 #Modula_3
⛵
-
Modula-2, UCSD P-System, and the birth of Scala
I stumbled across this tidbit from Hacker News.
I never liked that #Borland stuffs. And used to program in #Pascal in #UCSD P-system (my alma mater). When I got to the US Department of Defense they wanted me for my #C and #COBOL skills and then they sent me to an Air Force School where I studied Modula-2 and Ada.
I did a lot of work in Modula-2, which doesn't exist anymore. Modula-3 does, but in the meantime Scala was in the works. #Ada is still actually a thing. We didn't want clever, like those one liner #Perl challenges that folks use to put in their signature lines to demonstrate how clever they thought they were through obfuscation.
Clever is bad. Clever opens up a whole universe of unexpected behavior and potential vulnerabilities. Maybe that's why #Rust became so organically popular - because it's safe by design and nowadays it's included in the Linux kernel more and more.
When you're designing software for missle guidance systems you most certainly do not want clever. The job is simple and ambiguity is potentially catastrophic in warfare.
Anyway, I really enjoyed this interview, I can identify with the #Timex_Sinclair - my dad bought me one and that membrane keyboard was horrendous, but I was persistent and eventually I was writing code in cutting edge languages on mainframes and #Vaxen.
Many of the stories about how one thing or another came about were through frustrations; like the impetus for #Linus the #Linux kernel coz #MINIX just didn't cut it, and who wants to trodge through snow drifts in #Helsinki to the computer lab when you can be warm and cozy, drinking beers in your dorm room?
This story is kinda like that too, which I can really appreciate, even though I've never played with #Scala.
I hope you enjoy it too.
https://www.artima.com/articles/the-origins-of-scala
#tallship #FOSS #Modula_2 #Modula_3
⛵
-
Modula-2, UCSD P-System, and the birth of Scala
I stumbled across this tidbit from Hacker News.
I never liked that #Borland stuffs. And used to program in #Pascal in #UCSD P-system (my alma mater). When I got to the US Department of Defense they wanted me for my #C and #COBOL skills and then they sent me to an Air Force School where I studied Modula-2 and Ada.
I did a lot of work in Modula-2, which doesn't exist anymore. Modula-3 does, but in the meantime Scala was in the works. #Ada is still actually a thing. We didn't want clever, like those one liner #Perl challenges that folks use to put in their signature lines to demonstrate how clever they thought they were through obfuscation.
Clever is bad. Clever opens up a whole universe of unexpected behavior and potential vulnerabilities. Maybe that's why #Rust became so organically popular - because it's safe by design and nowadays it's included in the Linux kernel more and more.
When you're designing software for missle guidance systems you most certainly do not want clever. The job is simple and ambiguity is potentially catastrophic in warfare.
Anyway, I really enjoyed this interview, I can identify with the #Timex_Sinclair - my dad bought me one and that membrane keyboard was horrendous, but I was persistent and eventually I was writing code in cutting edge languages on mainframes and #Vaxen.
Many of the stories about how one thing or another came about were through frustrations; like the impetus for #Linus the #Linux kernel coz #MINIX just didn't cut it, and who wants to trodge through snow drifts in #Helsinki to the computer lab when you can be warm and cozy, drinking beers in your dorm room?
This story is kinda like that too, which I can really appreciate, even though I've never played with #Scala.
I hope you enjoy it too.
https://www.artima.com/articles/the-origins-of-scala
#tallship #FOSS #Modula_2 #Modula_3
⛵
-
Backports
This time for #Hams...
Yup, #Radio_Amateurs, I thought I'd share a little treasure trove with you all, as I figure many may not be aware of just how vast this resource is.
The Digital Library of Amateur Radio and Communications #DLARC
Their description:
The Digital Library of Amateur Radio and Communications is a library of materials and collections related to amateur radio and early communications. The DLARC is funded by a significant grant from Amateur Radio Digital Communications, a private foundation, to create a digital library that documents, preserves, and provides open access to the history of this community..
As an added bonus, I've included a huge archive link for thousands upon thousands of manuals for just about any electronic device you can think of, from the Manuals Plus Collection that was rescued when that company went out of business a couple of years back.
- Feel free to boost for the benefit of your fellow Hams and electronics hobbyists 🔩 ⚡ 📻
Enjoy!
#tallship #Ham_Radio #Manuals_Plus_Collection
⛵
-
Backports
This time for #Hams...
Yup, #Radio_Amateurs, I thought I'd share a little treasure trove with you all, as I figure many may not be aware of just how vast this resource is.
The Digital Library of Amateur Radio and Communications #DLARC
Their description:
The Digital Library of Amateur Radio and Communications is a library of materials and collections related to amateur radio and early communications. The DLARC is funded by a significant grant from Amateur Radio Digital Communications, a private foundation, to create a digital library that documents, preserves, and provides open access to the history of this community..
As an added bonus, I've included a huge archive link for thousands upon thousands of manuals for just about any electronic device you can think of, from the Manuals Plus Collection that was rescued when that company went out of business a couple of years back.
- Feel free to boost for the benefit of your fellow Hams and electronics hobbyists 🔩 ⚡ 📻
Enjoy!
#tallship #Ham_Radio #Manuals_Plus_Collection
⛵
-
Backports
This time for #Hams...
Yup, #Radio_Amateurs, I thought I'd share a little treasure trove with you all, as I figure many may not be aware of just how vast this resource is.
The Digital Library of Amateur Radio and Communications #DLARC
Their description:
The Digital Library of Amateur Radio and Communications is a library of materials and collections related to amateur radio and early communications. The DLARC is funded by a significant grant from Amateur Radio Digital Communications, a private foundation, to create a digital library that documents, preserves, and provides open access to the history of this community..
As an added bonus, I've included a huge archive link for thousands upon thousands of manuals for just about any electronic device you can think of, from the Manuals Plus Collection that was rescued when that company went out of business a couple of years back.
- Feel free to boost for the benefit of your fellow Hams and electronics hobbyists 🔩 ⚡ 📻
Enjoy!
#tallship #Ham_Radio #Manuals_Plus_Collection
⛵
-
Backports
A couple kids from Berkeley and a dream. That’s where it started."
Her utterance there, well that might be the understatement of the year.
"By porting it to the X86 processor, a proprietary academic testbed system only accessible to institutions and government became, in a moment, the means for any talented programmer to implement their ideas and expand their horizons."
~Lynne Jolitz, 14 July 2025
And there you are reading this, sitting there on your Android, or laptop running BSD or Linux, and what a feat that is. How wonderful it is to take all of that for granted, yet 33 years ago it was merely a vision of what could be, until Bill and Lynne smashed all doubt and a wonderful revolution exploded, unfolding into everyone's home, and indeed, even their hip pockets!
She offers some perspective on that HERE.
#tallship #FOSS #UNIX #Jolix #CSRC #80386
⛵
.
-
Backports
A couple kids from Berkeley and a dream. That’s where it started."
Her utterance there, well that might be the understatement of the year.
"By porting it to the X86 processor, a proprietary academic testbed system only accessible to institutions and government became, in a moment, the means for any talented programmer to implement their ideas and expand their horizons."
~Lynne Jolitz, 14 July 2025
And there you are reading this, sitting there on your Android, or laptop running BSD or Linux, and what a feat that is. How wonderful it is to take all of that for granted, yet 33 years ago it was merely a vision of what could be, until Bill and Lynne smashed all doubt and a wonderful revolution exploded, unfolding into everyone's home, and indeed, even their hip pockets!
She offers some perspective on that HERE.
#tallship #FOSS #UNIX #Jolix #CSRC #80386
⛵
.
-
Backports
A couple kids from Berkeley and a dream. That’s where it started."
Her utterance there, well that might be the understatement of the year.
"By porting it to the X86 processor, a proprietary academic testbed system only accessible to institutions and government became, in a moment, the means for any talented programmer to implement their ideas and expand their horizons."
~Lynne Jolitz, 14 July 2025
And there you are reading this, sitting there on your Android, or laptop running BSD or Linux, and what a feat that is. How wonderful it is to take all of that for granted, yet 33 years ago it was merely a vision of what could be, until Bill and Lynne smashed all doubt and a wonderful revolution exploded, unfolding into everyone's home, and indeed, even their hip pockets!
She offers some perspective on that HERE.
#tallship #FOSS #UNIX #Jolix #CSRC #80386
⛵
.
-
Ente completes CERN sponsored audit
This includes (especially so) Ente Auth.
I wanted to bring some awareness to this because when I think of MFA I typically think of TOTP Authenticators. Like my friend Eric Hameleers (alienbob), I bent the knee way back and adopted the proprietary, closed source product Authy by Twilio.
Why? Because there were considerations to raise, such as, "What if I drop my phone in the fricken' toilet?", or, "I want my authenticator to support installs on multiple platforms and sync" - Actually, both of those considerations are really the same thing. The mess about this really was that Google Authenticator and others didn't sync, existed on a single device, and I had no need or desire to enjoy passwordless authentication offered by Microsoft for some resources.
Authy provided multi-devices w/sync, on #Android, #Linux, and #Windows, okay I guess, and my phone(s). And then Ente Auth came out, they were working on the desktop version and close to a release, it sync'ed with multiple devices and second best of all, it was the first truly cross-platform (Okay I never tried running it on a BSD) authenticator - it could sync between a Linux box and a Windows desktop and an Android - that's everything in my Universe, and actually, who cares about Windows anyway?
Just about that time, as I started considering the move, Twilio informed everyone that Authy support on Desktop was going Bye Bye!
So the choice at that point was Easy Peasy - migrate nowwwww!!! And so I fired up my rarely used wYnd0z3 box and got an alert - "This desktop version will be retired soon, you need to update to the lastest version as soon as possible"... in so many words.
Hmmm... Yeah, I dunno. I think I'mma do some online searches, this sounds fishy to me. And oh boy did it stink to high heaven. I'm glad I checked that out and found a little blurb (over on Reddit, IIRC) that covered the steps required to export everything, a script, a hacked up patch, and voila! done - got it!
There was one caveat there, for those who ventured into those same murky waters that I had - DO NOT APPLY THE TWILIO UPDATE!!!* For those who did, they found out quickly that the a patch no longer worked, they could not perform the export, and this was by design since the export had to be performed on a desktop version of Authy, effectively subjugating the non-daring with the typical enshittification that we've always known as #Vendor_Lockin.
By the time Eric apparently got around to making the move to #Ente_Auth from #Authy, the laborious process was entirely manual - one site at a time, which you can READ ABOUT HERE.
You really gotta watch these sneaky proprietary types of folks.
So anyway, fast forward a bit to where we are now, and although I mentioned my second fav reason to select Ente Auth, I didn't disclose my fav - which should be obvious: It's #FOSS. And not just that, but #Self_Hosted FOSS, if you prefer to keep things close to your breast.
Anyway, that's the backstory and the long way around my announcement here that you an read up on the Audit of all Ente products here:
https://ente.io/blog/cern-audit/
So, IMNSHO, There's really no reason to choose another authenticator, really, truly, there just isn't.
I hope that helps. Enjoy!
⛵
.
-
Ente completes CERN sponsored audit
This includes (especially so) Ente Auth.
I wanted to bring some awareness to this because when I think of MFA I typically think of TOTP Authenticators. Like my friend Eric Hameleers (alienbob), I bent the knee way back and adopted the proprietary, closed source product Authy by Twilio.
Why? Because there were considerations to raise, such as, "What if I drop my phone in the fricken' toilet?", or, "I want my authenticator to support installs on multiple platforms and sync" - Actually, both of those considerations are really the same thing. The mess about this really was that Google Authenticator and others didn't sync, existed on a single device, and I had no need or desire to enjoy passwordless authentication offered by Microsoft for some resources.
Authy provided multi-devices w/sync, on #Android, #Linux, and #Windows, okay I guess, and my phone(s). And then Ente Auth came out, they were working on the desktop version and close to a release, it sync'ed with multiple devices and second best of all, it was the first truly cross-platform (Okay I never tried running it on a BSD) authenticator - it could sync between a Linux box and a Windows desktop and an Android - that's everything in my Universe, and actually, who cares about Windows anyway?
Just about that time, as I started considering the move, Twilio informed everyone that Authy support on Desktop was going Bye Bye!
So the choice at that point was Easy Peasy - migrate nowwwww!!! And so I fired up my rarely used wYnd0z3 box and got an alert - "This desktop version will be retired soon, you need to update to the lastest version as soon as possible"... in so many words.
Hmmm... Yeah, I dunno. I think I'mma do some online searches, this sounds fishy to me. And oh boy did it stink to high heaven. I'm glad I checked that out and found a little blurb (over on Reddit, IIRC) that covered the steps required to export everything, a script, a hacked up patch, and voila! done - got it!
There was one caveat there, for those who ventured into those same murky waters that I had - DO NOT APPLY THE TWILIO UPDATE!!!* For those who did, they found out quickly that the a patch no longer worked, they could not perform the export, and this was by design since the export had to be performed on a desktop version of Authy, effectively subjugating the non-daring with the typical enshittification that we've always known as #Vendor_Lockin.
By the time Eric apparently got around to making the move to #Ente_Auth from #Authy, the laborious process was entirely manual - one site at a time, which you can READ ABOUT HERE.
You really gotta watch these sneaky proprietary types of folks.
So anyway, fast forward a bit to where we are now, and although I mentioned my second fav reason to select Ente Auth, I didn't disclose my fav - which should be obvious: It's #FOSS. And not just that, but #Self_Hosted FOSS, if you prefer to keep things close to your breast.
Anyway, that's the backstory and the long way around my announcement here that you an read up on the Audit of all Ente products here:
https://ente.io/blog/cern-audit/
So, IMNSHO, There's really no reason to choose another authenticator, really, truly, there just isn't.
I hope that helps. Enjoy!
⛵
.
-
Ente completes CERN sponsored audit
This includes (especially so) Ente Auth.
I wanted to bring some awareness to this because when I think of MFA I typically think of TOTP Authenticators. Like my friend Eric Hameleers (alienbob), I bent the knee way back and adopted the proprietary, closed source product Authy by Twilio.
Why? Because there were considerations to raise, such as, "What if I drop my phone in the fricken' toilet?", or, "I want my authenticator to support installs on multiple platforms and sync" - Actually, both of those considerations are really the same thing. The mess about this really was that Google Authenticator and others didn't sync, existed on a single device, and I had no need or desire to enjoy passwordless authentication offered by Microsoft for some resources.
Authy provided multi-devices w/sync, on #Android, #Linux, and #Windows, okay I guess, and my phone(s). And then Ente Auth came out, they were working on the desktop version and close to a release, it sync'ed with multiple devices and second best of all, it was the first truly cross-platform (Okay I never tried running it on a BSD) authenticator - it could sync between a Linux box and a Windows desktop and an Android - that's everything in my Universe, and actually, who cares about Windows anyway?
Just about that time, as I started considering the move, Twilio informed everyone that Authy support on Desktop was going Bye Bye!
So the choice at that point was Easy Peasy - migrate nowwwww!!! And so I fired up my rarely used wYnd0z3 box and got an alert - "This desktop version will be retired soon, you need to update to the lastest version as soon as possible"... in so many words.
Hmmm... Yeah, I dunno. I think I'mma do some online searches, this sounds fishy to me. And oh boy did it stink to high heaven. I'm glad I checked that out and found a little blurb (over on Reddit, IIRC) that covered the steps required to export everything, a script, a hacked up patch, and voila! done - got it!
There was one caveat there, for those who ventured into those same murky waters that I had - DO NOT APPLY THE TWILIO UPDATE!!!* For those who did, they found out quickly that the a patch no longer worked, they could not perform the export, and this was by design since the export had to be performed on a desktop version of Authy, effectively subjugating the non-daring with the typical enshittification that we've always known as #Vendor_Lockin.
By the time Eric apparently got around to making the move to #Ente_Auth from #Authy, the laborious process was entirely manual - one site at a time, which you can READ ABOUT HERE.
You really gotta watch these sneaky proprietary types of folks.
So anyway, fast forward a bit to where we are now, and although I mentioned my second fav reason to select Ente Auth, I didn't disclose my fav - which should be obvious: It's #FOSS. And not just that, but #Self_Hosted FOSS, if you prefer to keep things close to your breast.
Anyway, that's the backstory and the long way around my announcement here that you an read up on the Audit of all Ente products here:
https://ente.io/blog/cern-audit/
So, IMNSHO, There's really no reason to choose another authenticator, really, truly, there just isn't.
I hope that helps. Enjoy!
⛵
.
-
Backports
“BREACH OF PROMISE SUIT EXPECTED MR. HERMAN TYPEE OMOO MELVILLE has recently been united in lawful wedlock to a young lady of Boston. The fair forsaken FAYAWAY will doubtless console herself by suing him."
~The Daily Tribune, 07 August 1847Perhaps not the most complimentary wedding congratulation a newspaper could have bestowed Elizabeth Shaw.
#tallship #literature #adventurers
⛵
.
-
Backports
“BREACH OF PROMISE SUIT EXPECTED MR. HERMAN TYPEE OMOO MELVILLE has recently been united in lawful wedlock to a young lady of Boston. The fair forsaken FAYAWAY will doubtless console herself by suing him."
~The Daily Tribune, 07 August 1847Perhaps not the most complimentary wedding congratulation a newspaper could have bestowed Elizabeth Shaw.
#tallship #literature #adventurers
⛵
.
-
Backports
“BREACH OF PROMISE SUIT EXPECTED MR. HERMAN TYPEE OMOO MELVILLE has recently been united in lawful wedlock to a young lady of Boston. The fair forsaken FAYAWAY will doubtless console herself by suing him."
~The Daily Tribune, 07 August 1847Perhaps not the most complimentary wedding congratulation a newspaper could have bestowed Elizabeth Shaw.
#tallship #literature #adventurers
⛵
.
-
Lies, lies, lies - You lie!!!
There's no freaking way that it could be as much fun as the Whiskey a GoGo on the #Sunset_Strip in 1980! Or where you could go for the aftermath gatherings at Danny's Dog's AKA "Oki-Dog's on Pico Blvd, where vomit, and loogie, encrusted punkers gathered about, sharing slightly edible food with other homeless runaways and comparing bragging rights as to whom should win the evening award for the punker that got beat up the worst that night.
I'm sorry, but there's just no way in hades that Threads can compare to the nightly melee of West Hollywood life in the late 70's through the mid-80's.
But nice try. We get the picture. It's a Faceplant (Meta) property that isn't worth allowing into one's #Fediverse streams. Thanks for taking that bullet for the team :) Darby Crash would be proud of you.
#tallship #punk_rock #Whiskey_a_GoGo #Hollywood #Oki_Dogs
⛵
-
Burning Down TLS Certificate Management?
About 7 months ago, Joe Thompson was a presenter at SCaLE and gave a talk on his proposal to reform of the management of #TLS certificates because, according to him, "disaster looms".
The video of his discussion on the topic, along with his paper (in PDF) on his plan on how to achieve this goal (that he says we need to take seriously NOW), can be found HERE.
Let us know your thoughts on the matter and what ideas you have, or just how critical his ominous omen might be.
#tallship #FOSS #certificate_management
⛵
-
This is indeed an abomination in not just terms of the globally environmental scale of such waste, but also an economic disaster of a magnitude that is massive.
400 million Linux and BSD machines available for $20 - $40 each, or perhaps through volunteer programs to provide free computers to those in need.
It is antithetical to the planned software obsolescence model Microsoft has embraced, a paradigm learned from that of Apple with their program of planned hardware obsolescence.
I just posted on how communities unwittingly banded together in standardizing software in the business marketplace through the act of personal software piracy, and how there's little point to willingly submit to subjugation by the proprietary, closed source software publisher market when there's virtually nothing one cannot do just as well, if not better, with #FOSS.
https://public.mitra.social/post/0199e4fc-02e7-0dcb-1857-64fc59d903be
That is how we FIX a broken software model. The way we FIX a broken hardware model is through the legislation of strict and powerful
Right to Repairlaws.I'm not sure how prevalent such laws are throughout the world or the jurisdictions they extend these common sense options to the consumer, but even considering that many folks won't actually fix their own equipment, many will, and further, small independant (and unaffiliated) shops unencumbered with official, expensive certifications will spring up to service their local communities. We have some pretty strong #Right_to_Repair laws in California and Oregon, markets that have opened up the rest of the nation with those same opportunities through the requirements they bring (long-term parts availability, etc.).
#tallship #recycle_reuse_repair #FOSS
⛵
.
RE: https://mastodon.social/users/iFixit/statuses/115374647198059236
-
Try roasting beets, whole or cut up, on the BBQ grill or in the oven on a cookie sheet.
I like to cut them in half or quarters on the BBQ or into irregular slightly smaller pieces in the oven (six to eight pieces per large beet), and season accordingly to your preference - I prefer a little salt and some savory seasonings like thyme, marjoram, basil, or oregano. Steak and asada seasonings are good too, and mixing whatever you season it with in a measuring cup with EVOO a bit of balsamic vinegar is typically how I mix those seasonings. Then stir and apply with a brush.
Don't be afraid to let them char a bit for character, again, to your preference of taste. When finished, they should be tender and melt away in your mouth.
Some folks aren't into the flavor of olive oil, but don't fret! melted tallow or lard works just as well, better even, for crispiness on the outside, without any intrusive flavors - but please don't use any seed oils, that defeats the purpose of eating healthy. These beets are still delicious this way even if you don't baste them with anything or even season them at all.
You can thank me later, or invite me to your next backyard BBQ.
#tallship #foodpr0n #beets #roasted_beets
⛵
.
-
## First steps towards Raspberry Pi5 support
### Stuart Winter's latest announcement on 05 Oct on the official Linux ARM port:
Using the new SAIR (Slackware AArch64 Installer Respin) tool, I created a variant of the Slackware AArch64 Installer that uses the Raspberry Pi Kernel fork instead of the upstream Linus Torvalds kernel. To test it, I installed Slackware onto a Raspberry Pi 4, and it worked — a big milestone! 🎉 Why the Pi 4? Because I don’t yet have an RPi5, but this gives me a way to get the core pieces working now so that we’ll be ready to integrate full support for the Raspberry Pi 5 as soon as I can test on real hardware. This is just the beginning, but it’s an exciting step forward. Thanks so much for your support.
If you're interested in a fully supported rolling distro for your production rPi home or office network you can track development following the Changelog HERE
Installation guides and video tutorials for rPi4 installation (including a rather comprehensive hardware guide) are located HERE and complete instructions for installation on other popular product lines such as Pine64 as well can be found HERE.
Stuart and Brent work hard at bringing the very leading edge of computing to the ARM architecture and #Slackware_Linux rides the cusp of that endeavor with their dedication and commitment to the single board computer market.
For your next #Raspberry_Pi project, consider the simple yet sleek and performant stability that Slackware Linux has been famous for since it was first distributed around campus at Moorehead State University on floppy disks over 30 years ago, predating Debian, Redhat, and every other Linux distribution in the marketplace.
As for me? Well, it says so in most of my profiles: "Slackware, OpenBSD, and a bit of a Debiantard." And that about sums it up for now!
### A bit on source based and rolling Linux distributions:
- Slackware -current, like Debian testing, Gentoo, and Arch Linux, is a fully rolling Linux distribution. A single command provides complete system updates to the very latest in versioning of packages and ongoing, active development.
- Unlike most other package based distributions, Slackware linux 'can be' a completely sourced based Linux distro, albeit a mostly inconvenient and rather redundant effort, since a single command can fetch and reinstall every single component of the base system (once initial installation of the machine has been completed), due to Slackware's uniquely historical, and simplistic methodology.
- Almost all additional packages not already in the official Slackware installation, with exception of a few very large and intensive applications, are #source_based installs, also capable of being fetched, downloaded from the upstream developer source repos, compiled, packaged, and installed locally (including dependencies) - with a single command. Some packages such as Firefox, LibreOffice, etc., are so huge that trusted package repos are maintained so they can be downloaded, and then installed in seconds with a single command.
- Once you have installed applications, you can share those packages with others freely so they can merely take those packages and install them in a few seconds with a single command. It is however, preferred by most to use the SlackBuilds.org repository for #Slackbuild scripts to compile and install from source (it's a trust issue).
- Slackware Linux is the oldest, extant Linux distro, and has maintained an aggressive, continuous development cycle since its initial public announcement on Usenet in 1993. The Slackware Team has also traditionally provided the longest running support for release versions over that of all Linux distributions (over a decade before EOL in many cases).I hope that helps, enjoy!