#tallship — Public Fediverse posts

Chatrie v. United States

Police officers conducted a Fourth Amendment search when they acquired Okello Chatrie’s location data from Google because an individual has a reasonable expectation of privacy in his cellphone location information.

But is that really the case? Sure, your phone's location data, and (in this country at least) a reasonable expectation of privacy, and that would presumably include cellular data the carriers have.

But does it really include location data that Mr Chatrie sold (bartered, traded in kind for access to network services instead of being charged directly for them) to Google, #Amazon, Faceplant, and other companies who buy ( with the right to resell in exchange for the privilege of utilizing their network services) this data - specifically to sell this privacy mined data to other third party aggregators and.... wait for it.... presumably those who either are, or would sell it to law enforcement agencies on the open market?

Lemme break that down into the crux of the biscuit. Faceplant, InstaSpam, TakToe, Google, Amazon, and others, buy your privacy in a transaction that includes your access to their services - that's the fee for using Faceplant (You know it's not free).

Most of those companies are built wholly, or in part, on this form of legally privacy mining you (in exchange for you using their services). That's how you pay for access to their services. They, in turn, sell that data for operating costs of their business product and hopefully make a profit by doing so.

That sure sounds like consensual sex to me!

So, what's the difference between selling your privacy mined data to other aggregators, for advertising, whatev, and law enforcement?

Don't get me wrong, I think that both notions are atrocious injustices:

- selling your privacy to have access to their network
- Selling that privacy mined data to law enforcement

Let's not church it up here folks - You went to the crossroads, just like Robert Johnson and sold your eternal soul so you could post stupid pictures of yourself on InstaSpam. You literally paid #Meta for network access and the use of their products (InstaSpam and FacePlant and Wassup). You litterally paid google for access to and the use of Google Docs and Gmail and YouTube, gDrive, Etc., (Wait for it...) by giving them permission over the ownership of a certain amount of your personal data (location, posts, private emails, documents saved on Google infra, etc.).

And you wanna know what's wrong with them providing law enforcement with this info.... without a warrant? Umm... Because you sold it to them so they could sell it to others on the open market!!!.

Now, I think there could be distinctions between just handing over data without an actual warrant, and selling that data to law enforcement. The former sounds like infringement of rights while the latter sounds perfectly reasonable to me - both resulting in the exact same disclosure of (potentially) your most private secrets.

But the facts of the matter are that you literally sold them the rights to distribute this information about you in the free marketplace!

"You got this ad because you're a teacher, but more importantly you're a Leo (and single). This ad used your location to see you're in Moscow. You like to support sketch comedy, and this ad thinks you do drag,"

Ew that must've stung!

Once upon a time you could just track virtually anyone's location on Faceplant in real time, but when some people started complaining and there were concerns about potential stalkers, they began shoring this up - first, with Opt-out, but eventually, just removing that capability from the platform for all intents and purposes.... sort of.

There are plenty of companies who publish their AUPs and ToS's explaining that under no circumstances will they divulge shit about you without a legally compelling warrant - further, many of these sites/companies often also publish a Warrant Canary. None of these businesses are of the stature that rises to the level of a #Big_Tech stature.

Here's a bit more on the topic of Warrant Canaries. And another #Warrant_Canary example is HERE.

Now, let's not get all upset about an innocent person being persecuted - Okello Chatrie is a fricken' bank robber who walked into and robbed a credit union in Virginia on the 20th of May in 2019.

If you read through that opinion, you may get the impression that the damming information was cellular data - but I don't believe that's the case; rather, I believe it was GPS data that Alphabet (aka Google) collects with your permission, as a condition agreed to so that you can use Google stuffs. You may say 'same difference', but if it was Geolocation based on GPS data that Google collected from his phone (rather than cellular data provided by the cellular carrier that was his provider), that's an important distinction (Besides, Neither T-Mobile nor Verizon are mentioned).

Anyway, he's a despicable scumbag to be sure, but did he give permission for Google to sell that information to other parties as a result of Google's consent for him to gain access to Googles services? After all, Google paid for the right to do so (when he sold his soul).

Where the distinction becomes relevant, as I see it, oh.... wait... disclaimer (IANAL). There, let's move along, in lay terms, coz I'm a lay person. Anyway, as I see it, Google didn't actually [legally] sell this information to a third party, namely the FBI and other law enforcement agencies - They provided under the terms of a warrant that was issued demanding that it be provided.

That might be nit-picking to some, but I think that's a HUGE distinction. Further, had the cops come to Google and asked if they would sell his geolocation data to them, I believe that it may have been a perfectly acceptable and legal transaction - after all, he did sell his privacy rights at the cross-roads.

But this was a judicial warrant, and the information was subpoena'd (I'm reaching here with the nomenclature, but you get the gist of what I'm saying here.

For a warrant demanding the information, he had a reasonable expectation of privacy. For the sale of the disclosure of information privacy farmed in his Google account for these very purposes, the sale would have, or rather might have, been perfectly legal.

I dunno. I'm interested in your take on this.

So, did the #InstaSpam users have an expectation of privacy to keep #Signal from publishing their private information? Nope! Because that data was legitimately purchased from #Faceplant (Meta, Whatev).

On the other hand, was the same data that law enforcement could have presumably legally purchased from #Google, but chose instead to acquire by court order, substantively any different due to the method they incorporated to secure that data?

Was this a subtle difference? Because I could buy that data from Google if I wanted to, right? Was it just because it was #law_enforcement?

In closing, again, I reiterate that #IANAL but it seems to me that there sure are a lot of crux in that biscuit.

#tallship #privacy_mining #privacy #industrial_surveillance #Supreme_Court

⛵

Assholes Will Always Exist

Over the years they've been called a lot of things. Some of the terms, these miscreants actually donned like a cape or wore the disparaging noun as a badge of honor:

- #cracker
- #list_bully
- #foreign_agent
- #incel
- #phishermen
- #spammer
- #blackhat

The list is truly, much too long to collate in a single fly by topical mention; and that's really not the point of what I'm writing about here either. What is absolutely pernicious, is the #MiTM style attack on software distribution rising to a level where even the source cannot be held in high confidence.

When these atrocious acts become the commonplace verbs to the infamous nouns above it is time that each and every one of us stand vigil and at the ready to come to the aid of our community members. Here's one such place where we can begin - the #AUR: https://archlinux.org/news/active-aur-malicious-packages-incident/

#tallship #FOSS #malware

⛵

@tedu

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

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

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

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

Welcome to the club of unhappilly disenfranchised #NIC_handles 😥

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

Backport Wisdom

"The reason is that they don’t buy the IBM answer as the only answer. The saying in the US is “nobody ever got fired for picking IBM.” That’s not a saying in Europe."
~Doug Michels, January 1987

#tallship #Microtimes #SCO #Logica #IBM #XENIX

⛵

.

#Tallship #Astrid salvaged from outside #oysterhaven to Kinsale, it's original destination.

Today, 12 years ago

#coast #corkCoast #coCork #westCork #WildAtlanticWay #kinsale #cork #speirGorm #irishBlueSky #mastodaoine
Pics KG

Today, 2007, Prince William @ Old Head of Kinsale

#coast #corkCoast #coCork #westCork #WildAtlanticWay #kinsale #cork #speirGorm #irishBlueSky #mastodaoine #tallship

Pic: kg

#Kinsale today, 2014, at Charles Fort
Jeanie Johnson famine #TallShip

#coast #corkCoast #coCork #westCork #WildAtlanticWay #kinsale #cork #speirGorm #irishBlueSky #mastodaoine #CharlesFort #JeanieJohnson #famineShip

Pics kg

Letzte Meile zur PEKING ab 30. März • Last mile to PEKING
🪢💨🌊⚓️❤️ 🛟
#peking #viermastbark #fourmastedbarque #flyingpliner #pliner #windjammer #tallship #großsegler #capehorn #kaphoorn #clipper #steelhulled #hamborgerveermaster #seemannsgarn #hafenmuseumhamburg #schuppen50 #deutscheshafenmuseum #hamburg #RQTD #pekingfreunde #viermastbarkpeking #pekinghamburg #peking1911 #freundederviermastbarkpeking

New Design: Belay Pins, Pinrail, and Rope lines – Tall Ship Amerigo Vespucci Prints and More [Shopping]

Available exclusively from
DouglasEWelch.com/shop/724

See my entire catalog
DouglasEWelch.com/shop/

#belay #belaypins #pinrail #ropes #lines #ship #boat #barca #tallship #ocean #sea #ropes #rigging #mast #antique #history #nautical #seagoing #sailing #sky #italy #italia #italian #nave #products #gifts #cards#clothing #arts #crafts #technology #iphone #samsung #cases #bags #totes #prints #home #housewares #tops #journals #pillows #clocks #mugs

New Design: Tall Ship Amerigo Vespucci - Broadside Prints and More [Shopping]

Available exclusively from
DouglasEWelch.com/shop/722

See my entire catalog
DouglasEWelch.com/shop/

#ship #boat #barca #tallship #ocean #sea #ropes #rigging #mast #antique #history #nautical #seagoing #sailing #sky #italy #italia #italian #nave #products #gifts #cards#clothing #arts #crafts #technology #iphone #samsung #cases #bags #totes #prints #home #housewares #tops #journals #pillows #clocks #mugs

Have you ever received an HTTP 418 status code while browsing? If so, it may be because you were trying to put a square peg in a round hole, or vice versa.

Indeed, RFC 2324 Lays out the specification, and Oopsies! It turns out that an April Fools joke was canonized, albeit with some utility. Turns out, even if someone's not trying to pull your leg, by telling you "I'm a Teapot", it's likely you're gently being encouraged to look for a resource other than the way in which you're asking.

For example, you ask for a coffeemaker and receive the error, HTTP 418 (I'm a Teapot). It's certainly nicer that a 404 and yet indicates that there is content where the page you've just asked for exists.

This is in some ways a concern that many have dug their heels in over, clinging as intransigent as ever when it comes to #tmpfs discussions beginning twelve years ago on the #Debian Dev list.

Often, in practice, cron is used to clean out unneeded clutter in /tmp or /var/tmp, as well as other methods. An issue I have is with the systemd defaults including /var/tmp in tmpfs on some implementations because temporary files here are intended to be persistent across reboots.

By default, systemd cleans out files in /var/tmp by default after 30 days, and this can be problematic, while the default is 10 days for /tmp. /var/run and /var/lock are also Incorporated - But I digress.

After well over a decade, about half of the major Linux distros have migrated to tmpfs: Arch, Fedora, and some versions of SuSE number among the most familiar. Others have not: Redhat, SLES, and other "Enterprise" focused distros, along with Debian, ... Until just recently, when much to my surprise during routine updates I noticed the switch to tmpfs has now occurred.

w00t 🤘🤠🤘

With respect to Slackware, does it use the traditional disk based method or the RAM based tmpfs? The answer to that of course, is "Yes, of course, it absolutely does!"

"Which one did you say?" I actually didn't, lolz. As is usually the case with Slackware (and Arch and Gentoo), it's really however you want it!

In Slackware, the implementation is much more elegant however. You simply mount /tmp on a ramdisk (again, leave /var/tmp alone - these files are intended to be persistent across reboots, and for possibly much, much longer than a mere 30 days).

Okay so back to Debian. If you're one of those fraidy cats that doesn't believe, or rather, isn't competent or confident enough to run Enterprise production machines on rolling distros, I've got good news for you! You won't be needing to concern yourself with this until Debian 13 is officially released or you're forced to upgrade to it in the next few years. Lucky you!

For the rest of us however, already running #Trixie, it has indeed arrived. Welcome! Here's the problems...

You may, depending on what daemons you run in production, want to tweak your defaults. i.e., 10 days may be less than appropriate for your company's needs. Remember, #cron is your friend. It's also why Slackware's approach was referred to as elegant, because you have to take into account what it is you want or need before you implement it.

For example, since you already know that you don't want temp files to survive reboots in /tmp, there's really nothing faster than disk space residing in RAM anyway.

On the other hand, Poettering doesn't make up the rules for the developers of this world or sysadmins. If you're not careful you can wind up right back on a spinning disk platter again, since the default for #systemd is to allocate 50‰ of your RAM for tmpfs, if you don't have ample memory, you go to SWAP.

Oh, the irony :p

When you're in an HA environment where your UNIX boxes have uptimes exceeding 800+ days, and the only reason to reboot is to install a new kernel, Poettering's 30 day default storage for tempfiles in /var/tmp, or for that matter, a default for files in /var/lock or /var/run, ... is absolutely absurd - this is why we have cron and shell scripts (and Perl/Python).

tl;dr: This is why I started of with that amusing simile about HTTP 418, because if you just trust systemd to hold your hand, you just may find that one of your mission critical Enterprise services informs you that it's been told it's a #Teapot 🫖

That's not a good thing when 5, 500, or 50,000 people expect their shit to just work without ever having to know your name as the person who makes that happen for them.

Disk based storage is the safe bet; that's why #Redhat still does it that way. But it's certainly not the most performant, and requires the steady fingers of a competent systems administrator for the care and feeding of the tmp file systems - otherwise, like so many n00bs have discovered (in the days when hard drives didn't exceed a Gigabyte in capacity), you may wake up one day to find that you've hammered your filesystem, everything is running, but nothing is doing anything it's supposed to be doing - now, rm and du have become your best friends until the moment you discover that rotating your log files and keeping /tmp clean is actually part of your job...

Even as a casual workstation user on your personal laptop. It's your job.

For those interested, here's an example of the systemd defaults for tmps should you wisely consider the beneficial consequences of responsible planning for managing the size of your growing tempfile directories, from the Arch Wiki:

/etc/tmpfiles.d/tmp.conf
# see tmpfiles.d(5)
# always enable /tmp directory cleaning
D! /tmp 1777 root root 0

# remove files in /var/tmp older than 10 days
D /var/tmp 1777 root root 10d

# namespace mountpoints (PrivateTmp=yes) are excluded from removal
x /tmp/systemd-private-*
x /var/tmp/systemd-private-*
X /tmp/systemd-private-*/tmp
X /var/tmp/systemd-private-*/tmp

Umm... 10 days, /var/tmp? IMNSHO, that's maybe just a tad (way more than a tad) aggressive.

Although I've so far only alluded to it, I actually do recommend that you consider removing /var/tmp from any cleanup schedule too, instead using cron and shell scripts, along with a little proactive monitoring to keep that part of your tempfile systems clean.

And remember: "You may be short, and you may be stout, but unless it's April 1st, don't let anyone call you a Teapot." 🫖

For further reading you can checkout the [LWN article here] (https://lwn.net/Articles/975565/?ref=news.itsfoss.com).

As always, feel free to boost and share this with others (sharing is love), and I'm always interested in hearing your thoughts and suggestions in the comments.

I hope that helps. All the best!

#tallship #FOSS #Linux #Slackware #Arch #Gentoo #SuSE #Fedora

⛵

.

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

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

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

#tallship

⛵

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

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

First discovered in 2002, paleontologist draw comparisons of #Dinocephalosaurus_orientalis with other aquatic species having no modern day analogs - why did the entire family of #Tanystropheidae or the genera exhibiting these morphological functionalities not continue?

Perhaps just as interesting is the convergent evolution (especially with respect to their necks) between that of Dinocephalosaurus and members of the Tanystropheus genus. A close resemblance on the surface, yet Dinocephalosaurus orientalis was strictly an aquatic species.

I've included an artists reconstructive rendition of Tanystropheus longobardicus for comparison between the two, but note that Dinocephalosaurus had four flipper-like feet of the same size, and unable to exist, or at least thrive in a terrestrial environment, where Tanystropheus exhibited larger feet in the rear - not unlike your hands being smaller than your feet.

And yes, as Yuki (@youronlyone) offers up as a contemplative inference, the whole "Dragon" and "Loch Ness Monster" corollaries are uncanny, raising questions as to why would pre-industrial societies actually have such fables, or in the case of the latter, claims of sightings, if not rooted in some previous observation by humans?

https://edition.cnn.com/2024/02/23/world/dragon-fossil-240-million-years-old-intl-scli-scn/index.html

Dinocephalosaurus was extant from the late #Paleozoic (late Permian period) through the early #Mesozoic (early Triassic period) eras.

#tallship #Dinocephalosaurus #Triassic #Tanystropheus #Tanystropheus_longobardicus h/t to @youronlyone for bringing the latest news on this matter to me - I'm always fascinated with things related to #marine_biology - especially #Opisthobranchia

⛵️

.

RE: https://c.im/users/youronlyone/statuses/111985758251416307

@youronlyone

Tallship sinks off Oysterhaven near Kinsale, 10 years ago today. Youth sail training vessel, all saved.

Diesel tank accidentally filled with water, engine stalled, too close to shore to sail out of danger.

📷📽️Sinking, salvage & demolition:
https://corkcoast.com/astrid/

#tallShip #rnli #sar #corkCoast #astrid #ircg

#IrishMastodon #CorkMastodon #mastodaoine #Chorcaí #cork #kinsale #wildAtlanticWay #ireland #sailing #sailTraining

@leftout @alex Ummm…. k,

I’mma Trekkie. All my life.

I gotta say thank you and also admit that I’m embarrassed ss a result of spreading that falsehood for prolly two decades. It was based on my direct recollection that our minds shape within us as we add and recall various experiences in life.

Let me take this opportunity to say, “Fuck your therapist” too, for had you cited, S1:E18 TNG I would have been awkwardly embarrassed, outraged at myself, and thought you a dikhed for thrashing me publicly. You are too kind, and a statesman in trekkering (if that’s even a freaking word, lolz).

Because of your subtle pointer, not pointing to the episode itself butt to the provenance of the saga’s chronology, I took your queue and went to the sources at StarTrek .com, Etc., and did my due diligence.

“Home Soil” was in fact the episode with Captain Picard and crew, and Ugly… Ugly giant bags of mostly water was the actual line converted over communication links off the Enterprise obo the:

• Crystal life form (wikis)
• Microbrains (IMDb, but I think this is wrong)
• Crystalline Entity (something from my own recollections, but I think I may be conflating with another episode again)

In the second utterance, where the quote comes from, it’s:

“Ugly bags of mostly water” which is kinda fucked up if you’re the ugly bag and you think you’re the bees knees of the universe, lolz.

Anyway, I need to go back and watch the episode again and regain my clarity.

From one Trekkie to another, thanks for the nudge in the right direction, fuck your therapist (again, cuz your instincts were better than his/hers), and here’s some personal questions, stuffs, I have for you…

My all time fav episodes:

1. The Balance of Terror (S1:E14 TOS - 1966) - Romulan Captain played by the same actor (Mark Lenard) as Sarek in later episodes, series (like TNG), and movies, through s few franchises.
2. The Inner Light - after either ten minutes or a whole lifetime, Picard returns to his cabin to play a flute bestowed upon him by a strange probe of remembrance of a people past, and sadly, extinct - he carries with him their hopes, loves, and dreams, the rest of his natural days, as a complete life experience.
3. Don’t fuck this up coz I’ll gig your ass, lolz - What we’re Captain Kirk’s last words?
4. Another major fav of mine is TNG’s, “Yesterday’s Enterprise” who’s Captain had even more balls than Captain Janeway, who in turn, had more balls than Captain Kirk, lolz.

As my profile and contact info clearly states, I’m a FOSS and Privacy Advocate, shoulder that mantle quite seriously, and even though I thought him initially to be a dweeb write in, came to appreciate Will Wheaton as Wesley Crusher and note that it was not one of our finest hours when we let the destructive child snimals out of their respective cages to drive him from the Fediverse - yeah, I was there when those teenage pieces of shit did that to him - even @Gargron , who held great sway back then, couldn’t contain or filter those 💩’s.

https://www.reddit.com/r/OutOfTheLoop/comments/9bimug/why_did_mastodon_run_off_wil_wheaton/

You have a wonderful day, evening, or afternoon, whatev time it is where you’re at and thanks again for the gentle bump to fact check myself with this errata.

#tallship #Star_Trek #Star_Trek_you_bitches #Kirk #Picard #Janeway #TOS #TNG #humanity #sacrifice #rememberance #conflation #memory #recollection #I_can_haz_Cheezburgerz? 🍔

⛵

.

#deutscheshafenmuseum #schuppen50 #viermastbarkpeking #hamburg
Foto: @jansiegfoto
🪢💨🌊⚓️❤️🛟
#FlyingPLinerHeritageFleet #peking #viermastbark #fourmastedbarque #flyingpliner #pliner #windjammer #tallship #großsegler #capehorn #hamborgerveermaster #seemannsgarn #hafenmuseum #hafenmuseumhamburg #schuppen50 #deutscheshafenmuseum #deham #hamburg #RQTD #pekingfreunde #viermastbarkpeking #pekinghamburg #peking1911 #freundederviermastbarkpeking