tallship @tallship@mastodon.sdf.org

Oh I found this really amusing...

Okay back story. I'm a Longtime L.A. County Underwater Instructor. It's a rather elite organization originally founded by a couple of L.A. County lifeguards back in the 50's.

When I went through the program to be awarded those credentials, elder (so to speak) UICC members would come and give siminars, and one of them when I went through the program was a gentleman by the name of Nick Acorns. He's probably long since passed, but he was high up in a fledgling company at the time called Pelican products (They made plastic diving gear - like flashlights).

Fast forward to today, and Pelican Products are a huge supplier of durable plastic cases for the movie and music industry, law enforcement, and pretty much everyone who wants a watertight and indestructible case for their guns, as well as diving products.

So, I grew up in Torrance, where the company is headquartered, and I just stumbled across this article from Engadget. I litterally could not stop laughing, because I remember a few times that the Torrance or Redondo cops drew their 4 D-Cell Mag-Lites on me as a kid, which any intelligent being knows it is time to shut up and comply with whatever the cops are telling you to do....

Or spend the night in the ER.

That's the lead-in to this funny as fuck story (article) from April 2007 for anyone who has ever been the focus of why a cop drew their aluminum Mag-Lite's from their holster lolz.....

"It's kind of sad when one of the main features being touted by the LAPD about its new flashlights is their inability to provide suspects with a good beating, but after that very public 2004 incident in which a motorist took 11 blows from a heavy 'torch,' we guess the new model's light weight is indeed an important selling point. The 10,000 Pelican 7060's that officers will soon begin carrying -- specifically designed for the department of Rodney King fame -- sport two separate power switches, a no-slip 'grenade grip,' cooling fins on the shaft, and 130 lumen LEDs that are said to be capable of momentarily blinding a non-compliant individual. Sounds like good news for criminals and the falsely-accused, but maybe not so great for that cop in the direct path of a raging meth-head; in those situations, we'd take the cold hard steel aluminum of our four D battery MagLite over a wimpy Pelican any day of the week."

For those who would like to read the complete article, here it is:

https://www.engadget.com/2007-04-02-lapds-blinding-new-flashlights-too-light-to-beat-suspects.html

#tallship #Vger #flashlight #LAPD #Pelican #funny #humor

⛵

.

#OpenMediaVault 6.0 was released a few hours ago this afternoon:

https://forum.openmediavault.org/index.php?thread/39490-install-omv6-on-debian-11-bullseye/

Yes, #Bullseye!

Incidentally, #Debian 10.10 was also released today (#Buster).

You can install OMV via the script above on a fresh install of Bullseye or d/l the OMV 6.0 iso and install from a bootable USB stick or DVD.

I've never been a fan of file based mass storage, so I've never really had much interest in #NAS, but it does well for cheap, small home based networks where folks like to keep collections of movies or other data mounted via NFS or #CIFS (#SAMBA) shares, and you can buy little network attached NAS boxes for cheap from your favorite consumer vendors.

#NFS itself is nice, and I make regular use of it, but why bother with an appliance when you can just enable that on a host directly and say, keep your #rsync replicated data or #Duplicity backups and #snapshots there?

Instead, coming from the big machine room environments with raised flooring and surrounded by a wall of glass, I look to the #SAN instead.

Because this is block based instead of file based, you can run a SAN on very little RAM w/o impact, and #OMV fits this bill quite nicely!

I've saved many enterprises over the years hundreds of thousands of dollars simply by rejecting exorbitantly priced Dell's EMC and of course the ever ubiquitous #NetApp appliances (among many others) in favor of deploying OMV in the datacenter with the native #iSCSI SAN plugin.

If you do this, please do not neglect to contribute to Volker - he does this for free and was one of the original dev's for the FreeNAS project. Im glad he decided to bring that expertise to Debian GNU/Linux as the base distro of choice for OpenMediaVault.

Prior to my having adopted OMV when it first launched, I used #OpenFiler.com which is a fantastic product - except for one thing, it's subscription based and nowadays the only non CE (Their terminology for "Commercial Edition", rather than what everyone else dubs, 'community edition') version is a little old and unsupported. It's very much a commercial and non community supported project and so I was very glad when they were making the transition and #Volker announced the very first release of OMV.

Yes, this version is a so-called preview, the 5.x branch had an update a couple of weeks ago.

I can't recommend OpenMediaVault enough, and it's also quite capable of managing things like #Portainer and #Nginx_Proxy_Manager along with all of the daemon's and services you would want to be forward facing services.

#tallship #Vger #FOSS #OpenSource #Open_Source @OpenSource @opensource
You can haz #Cheezburgerz!

⛵

.

Okay it seems South Korean Crown Prince Andrew Lee is still up to his shenanigans. Now he's directly hijacked the FSF?

Here's the update letter from the FSF on the matter (the initial announcement went out a couple of days ago and now freenode has hijacked FSF assets there):

<snip>
"Following our announcement of a planned gradual switch from the Freenode IRC network to Libera.Chat, Freenode staff, with no notice, seized control of the #fsf and #gnu channels away from FSF staff and GNU volunteers during the early hours of Sunday morning (EDT). This happened despite members of Freenode staff participating in the community meeting, as well as reassuring us publicly and privately that they would respect and support the resulting review and our decision. These channels were seized without informing the FSF or GNU representatives of any disagreements Freenode staff had with our plan, whether by means of the group contact system or otherwise. Adding to the situation's instability was their switch to a new IRC daemon late last night, also without notice, which dropped all existing nicks and channels from the database.

This has forced us to adjust our plans for the transition, a move that was already necessary due to an abrupt change in Freenode policy that occurred shortly after our announcement, which eliminated the distinction between # and ## channels that we planned to use to pass ownership of the #fsf and #gnu channels over to the wider free software community.

After several additional meetings of the working group FSF and GNU formed to investigate this issue, we announce the following changes:

The #fsf and #gnu channels on the Freenode network are to be considered unofficial and will not be moderated by FSF staff or GNU volunteers.

So as not to mislead users, who might otherwise think that the #fsf and #gnu channels on Freenode are the official channels for our organizations, the irc.gnu.org alias is being retired effective immediately. Instead, it is now pointed at a server of ours that will give notice of our migration to the Libera.Chat network to IRC clients that attempt to connect to it.

In light of these events, we would like to reiterate our call for GNU maintainers to move their channels away from the Freenode network, whether to a self-hosted server, alternate IRC networks such as Hackint or Libera.Chat, or other networks that fit the criteria we devised for our decision. Once again, GNU maintainers who have any concerns about their channels are encouraged to email maintainers@gnu.org with their questions.

In freedom,

Greg Farough
Campaigns Manager"
</snip>

The web version is here:
https://www.fsf.org/news/update-to-the-fsf-and-gnus-plan-to-move-irc-channels-to-libera.chat

So.... it appears to me at least, that freenode should now be considered a highly volitile and hostile network that should be avoided at all costs.

What are you thoughts on the matter, in light of the the preceding announcement update above by the FSF?

#tallship #Vger #freenode #andrew_lee #hijackers

:sailboat:

.

Two gin-scented tears trickled down the sides of his nose. But it was all right, everything was all right, the struggle was finished. He had won the victory over himself. He loved Big Brother.

https://gary.vger.cloud/videos/watch/80892852-b99b-483b-b6fe-42e1d5e6a4e7

#tallship #Vger #dystopia #subjugation #privacy

⛵

.

He was in the public dock, confessing everything, implicating everybody. He was walking down the white-tiled corridor, with the feeling of walking in sunlight, and an armed guard at his back. The longhoped-for bullet was entering his brain.

https://gary.vger.cloud/videos/watch/790f614c-8578-4b8f-8e40-727b1a042f20

#tallship #Vger #dystopia #privacy #subjugation

⛵

.

Think you're free? Wrong answer, think again!

https://www.cbc.ca/news/canada/manitoba/maxime-bernier-manitoba-taken-into-custody-1.6062801

#tallship #Vger #privacy #liberty #subjugation #persecution #despotism #dystopia

⛵

.

@koyu

Coming up on my second anniversary with Gemini soon. Vger's come a long way from an experimental space to full community services and I rarely even bother to scan the ML very often, except to catch up on the introduction of new innovations, of which there are more and more each week!

I don't think that we need to do anything further to, "...make #gemini attractive to the average person." Considering most of it's growth and adoption have occurred organically, simple plugs here and there or links (gemini://lin.ks) to content w/o explanation are pretty much all any advocates, such as ourselves should really need in order to whet the appetite of folks - "uh.... what's that? It's a link. What is Gemini? I'mma google that and see what all this excitement is all about".

Curiosity, IMO, has done more for folks to embrace this young technology and protocol than any amount of ground pounding or pontification could achieve, I think, but there are some considerations that we can lean upon as ambassadors of good will for Gemini that might be counterintuitive for many of us:

1.) I like #Elpher, and no, I'm a Vim person, but it's my goto Gemini (and Gopher) browser, because it handles gopher:// and gemini:// equally well, especially with respect to dumping raw page text and refreshes, it's just easy from an analysts point of view. But this is beyond what one can reasonably expect for the target audience to have their interest piqued where Gemini is concerned.

Many folks in the actual community prefer cli clients or slightly more souped up solutions like #Bombadillo that frankly, would leave, as you put it, "...the average person" disinterested. On my part, that includes Elpher (Yeah, "the average person" is a #wYNd0z3 user - try getting them to install #Emacs on a win10 machine and then explain Melpa to them.... you'll get that fisheye glaze every time).

So clients like #LaGrange (https://github.com/skyjake/lagrange/releases/v1.4.2) are exceedingly important to the sphere of adoption in Gemini space - the "average user" has been almost continually, categorically dismissed IMO, as someone that this new protocol is for, but it's not, when you look at most of the client software available that many of us use - yet it is actually specifically for them in more ways than it is for us that have been running Gemini servers since the very beginning - a chance for them to take a break from the overwhelmingly frustrating anxiousness they are entreated to when participating in the world of silo's - i.e., Faceplant, InstaSPAM, Twatter, etc.

Lagrange, and a couple of others, affords these average users the ability to just click, download, doubleclick, then click next/next/next, and Voila, a beautiful experience in their familiar browser-esque experience is presented.

2.) Having been a longtime member of the Gopher world, runnning gopher services almost continually since one of the few places you could find it was in a public library replacing physical card catalogs, a lot of my colleagues there express openly, some not unjustified level of enmity towards Gemini, and although this is understandably so, I feel it is unwarranted and due mostly to misconceptions, or perhaps even because no one has ever really reached out to the Gopher community with actual invitations or suggestions from that elder and more mature community of us.

Indeed, many of us, and initially most of us, actually did rally around what was for me at least, a more contemporary (and dare I say familiar?) syntax for authoring content and inserting links in pages, delving into the project at an early stage. Some I think, are a bit wary that regardless of #Solderpunk's declaration that Gemini, "...will not replace either", is arguably an ominous caveat that it may actually erode some of the relevance that at least Gopher has enjoyed during its resurgence in popularity during the last decade.

Not just that, but also that Gemini exited the gate with the specification that it would use TLS by default - something that we in the #Gopher community had bantered about over the years with proposals followed by repeated tabling of such initiatives. Yet now, #TLS is well supported (depending upon your server daemon of choice) by Gopher as too, seamlessly, transparently for those who choose to implement it, and also depending upon your choice of client as a user.

Outreach to the Gopher community, and embracing this lineage that Gemini has with Gopher, is important, and while on the surface it may not appear as if this is essential to adoption of Gemini by "the average user", I believe it is, because the "average user should be aware that with many clients such as #Lagrange and Elpher, among others, they essentially share the same similar support in the name space as relevant and viable services which "the average user" can visit - perhaps not even aware that clicking on a couple of links has brought them from Gopher space to Gemini space and back again.

I'll leave that point to be pondered, and move along...

3.) We can make Gemini attractive to "#the_average_user" by encouraging the developers of Gopher clients to include support for Gemini in their most excellent and existing products. Gopher clients like:

* #Dooble: https://github.com/textbrowser/dooble/releases/tag/2021.02.20 - a native Gopher enabled browser which is also a good HTML browser in its own right.

* #Gopher_Browser_for_Windows: http://www.mattowen.co.uk/gopher/gopher-client-browser-for-windows

* #Simple_Gopher_Client: Available in the Windows Store

* #Pocket_Gopher (Android): Available at F-Droid (https://f-droid.org/en/packages/com.gmail.afonsotrepa.pocketgopher/) and similarly, encouraging support for Gopher in Android Gemini clients such as #Ariane (https://f-droid.org/en/packages/oppen.gemini.ariane/)

And several other great Gopher clients.

4.) We can make Gemini attractive to "the average user" by encouraging *some* authors of #Gemini clients to include support for inline images - this will prove to be, without a doubt, a **dealbreaker** for many folks - these "average users" want, and indeed *expect* to see at least simple .jpg and .png pics while surfing, without requiring the use and understanding of how to launch external apps that, of course, are better suited to handle such tasks. Launching a .pdf viewer is one thing, but they really expect to be able to see inline images (and nothing in the spec even discourages that with respect to Gemini clients).

5.) Now this is controversial, and I do understand it is my own contention, one which I've advocated for on the Gopher list for well over a decade now, but...

Block HTML to Gemini proxy services (even though robots.txt is clearly defined in the spec, I'm not aware of ANY proxy services that respect it - I've checked) - if you want people to populate a space, make them participate in that space, instead of looking into the fishbowl from the convenience of Google Chrome! nuff said there - you make up your own mind how you feel about allowing a proxy, but I block them, categorically. You want Gopher and Gemini content and software that can only be found on my servers, then you need to use an actual client that can natively surf that portion of the name space.

To further incentivize the adoption of clients that natively access Gemini name space, make sure to publish unique content - duplicating what one has already published, or will soon publish on some arbitrary #WordPress site defeats the purpose of even expecting that "the average user" should do anything different than they already are.

7.) Nothing.... nothing at all. Don't do anything else, except talk about how kewl
it is for you and your friends and colleagues; just letting the curiosity of those who keep hearing how totally bitchen Gemini is do all the work until they say, "man, I gotta check this foshizzles out coz everybody's doin' it."

That's how #Myspace did it, that's now #Faceplant did it, that's how #SnapTrap and #TicTac did it, and that's how #InstaSPAM did it - It's the, "All my friends are there" factor of gaining #critical_mass.

8.) Use Gemini yourself - the proverbial, plural youze :)

9.) This one's a bit controversial too: [Continue to] Post links (without explanation) to content you've published in Gemini space on popular social media platforms in the privacy disrespecting, closed source, monolithic silos where the multitudes of captive users are currently engaged in the self-deprecating acts of the abdication of their freedoms.

10.) Disregarding the relevance of registering #port_1965 with #IANA or seeking fame by authoring an #RFC (and most certainly, at least for the next year or two) - those are almost completely irrelevant issues in this day and age when critical mass is everything, and mere folly for the sake of one's own vanity (at least, for the current time being). I left that as the last point because it encourages not the act of doing something to further the aims of the mass adoption of Gemini as a relevant and utilized computing platform, but rather, NOT doing something to avoid the disruption of what can only be stated as the unexpected and overwhelming embrace by a growing community of early adopters.

And already, that's how Gemini is achieving that already enjoyed level of rapid adoption :)

Yeah, just let nature takes its course, so to speak.

I hope that helps!

⛵

.

#tallship #Vger #1965 #fdroid
Ed_White_First_American_Spacewa…

#Wake_the_fuck_up people!!!

All hail the great #Faceplant :P

I would love to hear what happens to anyone who dares to repost those graphics to their Faceplant or #InstaSPAM pages Muahahaha!

If you do, let us know, m'kay?

https://gizmodo.com/signal-tried-to-run-the-most-honest-facebook-ad-campaig-1846823457

There's plenty of viable de-centralized social and communications platforms (secure too) that shield you from such instrusive raping of your most private secrets, and even what you publicly expound.

#Epicyon, #Pleroma, #Friendica, #Lemmy, #Misskey, #Diaspora, #movim, #matrix, #XMPP, #GNU_Social #Writefreely #jujeune #planetary (#scuttlebutt), and even using your own email services in defiance of what the great Spamming Google gmail engine virtually demands that you not do; are all very viable and privacy respecting opportunities to meet and make new friends, acquaintances, and forge business relationships with others who you'll know are already concerned with privacy respecting communications technologies.

I'll just let that, and the previous advertisements that exposed the private information about people using InstaSPAM and Faceplant users speak for itself.

Kudo's to #Moxie_Marlinspike - You go girl :)

#tallship #Vger #privacy #security #tracking #you_are_the_product

⛵

.

​
2021-05-05 14.36.40 gizmodo.com…

​
2021-05-05 14.37.04 gizmodo.com…

​
2021-05-05 14.37.23 gizmodo.com…

​
2021-05-05 14.36.07 gizmodo.com…

GET THE #FLOC OUTTA HERE!!!!

I mean, even the term, "Cohorts"... don't you think that sounds kinda ominous?

A friend sent me this **All in One** cheat sheet link, and I encourage everyone to incorporate it and avail themselves of it:

https://paramdeo.com/blog/opting-your-website-out-of-googles-floc-network

Already, #Vivaldi said recently this is a no-go for their browser - keep an eye on your preferred #browser to see how respecting of your privacy they are.

#tallship #Vger #security #privacy #advertising #spyware #tracking #evil

⛵

.

Okay I got my notification yesterday from #Debian and #Slackware, and I bit my tongue for a day on this one, because it is potentially so catastrophic. I migrated all of my Exim servers to Postfix and good ole Sendmail quite a few years back.

Now that the news itself is in the wild I'll link to an article:

https://dailyuknews.com/tech/21-nails-in-exim-mail-server-vulnerabilities-enable-full-remote-unauthenticated-code-execution-millions-of-servers-at-risk/

#tallship #Vger #security #vul #MTA #exim @OpenSource

Please patch your boxes yesterday, if not sooner, and make sure you subscribe to ALL security lists for the software you run, m'kay?

⛵

.

@dheadshot @eric @OpenSource

Yes, and let's not forget Microsoft who, last time I checked (going out on a limb here) got about $6 for every single Android sold - due to their Patent trolling.

A humorous aside, "/e/", aside from being a pain in the ass to search on as a term, if you ask a Ham Radio operator, will tell you that it can be correctly pronounced:

"Marky Mark" :P

Boom Shakalaka!

You Git (sic) Nuthin'! Now go pound sand :P

https://boingboing.net/2021/04/29/signals-response-to-fbis-grand-jury-subpoena-for-user-data-you-get-nothing-you-lose-good-day-sir.html

#tallship #Vger #privacy #signal #security #communications #e2e
#DHS, You no can haz #Cheezburgerz! 🍔

⛵

.

For consideration by the privacy conscious folks out there, tired off being raped wholesale by the Google silos...

Before I begin this little phone rant, haber you read the great news about #Vivaldi categorically rejecting Google's latest insidious advertising scheme? I wonder if #Firefox will need able to resist? They get a lot of their dev money from Google y'know 🤘😎🤘

Okay then... What are some kewl choices that help protect your privacy where phones are concerned?

There's https://puri.sm/products/librem-5/ it's got physical switches to turn off the cellular radio and can even be completely removed and replaced (for a different IMSI - not to be confused with #IMEI which is tied to the SIM).

The battery is removable as well - w00t !! So not even the NSA can turn your phone on remotely lolz, and it will accept a whopper 2TB Micro-SD.

Do you ever lie awake in bed at night wondering why you can't get a phone with a removable battery?

I don't either anymore!

There are other physical kill switches that can turn off GPS, Wifi radio, and the mic/camera.

Imagine that though... Changing out your #IMSI in less than a minute without changing your OS or three configs for your installed applications! That's the one thing you can NEVER change on any other phone - meaning, there's no such thing as a #burner_phone (meaning, swapping out SIM cards is pointless) and anyone who thinks so.... OkayI'll be nice (I'm practicing being family friendly.... at least part of the time). But now there is a true burner phone, you quite literally can swap that puppy out Easy Peasy!

There's also the Pine Phone:
https://www.pine64.org/pinephone/

The #Pine_Phone is privacy respecting in the sense that it isn't actually an Android by any measure at all, but rather, a handheld Linux computer (pick your distro, I prefer #Slackware or #Debian). It can also function as a phone secondarily. I use a small #Bluetooth keyboard that can switch between three devices, and that would be a really handy setup for this er... phone, right? ;) Or you can use a full sized wireless combo keyboard/mouse and monitor for a #Linux box that fits in your pocket when you walk away from your desk.

Do you need it to do something really special? Tell me, what can't you do with a real Linux machine? Okay, you can't chop 🪓 🪵 wood or do laundry.

Really though, how kewl is that???

Neither are the best of any world though, but they are best in breed IMNSHO.

Let's look at pure #Android solutions now, k?

For #ROMs I prefer #CalixOS:
https://calyxos.org/
https://invidious.fdn.fr/watch?v=jdazCQemwqQ&local=true

A de-googled #Pixel 3 XL with 128GBytes of storage is a pretty good and inexpensive platform for this which your can pick up all over #eBay for really cheap

It uses the #Aurora repo/store for closed source proprietary software (so you're de-googled) and of course you use F-Droid to install #FOSS or get the #APKs directly from the devs at their #Git repos (best way for some software, like #Fair_Email, for example).

There's also #GrapheneOS (https://grapheneos.org/), and it has a lot of supporters, but I don't find it as performant as CalixOS. Both are, however, fantastic.

Here's a tidbit about the so-called #MiFi pucks that you're entitled to when you're a member of the #Calix Institute... You're listed as Calyx Institute to the broadband provider - only you and the #Calyx_Institute know your identity because it's on their bill lolz, and that's kept secret and has never been compromised, because they maintain an active warrant canary. 🐦 So if you use one of those and a #Librem_5 with the cellular radio turned off or removed, and using your own #Asterisk server for #VoIP, you're truly just an IP addy surfing the internet while you're talking on the phone.

Of course... You'll need to do all this without your Candy 🍬 Crush. But... There's always APKPure in conjunction with #NetGuard from F-Droid 😉

I hope that helps! Please feel free to share this around with a #boost to raise awareness that, well... All is not lost, and #damn_the_torpedos!

And remember, you can haz #Cheezburgerz! 🍔

#tallship #Vger #OpenSource @OpenSource @eric

⛵

.

@Aeron

Aside from not being aware of what "vfv" refers to, I concur wholeheartedly.

I basically believe that anyone worth interfacing with will reside in a place where it's safe (not a great choice of a word, but for lack of a better term it will suffice) for me to interact online.

I also believe that abandonment of non-privacy respecting monolithic silos as a practice, while at the same time participating and publishing in an environment that is primarily #FOSS based, and privacy respecting. For social systems a distributed model that federates with other independently operated instances, I see it as a critical mass building event - When others see that they're missing out and want to belong somewhere (the reason they stay at #FacePlant, #Twatter, and #InstaSPAM in the first place), they will come.

In the meantime, I've got plenty of friends, associates and colleagues to keep me occupied so I know I'm not missing out on anything - **ESPECIALLY** because I existed online back when the only connection methods were through the use of 300 BAUD acoustic couplers. So anything more advanced than that and a Z80 or 8080 on an S-100 Bus is a total win for me lolz :)

Not to imply that we need to trick people, but getting back to that whole Zoom bullshit, If I'm going to have a video meeting conference, what I do is tell people and either send the invite from my NexCloud calendar or via direct email. I tell them, "Hey at such and such time we're doing a video conference and here's the link :)"

"Oh! We're doing a Zoom call? Cool!"

I say nothing. Let them think whatev...

They don't know the difference from one URL to another anyway, and then when they land, they invariably say, "Wow this is really neat, where did you come across this?" As if it's something novel lolz.

BBB and Jitsi have a zero learning curve onboarding, the average, naïve user simply needs to click the link and then following the event they now have that in their vocabulary.

#tallship #Vger

⛵

.
bbb.png

@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

⛵

.

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…