tallship @tallship@mastodon.sdf.org
- Finger
- tallship@sdf.org
- Matrix
- #tallship:matrix.org
- Github
- https://github.com/tallship
- PGP Fingerprint
- A0E3 9133 9067 0CCE
On the beaches of Super Sunny Southern California.
(And the remote mountain wilderness of Humboldt)
Slackware, OpenBSD, and a bit of a Debiantard.
#Slackware #Linux #FOSS #openBSD #NetBSD #freeBSD #Debian #ArchLinux #Humboldt #tallship #cheezburgerz
Joined Aug 2019
tallship
boosted
@0 @gdroid
You're very welcome!
And K9 mail is great stuff too.
One thing I would urge you to pay attention to, without going into a whole dissertation, is that with Fair Email, there are basically three versions.
1.) Google Play store - some features may not be present due to Google's rules, plus the whole signing issue I've ranted on over the last couple of days where they can alter your code and redistribute it (ATM, only *new* apps, but later, everyone's)
2.) F-Droid - The dev considers the F-Droid version current if it is the current version at his GitHub repo. There's a couple of particulars to this.
a.) They sign the compiles with their key so some parts are excluded (Google parts for autoconfig, etc., coz Google only allows one key, that of the dev's, to be used in a version that includes their stuff)
b.) Many devs create an F-Droid compatible repo so you can enable that repo and use the dev's compiled version via your F-Droid client for updates, etc. to use those versions, you must first uninstall whichever version you have installed and then install the Dev's F-Droid compatible repo, and pull down from the top of the screen for refreshes, etc., like with any other app.
3.) Most FOSS projects have a Git repo where you can get the APKs directly and install them from their official releases signed with their keys. But Fair Email is different, in that most projects you have to manually install newer versions (Why most devs use an F-Droid repo of their own) - Fair Email's apk checks the dev's GitHub repo for updates and the app can actually update regularly whenever there is a new release directly from the GitHub repo - that's pretty kewl.
Also, remember that the Google features which are crippled/absent/disabled in many of the official F-Droid apps? This version is signed with the dev's creds so all of the Google features are enabled (Like autoconfig of gmail aliases, etc.).... But there's more.
Aspects of the client that aren't permitted to be included in the Google Play Store version can also be included in the GitHub version because not only is it signed with his creds, but also, it's not being distributed from the Google Play Store so like, with other apps where say, OAUTH stuff is taken out, or whatev, such is not the case with this one - i.e., it has everyting, is the most current, automatically checks for updates and installs them if you wish, etc., etc., etc.
So I recommend, at least with this application, installing directly from:
https://github.com/M66B/FairEmail/releases
The latest version, "FairEmail-v1.1554-github-release.apk" a/o the time I'm posting this, was released just 10 hours ago - that coffee's still fresh and hot lolz.
The dev states that the only thing enabled in his version that isn't included in the Play Store version is Android Auto integration....
I dunno about reading email while driving though, that doesn't sound to safe lol.
And I was also under the understanding that the OAuth support for gmail was missing because it wasn't signed with the dev's keys, but perhaps I'm mistaken there?
There is a couple of major things to note, however:
First, uid/pwd access is going away in gmail soon (for GSuite/Google Apps for Business/whatev you wanna call it) - so one must use OAuth to authenticate with their gmail accounts (Like I said, I could swear the F-Droid version *couldn't* have this because they sign with their keys, not the dev's himself)
Second, I strongly recommend that people, in almost all use cases, DO NOT enable Google's "Advanced Protection Program":
https://landing.google.com/advancedprotection/
If you do, not only can you not run third party email apps (this is not just a gmail thing, mind you), there are many applications you won't be able to install and run - it is far reaching with sweeping ramifications.
Anyway, I run the GitHub version and yes, it's an absolute dream!
The home page on the web with lots of kewl screenies and links to many of the resources is here:
https://email.faircode.eu
So my post turned out to be a virtual dissertation anyway. Oh well ;)
@OpenSource #FairEmail #FOSS #OpenSource #tallship #Vger
⛵
.
You're very welcome!
And K9 mail is great stuff too.
One thing I would urge you to pay attention to, without going into a whole dissertation, is that with Fair Email, there are basically three versions.
1.) Google Play store - some features may not be present due to Google's rules, plus the whole signing issue I've ranted on over the last couple of days where they can alter your code and redistribute it (ATM, only *new* apps, but later, everyone's)
2.) F-Droid - The dev considers the F-Droid version current if it is the current version at his GitHub repo. There's a couple of particulars to this.
a.) They sign the compiles with their key so some parts are excluded (Google parts for autoconfig, etc., coz Google only allows one key, that of the dev's, to be used in a version that includes their stuff)
b.) Many devs create an F-Droid compatible repo so you can enable that repo and use the dev's compiled version via your F-Droid client for updates, etc. to use those versions, you must first uninstall whichever version you have installed and then install the Dev's F-Droid compatible repo, and pull down from the top of the screen for refreshes, etc., like with any other app.
3.) Most FOSS projects have a Git repo where you can get the APKs directly and install them from their official releases signed with their keys. But Fair Email is different, in that most projects you have to manually install newer versions (Why most devs use an F-Droid repo of their own) - Fair Email's apk checks the dev's GitHub repo for updates and the app can actually update regularly whenever there is a new release directly from the GitHub repo - that's pretty kewl.
Also, remember that the Google features which are crippled/absent/disabled in many of the official F-Droid apps? This version is signed with the dev's creds so all of the Google features are enabled (Like autoconfig of gmail aliases, etc.).... But there's more.
Aspects of the client that aren't permitted to be included in the Google Play Store version can also be included in the GitHub version because not only is it signed with his creds, but also, it's not being distributed from the Google Play Store so like, with other apps where say, OAUTH stuff is taken out, or whatev, such is not the case with this one - i.e., it has everyting, is the most current, automatically checks for updates and installs them if you wish, etc., etc., etc.
So I recommend, at least with this application, installing directly from:
https://github.com/M66B/FairEmail/releases
The latest version, "FairEmail-v1.1554-github-release.apk" a/o the time I'm posting this, was released just 10 hours ago - that coffee's still fresh and hot lolz.
The dev states that the only thing enabled in his version that isn't included in the Play Store version is Android Auto integration....
I dunno about reading email while driving though, that doesn't sound to safe lol.
And I was also under the understanding that the OAuth support for gmail was missing because it wasn't signed with the dev's keys, but perhaps I'm mistaken there?
There is a couple of major things to note, however:
First, uid/pwd access is going away in gmail soon (for GSuite/Google Apps for Business/whatev you wanna call it) - so one must use OAuth to authenticate with their gmail accounts (Like I said, I could swear the F-Droid version *couldn't* have this because they sign with their keys, not the dev's himself)
Second, I strongly recommend that people, in almost all use cases, DO NOT enable Google's "Advanced Protection Program":
https://landing.google.com/advancedprotection/
If you do, not only can you not run third party email apps (this is not just a gmail thing, mind you), there are many applications you won't be able to install and run - it is far reaching with sweeping ramifications.
Anyway, I run the GitHub version and yes, it's an absolute dream!
The home page on the web with lots of kewl screenies and links to many of the resources is here:
https://email.faircode.eu
So my post turned out to be a virtual dissertation anyway. Oh well ;)
@OpenSource #FairEmail #FOSS #OpenSource #tallship #Vger
⛵
.
tallship
boosted
Well shit howdie!
Reports are starting to trickle in now about how this has actually been in the wild for a while and now folks are experiencing active exploits and being #pwn3d.... Not good, even for a shitty software platform that NO ONE should be using in the first place - What are you thinking?
Le's see... um.... #NextCloud_Talk, #Matrix, #XMPP, #Big_Blue_Button, #Jitsi - there's no shortage of #self_hosted #secure #FOSS solutions so, bottom line:
If you EVER use Zoom, you're a fucking idiot!
#Zoom no can haz #Cheezburgerz 🍔
#tallship #Vger #zoom #rce #vul #exploit
⛵
.
zoom_no_can_haz_cheezburgerz.jp…
Reports are starting to trickle in now about how this has actually been in the wild for a while and now folks are experiencing active exploits and being #pwn3d.... Not good, even for a shitty software platform that NO ONE should be using in the first place - What are you thinking?
Le's see... um.... #NextCloud_Talk, #Matrix, #XMPP, #Big_Blue_Button, #Jitsi - there's no shortage of #self_hosted #secure #FOSS solutions so, bottom line:
If you EVER use Zoom, you're a fucking idiot!
#Zoom no can haz #Cheezburgerz 🍔
#tallship #Vger #zoom #rce #vul #exploit
⛵
.
zoom_no_can_haz_cheezburgerz.jp…
tallship
boosted
@Mastodon @Sujitech_official @lickability I seriously hope accessibility is a priority in the official app. We don't need another Reddit, where blind users *have* to download a third-party app just to use the service well.
tallship
boosted
**Please Boost** :)
#FOSDEM 2021 presentation by #Stephane_Bortzmeyer, the author and maintainer of the #LUPA statistical analysis engine, on #Project_Gemini, it's explosive growth, and in depth demonstration of the origin, utility, and usage of #Gemini_space.
https://gorf.tube/videos/watch/cf88a4cc-1c06-468c-a7db-74b0c3442b64
#tallship #Vger #Gemini You can haz #Cheezburgerz! 🍔
⛵
.
#FOSDEM 2021 presentation by #Stephane_Bortzmeyer, the author and maintainer of the #LUPA statistical analysis engine, on #Project_Gemini, it's explosive growth, and in depth demonstration of the origin, utility, and usage of #Gemini_space.
https://gorf.tube/videos/watch/cf88a4cc-1c06-468c-a7db-74b0c3442b64
#tallship #Vger #Gemini You can haz #Cheezburgerz! 🍔
⛵
.
tallship
boosted
You can learn a lot from a dummy 🤡
#tallship #Vger #kiil_the_crew #They_eat_their_young #you_got_lucky_this_time
⛵
.
randomTemp15565319688559179477.…
#tallship #Vger #kiil_the_crew #They_eat_their_young #you_got_lucky_this_time
⛵
.
randomTemp15565319688559179477.…
tallship
boosted
@oppen
It simply is what it always has been :)
As a longtime solution provider, for decades myself, I learned early on that there really is not so much a notion of *problems*, as there is the, #Opportunity_for_Solutions.
It is what it is, and I'm confident in my belief that you've discovered a new opportunity and can develop a viable solution within the confines of the #Gemini spec.
You can still find folks selling #ASCII art portraits at the local Saturday morning swapmeets - they take your photo and then print a coffee cup, or mousepad, and these files can be further manipulated online, even generating #QR_Codes from the artwork. They were indeed not designed for proportional spacing, and #ANSI art is on the rise again as well.
If nothing else, these ASCII-art headers are a hat tip to a kinder, simpler computing environment, while these screen readers you've mentioned are quite probably an example of dismissive arrogance that condescends from the same lofty perch that the big monolithic silos sit upon, as they beautify the intricately complicated monetization, slaughter, butchering, packaging, and distribution of the target commodity we call people, but they call inventory.
Yup, this same pretty #Dopamine delivery system that actually spawned something like #Project_Gemini in the first place, with its simple plaintext files that beg the acknowledgement of those #ASCII_Art banners - the same ones you see in every #IRC network, #UNIX #MOTD, #Gopher, and #FTP servers around the globe (not to mention the thousands of extant #Echomail based file sharing network systems or the signature line artwork that plaintext based email users incorporate).
If there's indeed a problem here, one might propose that it stems from the lack of regard for the concept of backward compatibility in contemporary tools predicated on, and intended for use in, an environment where the only truly important thing is to facilitate the cannibalistic feeding upon of the users themselves in a market based economy of total consumer consumption.
And I don't mean the consumer consuming, but rather, the consumption of the consumer.
#They_eat_their_young.
There's a lot you can do client side with Ariane I think?
Love your work by the way!
⛵
.
#tallship #Vger #FOSS #1965
randomTemp12093934181916801955.…
It simply is what it always has been :)
As a longtime solution provider, for decades myself, I learned early on that there really is not so much a notion of *problems*, as there is the, #Opportunity_for_Solutions.
It is what it is, and I'm confident in my belief that you've discovered a new opportunity and can develop a viable solution within the confines of the #Gemini spec.
You can still find folks selling #ASCII art portraits at the local Saturday morning swapmeets - they take your photo and then print a coffee cup, or mousepad, and these files can be further manipulated online, even generating #QR_Codes from the artwork. They were indeed not designed for proportional spacing, and #ANSI art is on the rise again as well.
If nothing else, these ASCII-art headers are a hat tip to a kinder, simpler computing environment, while these screen readers you've mentioned are quite probably an example of dismissive arrogance that condescends from the same lofty perch that the big monolithic silos sit upon, as they beautify the intricately complicated monetization, slaughter, butchering, packaging, and distribution of the target commodity we call people, but they call inventory.
Yup, this same pretty #Dopamine delivery system that actually spawned something like #Project_Gemini in the first place, with its simple plaintext files that beg the acknowledgement of those #ASCII_Art banners - the same ones you see in every #IRC network, #UNIX #MOTD, #Gopher, and #FTP servers around the globe (not to mention the thousands of extant #Echomail based file sharing network systems or the signature line artwork that plaintext based email users incorporate).
If there's indeed a problem here, one might propose that it stems from the lack of regard for the concept of backward compatibility in contemporary tools predicated on, and intended for use in, an environment where the only truly important thing is to facilitate the cannibalistic feeding upon of the users themselves in a market based economy of total consumer consumption.
And I don't mean the consumer consuming, but rather, the consumption of the consumer.
#They_eat_their_young.
There's a lot you can do client side with Ariane I think?
Love your work by the way!
⛵
.
#tallship #Vger #FOSS #1965
randomTemp12093934181916801955.…
tallship
boosted
tallship
boosted
Something has been bothering me for a while (years, actually), and it's privacy related in the sense that someone can use a privacy concious search utility like Duck Duck Go or Startpage, and yet still only be handed the sanitized results that meet the objectives of the companies stealing the privacy of individuals in the first place.
It is a zero sum game - you're still packaged and quantified. You're still getting the results that you were bought and paid for in the first place.
Examples:
* You affect a search for a hotel room in some town you plan to visit in a few days. Travelocity and like sites come up, but the bed and breakfast you probably would have chosen is buried on page four of the SERPS. They're also listed in one of the directory services on page one that, if they didn't already pay for, would leave their website buried in oblivion - even though booking directly would cost less than the megaopolis sites that extort them at the peril of being driven into bankruptcy, and never mind the money that they spent on SEO for their own website.
* You do a search for a plumber. That's local to you, right? And even though the plumber had a website, that too is buried under several pages of directory indexers like Yelp - even below their own GMB (Google My Business) page, which of course, is down in page two or three of the #SERPS. Big wealthy plumbing companies with marketing departments dominate Yelp anyway, add have dedicated staff to solicit ratings and okay the rank game with Yelp and other directories, so you never actually reach the vendors that you actually would have chosen.
They get fucked in the ass and so do you.
What if...
There was a #search_service that utilizes something like startpage or DDG , yet filtered out all of those big monolithic motherfuckers that are running the equivalent of modern day #protection_rackets, threatening to crush the Ma & Pa plumbers and motels and other small businesses that no matter what, never will appear on page one of a Google or Bing search?
What technology exists to build this, and how stable and effective might it be?
Your thoughts? Suggestions? Expertise in implementing such a fair and equitable service?
I'd really like to open a dialog about this. We have Nitter, and Yotter, and Invidious, and Bibliogram. These seem to address one aspect of how we are tossed into the chipper and then reconstituted as Soylent Green. It's freaking cannibalism, if you think about it.
So what initiatives, dialogs, discussions, or projects might we be able to deploy with the long range goal being the, #disruption_of_the_corruption as a viable solution?
#Please_boost, and I'm so very interested in hearing your input.
Thanks, and I guess that helps! :)
⛵
.
#tallship #Vger #FOSS #LibreSearch
randomTemp16645347990549432608.…
It is a zero sum game - you're still packaged and quantified. You're still getting the results that you were bought and paid for in the first place.
Examples:
* You affect a search for a hotel room in some town you plan to visit in a few days. Travelocity and like sites come up, but the bed and breakfast you probably would have chosen is buried on page four of the SERPS. They're also listed in one of the directory services on page one that, if they didn't already pay for, would leave their website buried in oblivion - even though booking directly would cost less than the megaopolis sites that extort them at the peril of being driven into bankruptcy, and never mind the money that they spent on SEO for their own website.
* You do a search for a plumber. That's local to you, right? And even though the plumber had a website, that too is buried under several pages of directory indexers like Yelp - even below their own GMB (Google My Business) page, which of course, is down in page two or three of the #SERPS. Big wealthy plumbing companies with marketing departments dominate Yelp anyway, add have dedicated staff to solicit ratings and okay the rank game with Yelp and other directories, so you never actually reach the vendors that you actually would have chosen.
They get fucked in the ass and so do you.
What if...
There was a #search_service that utilizes something like startpage or DDG , yet filtered out all of those big monolithic motherfuckers that are running the equivalent of modern day #protection_rackets, threatening to crush the Ma & Pa plumbers and motels and other small businesses that no matter what, never will appear on page one of a Google or Bing search?
What technology exists to build this, and how stable and effective might it be?
Your thoughts? Suggestions? Expertise in implementing such a fair and equitable service?
I'd really like to open a dialog about this. We have Nitter, and Yotter, and Invidious, and Bibliogram. These seem to address one aspect of how we are tossed into the chipper and then reconstituted as Soylent Green. It's freaking cannibalism, if you think about it.
So what initiatives, dialogs, discussions, or projects might we be able to deploy with the long range goal being the, #disruption_of_the_corruption as a viable solution?
#Please_boost, and I'm so very interested in hearing your input.
Thanks, and I guess that helps! :)
⛵
.
#tallship #Vger #FOSS #LibreSearch
randomTemp16645347990549432608.…
tallship
boosted
tallship
boosted
@marnic
Yah, After Bank Street Writer, MultiMate, and Wordstar, there was #Star_Writer, and #StarOffice was free even before being #OpenSource and then under the tutelage of the Mighty #Sun_Microsystems.
After #Sun was gobbled up by the #Evil_EllisonCo, OOo was going to be hopefully released back to the community, shepherded by the capable defectors of #The_Document_Foundation, but Larry Ellison, being the vindictive dik that he is held the brand hostage until the defectors had rebranded the fork as #LibreOffice, and then, after effectively killing off the #OOo brand, he dumped it like trash on the Apache Foundation, where it languished in their *incubator* until it was all but completely irrelevant.
Long live The Document Foundation; Long live LibreOffice!
⛵
.
@libreoffice
randomTemp14483364695703388503.…
Yah, After Bank Street Writer, MultiMate, and Wordstar, there was #Star_Writer, and #StarOffice was free even before being #OpenSource and then under the tutelage of the Mighty #Sun_Microsystems.
After #Sun was gobbled up by the #Evil_EllisonCo, OOo was going to be hopefully released back to the community, shepherded by the capable defectors of #The_Document_Foundation, but Larry Ellison, being the vindictive dik that he is held the brand hostage until the defectors had rebranded the fork as #LibreOffice, and then, after effectively killing off the #OOo brand, he dumped it like trash on the Apache Foundation, where it languished in their *incubator* until it was all but completely irrelevant.
Long live The Document Foundation; Long live LibreOffice!
⛵
.
@libreoffice
randomTemp14483364695703388503.…
tallship
boosted
With the help of @pixelfed dev, we implemented last missing endpoints for #Fedilab. Thank you @dansup
The beta release should be released in production very soon.
If you use 2FA with #Pixelfed, don't hesitate to give it a try and share your feedback.
If you are a #Fdroid user, you can add our custom repository: https://fdroid.fedilab.app
tallship
boosted
When I first came across "No Support Linux Hosting" a couple of years back, I couldn't stop laughing. 'What a novel idea!', I thought.
On demand, self-managed hosting services usually indicate that the typical tech support response is usually going to be: "Just click that little red button in your control panel and reinstall the OS, and all will be well".
Generally not what the customer was praying to hear.
After all, the responsibility for the management of the machinery ends with that machinery being up and available in a self-managed environment. Anything beyond that, and the customer is entitled to break their machines any way they like - whether on purpose or accidentally.
So the **No Support** branding makes for great marketing, because that's exactly what on demand, self-managed services are anyway (yes, you can elect to pay more for hand holding or even managed services, with some managed services plans meaning you're not allowed to touch your own server).
This story has made it all the way from TorrentFreak to Ziff Davis, highlighting just how pervasive this takedown, and two others, were.
Most providers incorporate active #disaster_recovery plans including #backups and #snapshots of their customer's machinery even if the customer doesn't pay for those additional upsells.
Why? Because if something happens at the infrastructure level it's the provider's responsibility to get things back online ASAP, and if the customer blows something up it presents an opportunity for the provider to come riding in like a knight in shining armor and rescue the irresponsible customer by charging just enough of a shitload of money so their customer's business operations don't entirely fail. A penalty, so to speak, for the customer not electing to subscribe to the #backup or #snapshot services before #disaster struck.
So... Why wasn't that the case here?
Or perhaps, as the article suggests, maybe there was some hidden complicity?
Since there are inferences to #piracy and #copyright violations, one might point out that several emerging technologies and initiatives in the world of file sharing are now exploring, and/or deploying, infrastructure incorporating #IPFS and #blockchain technologies - a possible game changer for Internet #archives and the ability to affect #DMCA takedowns in the future.
So let's break out the bon bons and #popcorn, pick a comfy seat, and settle in to watch how the #plot of this #movie unfolds, shall we?
I hoped that helps! :)
#tallship #Vger You can haz #Cheezburgerz! 🍔
⛵
.
https://www.zdnet.com/article/web-hosting-provider-shuts-down-after-cyber-attack/
randomTemp19077489258024755595.…
On demand, self-managed hosting services usually indicate that the typical tech support response is usually going to be: "Just click that little red button in your control panel and reinstall the OS, and all will be well".
Generally not what the customer was praying to hear.
After all, the responsibility for the management of the machinery ends with that machinery being up and available in a self-managed environment. Anything beyond that, and the customer is entitled to break their machines any way they like - whether on purpose or accidentally.
So the **No Support** branding makes for great marketing, because that's exactly what on demand, self-managed services are anyway (yes, you can elect to pay more for hand holding or even managed services, with some managed services plans meaning you're not allowed to touch your own server).
This story has made it all the way from TorrentFreak to Ziff Davis, highlighting just how pervasive this takedown, and two others, were.
Most providers incorporate active #disaster_recovery plans including #backups and #snapshots of their customer's machinery even if the customer doesn't pay for those additional upsells.
Why? Because if something happens at the infrastructure level it's the provider's responsibility to get things back online ASAP, and if the customer blows something up it presents an opportunity for the provider to come riding in like a knight in shining armor and rescue the irresponsible customer by charging just enough of a shitload of money so their customer's business operations don't entirely fail. A penalty, so to speak, for the customer not electing to subscribe to the #backup or #snapshot services before #disaster struck.
So... Why wasn't that the case here?
Or perhaps, as the article suggests, maybe there was some hidden complicity?
Since there are inferences to #piracy and #copyright violations, one might point out that several emerging technologies and initiatives in the world of file sharing are now exploring, and/or deploying, infrastructure incorporating #IPFS and #blockchain technologies - a possible game changer for Internet #archives and the ability to affect #DMCA takedowns in the future.
So let's break out the bon bons and #popcorn, pick a comfy seat, and settle in to watch how the #plot of this #movie unfolds, shall we?
I hoped that helps! :)
#tallship #Vger You can haz #Cheezburgerz! 🍔
⛵
.
https://www.zdnet.com/article/web-hosting-provider-shuts-down-after-cyber-attack/
randomTemp19077489258024755595.…
tallship
boosted
@kinetix
Nor should you have that need my friend. It'll get patched, and it's a limited #vul anyway.
Screen is real #GNU, but it's had several maintainers and some claim it's a bit of spaghetti code after all these decades.
I originally began my migration to #tmux soon after its release by the #OpenBSD folks and in there beginning used to even remap the keybinding to ^a to mimic #screen, but now, on machines that I use #Byobi on, I map that to ^b to mimic tmux, which is what it's actually built over.
Now, here's something I do that you might be interested in...
http://northtech.us/content/20110311/adding-convenient-layers-persistent-abstraction-simplify-remote-administration
I've been a package maintainer for #TWIN for almost twenty years, and while it pretty much just languished in relative obscurity at #Sourceforge until just a few years ago it has enjoyed a considerable surge in popularity since being rehomed at #GitHub.
I like to use it in its own, regular, virtual Linux console, away from X-Windows, or I'll attach via X-forwarding remotely. That way, I'll just <Ctrl>+<Alt>+Fn# to get out of my local X Server Session, ssh into that box, and attach. I'll tile several TWinTerms inside of which I run my tmux or screen sessions.
You might want to make sure you're running #gpm for your mouse support ;)
You should give it a go. It's fucking fun shit. And do please tell me what you think okay? It's a bit different, and you guys remember coz it was originally written for #DOS in the #386 days, but if you've ever networked DOS to #UNIX machines using #Quarterdeck's #DESQview/X you should be right at home 🚀
Nowadays, development is once again quite active and you can visit the project at GitHub:
https://wikipedia.org/wiki/Twin_(windowing_system)
I hope that helps! :)
⛵
.
#tallship #Vger #FOSS #OpenSource @OpenSource
randomTemp1429581523704907219.p…
Nor should you have that need my friend. It'll get patched, and it's a limited #vul anyway.
Screen is real #GNU, but it's had several maintainers and some claim it's a bit of spaghetti code after all these decades.
I originally began my migration to #tmux soon after its release by the #OpenBSD folks and in there beginning used to even remap the keybinding to ^a to mimic #screen, but now, on machines that I use #Byobi on, I map that to ^b to mimic tmux, which is what it's actually built over.
Now, here's something I do that you might be interested in...
http://northtech.us/content/20110311/adding-convenient-layers-persistent-abstraction-simplify-remote-administration
I've been a package maintainer for #TWIN for almost twenty years, and while it pretty much just languished in relative obscurity at #Sourceforge until just a few years ago it has enjoyed a considerable surge in popularity since being rehomed at #GitHub.
I like to use it in its own, regular, virtual Linux console, away from X-Windows, or I'll attach via X-forwarding remotely. That way, I'll just <Ctrl>+<Alt>+Fn# to get out of my local X Server Session, ssh into that box, and attach. I'll tile several TWinTerms inside of which I run my tmux or screen sessions.
You might want to make sure you're running #gpm for your mouse support ;)
You should give it a go. It's fucking fun shit. And do please tell me what you think okay? It's a bit different, and you guys remember coz it was originally written for #DOS in the #386 days, but if you've ever networked DOS to #UNIX machines using #Quarterdeck's #DESQview/X you should be right at home 🚀
Nowadays, development is once again quite active and you can visit the project at GitHub:
https://wikipedia.org/wiki/Twin_(windowing_system)
I hope that helps! :)
⛵
.
#tallship #Vger #FOSS #OpenSource @OpenSource
randomTemp1429581523704907219.p…
tallship
boosted
Ruh roh!
Everyone uses #tmux instead nowadays anyway, right?
I know, ewb00ntewians use #Byobi and that's actually built on top of tmux anyway, not screen
#screen #vul #vulnerability #irssi #minecraft #irc #tallship #Vger
https://nitter.fdn.fr/taviso/status/1359209259385294850#m
Everyone uses #tmux instead nowadays anyway, right?
I know, ewb00ntewians use #Byobi and that's actually built on top of tmux anyway, not screen
#screen #vul #vulnerability #irssi #minecraft #irc #tallship #Vger
https://nitter.fdn.fr/taviso/status/1359209259385294850#m
tallship
boosted
@garritfra
Hi Grant,
I'm interested in any links you might be able to provide leading to the GPL you think you read, and we'll do what we can to correct this issue.
Why? Because that phrase nor any part of it exists in either version 1.0, 2.0, or 3.0 of the GNU General Public License.
To be clear, I would steer you towards:
https://www.gnu.org/licenses/gpl-3.0.en.html
https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html
https://www.gnu.org/licenses/old-licenses/gpl-1.0.en.html
Those three links are definitive, official texts for all three versions of the license.
Please refer to those texts for future reference.
**Someone has been lying to you**.
I hope that helps! :)
#tallship #Vger #FOSS #FSF #GNU
#GNU's #Not #UNIX
#Free_Software_Foundation
#misinformation #open_source
⛵
.
Hi Grant,
I'm interested in any links you might be able to provide leading to the GPL you think you read, and we'll do what we can to correct this issue.
Why? Because that phrase nor any part of it exists in either version 1.0, 2.0, or 3.0 of the GNU General Public License.
To be clear, I would steer you towards:
https://www.gnu.org/licenses/gpl-3.0.en.html
https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html
https://www.gnu.org/licenses/old-licenses/gpl-1.0.en.html
Those three links are definitive, official texts for all three versions of the license.
Please refer to those texts for future reference.
**Someone has been lying to you**.
I hope that helps! :)
#tallship #Vger #FOSS #FSF #GNU
#GNU's #Not #UNIX
#Free_Software_Foundation
#misinformation #open_source
⛵
.
tallship
boosted
Zerowing - Intro (All Your Base are Belong to Us)
This the Famous intro the Game Zero Wing for the Sega MegaDrive/ Genesis. ALL your base are belong to us.
https://youtu.be/RlrkcE_2DJg
randomTemp18931064785550073565.…
This the Famous intro the Game Zero Wing for the Sega MegaDrive/ Genesis. ALL your base are belong to us.
https://youtu.be/RlrkcE_2DJg
randomTemp18931064785550073565.…
tallship
boosted
OMFG this is so cute!
For those of you who *really* know me, you are already aware that I forgoed medical school, even though I was a shoe in, coz I was informed that I would not be selected for a PhD program in Biological Oceanography at Scripps Institution of Oceanography back when I attended UCSD.
Ling story short, I wanted to count fucking fish, not stitch people up.
And I am still, at heart, a wanna-be Marine Biologist.
And this little ditty I scraped from elsewhere here in the Fediverse just warmed my icy fricken' heart. I want to share it with you now, all of my friends and even my frienemies, and ask if any of you can say that you've never done this yourselves, lolz.
I just wanna bring a bit of love and a smile to your beautiful faces... Truly.
Yah, we're really all just one big happy fucking family, and not so different from one another. Truly!
I hope you enjoy, and that this short video brings a smile to your face and all of your friends that you share this with!
Please boost!
Luvies!
-tallship
⛵
.
#tallship #Vger #Marine_mammals #our_better_half
randomTemp14854482164543259198.…
For those of you who *really* know me, you are already aware that I forgoed medical school, even though I was a shoe in, coz I was informed that I would not be selected for a PhD program in Biological Oceanography at Scripps Institution of Oceanography back when I attended UCSD.
Ling story short, I wanted to count fucking fish, not stitch people up.
And I am still, at heart, a wanna-be Marine Biologist.
And this little ditty I scraped from elsewhere here in the Fediverse just warmed my icy fricken' heart. I want to share it with you now, all of my friends and even my frienemies, and ask if any of you can say that you've never done this yourselves, lolz.
I just wanna bring a bit of love and a smile to your beautiful faces... Truly.
Yah, we're really all just one big happy fucking family, and not so different from one another. Truly!
I hope you enjoy, and that this short video brings a smile to your face and all of your friends that you share this with!
Please boost!
Luvies!
-tallship
⛵
.
#tallship #Vger #Marine_mammals #our_better_half
randomTemp14854482164543259198.…
tallship
boosted
After six very long months for many that have been waiting and hoping, a #Framasoft sponsored project has finally been released in the form of the latest version of #Fedilab (v2.38.1) on F-Droid!
Fedilab, is an #Android client to access the distributed #Fediverse, consisting of social networking platforms including photo sharing and video hosting, blogging aggregation and sharing services.
A couple of really kewl new features become available in this latest stable version, both are really kewl, but only one is actually listed in the release notes, so let's start with that:
* #New_post_notifications are available as a new feature you can elect to implement on a case by case basis, for the accounts you follow. Yet another feature present in most social networks and forum software that has been around for ages and still not implemented on most #Fediverse platforms (it does already exist on #Friendica instances).
*The other major upgrade, although not really a new feature is seamless and triangle #translation_services that facilitate making and maintaining friendships with others worldwide, regardless if there's a common language between parties. This feature was introduced a long time ago and supported exclusively by Fedilab, using the Yandex engines' free services...
Until those free services wetter terminated, and the translation feature languished for much of the last year with an interesting future.
Well, Fedilab has just rebased their language translation services integrating with #Libretranslate, and I must say it's is noted lightning fast and flawless, as much as translations can be anyway 😉
Don't forget to pickup the latest version of Fedilab at F-Droid :)
As an added bonus, you can even stay abreast of the bleeding edge of Fedilab development by enabling their own F-Droid repo where you can obtain the very latest, including beta versions of of Fedilab, and you can do this in just a couple of quick clicks at: https://fdroid.fedilab.app/
I hope that helps! :)
⛵
.
#tallship #Vger #F_Droid #Open_Source #FOSS
@apps @Fedilab
@OpenSource
randomTemp1723219536307995742.p…
Fedilab, is an #Android client to access the distributed #Fediverse, consisting of social networking platforms including photo sharing and video hosting, blogging aggregation and sharing services.
A couple of really kewl new features become available in this latest stable version, both are really kewl, but only one is actually listed in the release notes, so let's start with that:
* #New_post_notifications are available as a new feature you can elect to implement on a case by case basis, for the accounts you follow. Yet another feature present in most social networks and forum software that has been around for ages and still not implemented on most #Fediverse platforms (it does already exist on #Friendica instances).
*The other major upgrade, although not really a new feature is seamless and triangle #translation_services that facilitate making and maintaining friendships with others worldwide, regardless if there's a common language between parties. This feature was introduced a long time ago and supported exclusively by Fedilab, using the Yandex engines' free services...
Until those free services wetter terminated, and the translation feature languished for much of the last year with an interesting future.
Well, Fedilab has just rebased their language translation services integrating with #Libretranslate, and I must say it's is noted lightning fast and flawless, as much as translations can be anyway 😉
Don't forget to pickup the latest version of Fedilab at F-Droid :)
As an added bonus, you can even stay abreast of the bleeding edge of Fedilab development by enabling their own F-Droid repo where you can obtain the very latest, including beta versions of of Fedilab, and you can do this in just a couple of quick clicks at: https://fdroid.fedilab.app/
I hope that helps! :)
⛵
.
#tallship #Vger #F_Droid #Open_Source #FOSS
@apps @Fedilab
@OpenSource
randomTemp1723219536307995742.p…
tallship
boosted
@solene
I would recommend, for you anyway my friend, and in this order...
* Slackware -current (will be the closest to what you're already used to with #OpenBSD). Get familiar with https://sbopkg.org , which supports #queuefiles for dependency resolution, and the underlying source build system at https://slackbiilds.org too.
At the distro layer there is #Slackpkg and Slackpkg+ for maintaining and customizing your OS installation: https://wikipedia.org/wiki/Slackpkg
* #Arch Linux - I can't express how much both n00bs and gurus alike love this distro, with arguably the best supporting documentation available in the Linux world.
* #Gentoo - you should be a bit familiar with this model, although the olden days of starting off from a stage 1 CD image are long since past, yet there's a lot to learn there too that I think you might find interesting, by familiarizing yourself with one of the last truly source based Linux distributions.
And finally...
* #Debian -testing , a bit boring perhaps for you, at least at first, but this will provide you with a great appreciation and understanding for how and why many of the other popular contemporary distros work.
All four recommendations above are, in fact, rolling distros, the maintenance of which in #enterprise_production environments requires a bit more care and attentiveness on the part of you, the #SysAdmin; yet all four are quite suitable for just such production environments in the capable hands of competent staff and run in perpetuity for years - decades even, to be sure. I've got #Slackware servers running enterprises that started off back in Slackware 10 and were installed from a stack of floppy disks.
I know that you are the sort of person who likes to see what makes things tick, so this is my custom recommendation for you.
#tallship #Vger #FOSS #Open_Source #Linux #GNU #X You can haz #Cheezburgerz! 🍔
⛵
.
randomTemp11714226099762207260.…
I would recommend, for you anyway my friend, and in this order...
* Slackware -current (will be the closest to what you're already used to with #OpenBSD). Get familiar with https://sbopkg.org , which supports #queuefiles for dependency resolution, and the underlying source build system at https://slackbiilds.org too.
At the distro layer there is #Slackpkg and Slackpkg+ for maintaining and customizing your OS installation: https://wikipedia.org/wiki/Slackpkg
* #Arch Linux - I can't express how much both n00bs and gurus alike love this distro, with arguably the best supporting documentation available in the Linux world.
* #Gentoo - you should be a bit familiar with this model, although the olden days of starting off from a stage 1 CD image are long since past, yet there's a lot to learn there too that I think you might find interesting, by familiarizing yourself with one of the last truly source based Linux distributions.
And finally...
* #Debian -testing , a bit boring perhaps for you, at least at first, but this will provide you with a great appreciation and understanding for how and why many of the other popular contemporary distros work.
All four recommendations above are, in fact, rolling distros, the maintenance of which in #enterprise_production environments requires a bit more care and attentiveness on the part of you, the #SysAdmin; yet all four are quite suitable for just such production environments in the capable hands of competent staff and run in perpetuity for years - decades even, to be sure. I've got #Slackware servers running enterprises that started off back in Slackware 10 and were installed from a stack of floppy disks.
I know that you are the sort of person who likes to see what makes things tick, so this is my custom recommendation for you.
#tallship #Vger #FOSS #Open_Source #Linux #GNU #X You can haz #Cheezburgerz! 🍔
⛵
.
randomTemp11714226099762207260.…
- Finger
- tallship@sdf.org
- Matrix
- #tallship:matrix.org
- Github
- https://github.com/tallship
- PGP Fingerprint
- A0E3 9133 9067 0CCE
On the beaches of Super Sunny Southern California.
(And the remote mountain wilderness of Humboldt)
Slackware, OpenBSD, and a bit of a Debiantard.
#Slackware #Linux #FOSS #openBSD #NetBSD #freeBSD #Debian #ArchLinux #Humboldt #tallship #cheezburgerz
Joined Aug 2019
