tallship

Slackware, OpenBSD, and a bit of a Debiantard. FOSS and Privacy Advocate.

Soft landings usually mean it doesn't hurt very much at first, then perhaps the event becomes more frequent and escalates to something that looks like the attached screenie...

When this happens, you may wish to avail yourself of some of the alternatives below.

Once you get here you're faced with trying options or even becoming disenfranchised. Switching to another browser is a prudent test, some have suggested pasting links into Incognito Mode tabs or logging out, while others have claimed that stock Brave Browser seems to humming along for them; and third party utils from among the list that follows:

Web based:

Android (both are available at F-Droid):

Desktop:

Browser extension (a native, local, cross-platform solution):

  • AdNauseam This last option is a simple browser extension that is apparently quite popular with folks, levying its own ethical pressure upon those who would force-feed you with data mined ad generation. The README file has some great information on the methodology incorporated.

On #Android, I haven't been presented with any of these foreboding pop ups warning me about blockers. I typically use #Brave or #Vivaldi Browser, they're stock, but I use the YouTube app more than I do any one of my browsers on my phones.

I also run the #DuckDuckGo “App Tracking Protection service”. This is NOT #FOSS, so your choices are either installing from the #Aurora or Google Playstore, yet there's no requirement to use the #DDG browser to enable this protection – it's not for your browsers though (even DDG), it is designed to work with pretty much everything on your Android EXCEPT browsers; i.e., almost all of your installed apps, seamlessly, and since most folks stream YouTube videos through the Google YouTube Android app, I surmise that it targets and obliterates ads in the app (I haven't confirmed the veracity of that, it's merely supposition, but it blocks zillions of attempts by installed apps to phone home).

I'm Looking forward to hearing your thoughts, personal observations, and concerns; other toolsets or applications that meet your needs, and why you may have chosen those particular types of tools.

I hope that helps!

I can be reached on Matrix at:

@tallship:matrix.org

via XMPP at:

tallship@jabber.org

and in the Fediverse at: @tallship@public.mitra.social

#tallship #privacy #Adblock

.

With some frogs and snails and puppy dog tails

I just finished this new Cinnamon post: https://cinnamon.video/watch?v=679173664947569768

Wow, what can I say? I certainly wasn't any sort of proponent for the web-monetization schemes of the past, but oddly enough, following the implosion of freenode, one of the former staff members who helped me to move and get my projects migrated with fully registered status to LiberaChat was a big supporter of Coil.

Coil? What's that? Web monetization? He doesn't seem like the type to embrace some flippant... hm...

I bit down hard, why? Why would he be so head first into yet another plan to disrespect privacy when he was all about the opposite?

So I signed up for Coil – it was kinda weird, with all this convoluted GlobalID thing that you had to navigate and all, which I'm still not convinced of its use case, and there didn't seem to be a way to avoid setting it up without a phone, but it was necessary to bridge the gap to Interledger protocol and I also wanted a kewl Uphold.com account/debit card, and convenient way to spend/receive/send crypto in the process (via XRP).

I found a rag tag website equivalent of those old roomatefinders services, complete with late 90's UX like something out of a 3 day HTML course, and low and behold, a desktop way to do that GlobalID thing and verify with an email address instead of a phone number – Finally!

The Uphold KYC was simple, straight-forward, and predictably modern, and a few minutes later I had what still might end up being a useless GlobalID and a really kewl Debit card from Uphold on its way to me in the mail.

I've used Uphold semi-regularly, and not because I need to, but more of a fun thing, or quick way to move a little crypto onto a card to use at a retail store.

Oh, yeah, and this Coil thing that following a bit of research appeared to have like, maybe ten websites with no market, and that was sad because after reading up quite thoroughly, it really did appear to be a great model in this era of walled gardens in your face every time you click on a newsworthy item in your search results – a phenomenon so offensive that the EFF actually released a plugin to block all walled garden websites from your searches – You go girl! FSF and EFF FTW w00t.

I did the Coil thing on a couple of my sites. Easy enough, add a meta tag and poof! done. Nothing. Sad. A few months go by and same same. Sad.

And so, like so many other novel initiatives that aren't actually predicated upon stealing from you (like Faceplant, Twatter, InstaSPAM, etc.), I forgot about the krufty lines of code in those couple of sites. Someday I'll stumble upon them, rummage through my documentation and go, “Oh yeah, I remember that Coil thing! Too bad it didn't amount to anything.”

And I'll remove the code and forget all about it. Like you've forgotten about the purple gorilla that you couldn't get off of your Windows 98 desktop no matter what you tried to do about it, except for when it didn't want to be there, or Klippy, the dancing paperclip that offered little in the way of actual help – but it was something you could watch when your box labored for more than a seconds trying to open that PowerPoint presentation.

After a while I got into a regular usage cycle just to exercise my Uphold card. Send 10 bucks worth of XRP to it, convert it to cash, and buy a six pack of beer and a candy bar, or fund it with $10 from a credit card real quick so I can send a little XRP to some DEX for a funky trash token that is absurd, and then send those to my friends as goofy gifts to clutter their Tronlink wallets. Nothing especially of real utility, although you could Hodl custodial BTC and a myriad of others and swap 'em into cash really quickly whenever you wanted to go out on a dinner date.

If nothing else, the Uphold card is a good way to siphon off your crypto income from transactions where you sold stuffs to people, put it into an intermediary custodial account and let it sit while you waited for a time to use it as walking around money – without the fuss that some exchanges entail.

I started noticing these tiny, incremental transactions after a while and couldn't glean what was going on though. After a while, they became more frequent. I mean, like a penny or three cents, and pretty soon the pattern emerged to coincide with some articles I had written that had a lot of readership – What? could it be that mainspring thing I deployed months back? What was that called.... Coil! That's it! Coil.com!

It was indeed.

I decided to burrow into a kdbx file and find that interledger stuff that was so irrelevant and grab that meta-tag and begin a little copypasta cuisine. Whoa... Now I've got a pretty steady stream of pennies, nickels dimes, and even quarters coming in all the time....

Hey this is pretty kewl :)

And it actually hasn't been that long. Sometimes a good idea is just a good idea and it has to propagate and age a bit – like a good Kentucky straight bourbon.

Now, I like to write, spread the poison of my warped ethics all around the playground, and edjumacate, and inform, and clarify why I believe a certain way, or prevent someone from making the stupid mistakes I did by explaining how I should have done it.

I didn't write most of those items to cha ching, but there's seriously enough there to buy a sandwich for lunch here and there. I mean, I've written articles and nada, for a long time, and then something happens and it starts getting readership. I dunno why half the time, but here's the deal I'm a big FOSSie, a proponent of the open source model in general, and when I do something I like to doc it, like a good sysadmin, and I also like to clean that up a bit and share that – sometimes even release scripts for other lazy fuckers like me.

I've made part of a career by eradicating Windows and proprietary software in favor of FOSS. Early adopter of Linux, even working with it back in 1992. Whenever I deploy for a business, I make sure the principal knows how much the license would have been had I used Microsoft and other proprietary closed source software, My labor being about the same regardless, they're running free software that is actually better than the encumbered alternative, so I require the customer to donate to the developers or project each year. I never tell the customer how much, I just make it clear the money they would have paid.

I think that's a good ethical approach. So now there's all these people out there unbeknownst to any of us who they actually are, paying five bucks a month just on the off chance they'll land on a web page where someone who writes an article has this FOSS spirit, and now, it's starting to show...

So then everything sat for a while and then, I get a notification that Coil Blogs is being EOLed, and I had to move my existing blogs to Write.as or lose them. I didn't even know I would get a year of free pro service until a few minutes ago.

I also stumbled upon Cinnamon – That's right here where we are now! And of course there's much more.

Pretty much everything I publish is licensed CC-BY-SA 4.0 and so my interledger address I got from Coil and Uphold is used for my HackerNoon and Dev.To writings as well....

Okay stop. How many is that so far? Cinnamon, Write.as, Dev.To, and HackerNoon – all monetized at 36 cents an hour of reading time. That may not sound like a lot, but I've also monetized other infra that I self-host – websites, etc., too numerous to mention at this juncture.

It has all become a way to “Passively monetize my efforts for things I publish that are otherwise free anyway – so people who that money comes from are full on, opt-in, paying 5 bucks a month (never any more than that) to support hundreds of thousands of Coil web monetized sites.

Relatica – the new desktop and mobile Fediverse client

Relatica is a new, refreshing, and promising cross platform #Friendica client in beta now.

#Relatica runs on #Android, #Linux, #Mac, and #Windows. It also has some welcome and ambitious goals on the roadmap:

Testers, packagers, and early adopters are wanted for the official beta program.

Relatica's developer is friendly, accessible, and responsive. The project enjoys an aggressive development cycle and has its own dedicated #Matrix support channel.

It's good to see a novel and dedicated effort to deliver a capable #desktop and mobile client that allows for #social engagement without a browser:

https://gitlab.com/mysocialportal/relatica/-/blob/main/README.md

For those here that aren't aware already, Friendica is one of the earliest and yet most modern and feature rich #Fediverse platforms, #internetworking with other protocols that enables you to do things like directly interface with #Diaspora and even the deprecated legacy silo networks too.

#Friendica has a pluggable addon system and provides direct support for multiple text formats and even direct linking of images in posts.

There's really just too much to list. If you're wanting a feature complete platform for #publishing, #microblogging, #news, #RSS, social engagement and more then Relatica is definitely worth trying out!

If you're interested in trying out Relatica's ease of use and features then you'll need to have a user account on a Friendica server.

You can self-host or get yourself a free Friendica account here:

https://Friendi.ca

I hope that helps!

I can be reached on Matrix at:

@tallship:matrix.org

via XMPP at:

tallship@jabber.org

and in the Fediverse at: @tallship@public.mitra.social

#tallship #FOSS #Relatica #ActivityPub You can haz #Cheezburgerz! 🍔

⛵

.

hmtl/ or public_html/, DNS, what is IP or name based virtual hosting, and what's this SNI stuff? Why does it say, “It Works!”?

Self-hosting was always easy. You simply harness the awesome power of a UNIX machine with BIND and an Apache server, and dump all those AngelFire files into the default directory. Then you register a domain name from Internic for $35/yr and give them the names and IP addresses for the glue records to point at your AUTH nameservers.

Easy Peasy!

And then you realize that for all the work you just did, you could be hosting a couple of hundred websites. After all, you've got an AMD K6-2/350 with a whopping 16MBytes of RAM and that /24 they handed you gratis a few years back!

Most websites just sit there, waiting very quickly to have their files served, and the money just keeps rolling in at $15/mo for each website, but you're beginning to run out of IP addresses to alias and bind to your 3Com 3c905 NICs.

But with HTTP 1.1 there's a new potential, it might be a little tricky at first though...

Yes, back when SNI first enabled us to move away from IP based VirtualHost containers in Apache to the Name Based VirtualHost where many websites shared a single IP address, there were some interesting issues, such as the default VirtualHost container being served if you didn't also specify non RFC compliant hostnames as aliases.

For example, there was a trend at the time to ignore proper usage of hostnames, with “www” generally being used as the traditional defacto, default hostname for a host delivering HTTP. i.e.,(http://www.SLD.TLD).

Similarly, you would usually name your first FTP server “ftp”, and the protocol was specified as “ftp”, yielding ftp://ftp.SLD.TLD, and gopher would be gopher://hostname.SLD.TLD in the address bar of your browser. Other protocols followed that same “protocol://hostname.4LD.3LD.SLD.TLD format, these child zones being a very common practice in universities in the .EDU and .MIL TLDs, as well as the .UK, .FR, .AU, .US, and some other ccTLD's (Australia has recently dropped that whole requirement for .com.au and .net.au finally lol).

So, although it was merely convention to name your hosts after the services they were delivering, like “www, www2, www3, Etc.”, or ftp, gopher, Etc., Those were only conventions and you could name them whatever you wanted.

But you weren't supposed to use the canonical domain name as the hostname!

Nevertheless, as the “web” became more ubiquitous and average users, oblivious to other protocols, began to ask the question, “why do I need to type in all those extra characters for www.ibm.com (like http://www3.ibm.com) instead of just ibm.com?“, in conjunction with the popular trend of browsers defaulting to “http://” protocol (unless you manually specified another protocol), many providers started to accommodate those hosting customers by breaking with the RFCs and pointing DNS A RRs to “@” or “SLD.TLD” – the canonical domain name, akong with another A record for “hostname.SLD.TLD” (usually still using www for the first website).

Now, when you query a DNS server for a hostname, it returns an IP address, no problem so far. And with IP based hosting it really doesn't matter what you call your website in your Apache server's VirtualHost container – it's just going to return a web page for the server at that IP address, coz that's all it's being asked: “Do you have HTML to send me for the IP address on this HTTP server?”, And then it sends the page – coz there's only one website per IP address!

But with HTTP 1.1 and SNI it's a compound question:

“Do you have HTML to send me for the IP address with the hostname of 'www.SLD.TLD' on this HTTP server?”

If yes, then serve the page. If not however, it gets a little weird. The default VirtualHost container is usually the first one defined in httpd.conf, so on many web servers that's the page that says – “It Works!” lolz.

So, in DNS you had to have two A Resource Records (RRs) one for say, 'www', and one for '@', or you could use a CNAME RR if you're one of those lame-o boneheads (bad form – don't use CNAME's!), AND... You also either need to specify two <Named VirtualHost> containers pointing to the same directory, or just one with an Alias directive.

NOTE: you 'could' point to two different directories, but in 99% of all cases, why the heck would you do that?

I dunno why, but maybe coz many hosting providers didn't understand how to write a DNS zonefile in BIND or maybe coz they didn't grasp that the browser was actually now asking for an actual hostname with it's request to the IP address that httpd was listening on, but this resulted in a lot of “no joy” when people neglected to type in the “www”, resulting in delivery of either someone else's website or the comical “It Works!” page (ROFLMAOPMP).

Adding insult to injury, the opposite could be the case when leaving out the hostname and just typing in the domain into the address bar, depending on how httpd.conf was configured – many knowledgeable sysadmins resisted this the because it wasn't RFC compliant, but eventually (the customer's money is always right), most default websites today just serve the canonical domain name as the main (or maybe even the only) hostname in a VirtualHost container in Apache with an alias to the 'www' hostname (or server block on Nginx.

As a little epilog, that came back to bite hosting providers, and moreso, their customers, in the last decade or so when the evil Cloudflare and ever popular WordPress came into prominence – To enforce their predatory vendor lock-in practices, Cloudflare offered free CDN services to people with websites... But only for one hostname per domain, AND, that hostname HAD TO BE “www”, lolz...

Well, after a couple of decades of dumbing down the user and people setting the main name of their WordPress sites to, “SLD.TLD”, this would cause, in the best scenario, to have their websites served to most people without the (so-called) benefit of Cloudflare's CDN... Unless you could retrain every user on the entire planet to type in the actual hostname (www), OR... pay Cloudflare lolz.... 🤘🤡🤘

Well my friends, That's all I've got right now, I hope you found that a bit amusing in a sort of nostalgic kinda way.

I can be reached on Matrix at:

@tallship:matrix.org

via XMPP at:

tallship@jabber.org

and in the Fediverse at: @tallship@social.sdf.org

#tallship #ramblings #lamentations #humor #geek_pr0n #BOFH #comedy

⛵

.

takahē – A new Fediverse paradigm

Fresh out of the oven is #Takahē, introducing a very interesting basic functional motive for development and delivering a beautiful #UX. It also derives inspiration in the form of its #mascott from a species once thought extinct for about a century.

That is, until a single man obsessed with the saga of this large, flightness bird since his early childhood, endlessly sought out and eventually rediscovered it was actually extant 75 years ago through his tireless efforts.

In recent years, and not without some particularly problematic attempts in the management of this #endangered_species, the population of these magnificent birds has more or less stabilized at around 100 members living in the wild, thanks to the committed efforts of a government sponsored #refoliation, hatching, and rearing program; in c