Flutterby™! : External costs of crypto

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

External costs of crypto

2024-07-17 18:43:57.008157+02 by Dan Lyke 0 comments

I've been thinking a lot about the external costs of things. Automobiles are easy, except that even now, in twenty freakin' twenty four, we're still finding direct ways (tire dust) that cars have huge external costs, let alone all of the far down the list effects like increased personal mobility allowing decreased density which means ideas propagate more slowly leading to less innovation.

Advertising is a cost. I remember writing a very angry screed to a science fiction author who spammed a bunch of us who'd signed on to an ITAR export violation (eg: potential felony) with a "you like freedom, maybe you'd like my book!" ad. Spoiler: Dude had not signed on to the same list. But while that, and, of course, the original Canter & Siegel thing, was something worthy of outrage. Today we've accepted the destruction of all of those amazing email lists, indeed, of email itself, as we buckle under the weight of all of the crap.

Looking back at the early electronic currencies of the '90s, or Bitcoin starting in 2008, I'd like to see who predicted this incredible load on our critical infrastructure that it enabled: Ransomware continues to pile on costs for critical infrastructure victims. and as we hear that AT&T reportedly paid $370k for a video of someone allegedly deleting their stolen call records the external costs of cryptocurrencies that are imposed on all of us are only gonna get worse.

[ related topics: Books Privacy Writing Consumerism and advertising Civil Liberties Automobiles Video Government ]

comments in ascending chronological order (reverse):

Add your own comment:

(If anyone ever actually uses Webmention/indie-action to post here, please email me)




Format with:

(You should probably use "Text" mode: URLs will be mostly recognized and linked, _underscore quoted_ text is looked up in a glossary, _underscore quoted_ (http://xyz.pdq) becomes a link, without the link in the parenthesis it becomes a <cite> tag. All <cite>ed text will point to the Flutterby knowledge base. Two enters (ie: a blank line) gets you a new paragraph, special treatment for paragraphs that are manually indented or start with "#" (as in "#include" or "#!/usr/bin/perl"), "/* " or ">" (as in a quoted message) or look like lists, or within a paragraph you can use a number of HTML tags:

p, img, br, hr, a, sub, sup, tt, i, b, h1, h2, h3, h4, h5, h6, cite, em, strong, code, samp, kbd, pre, blockquote, address, ol, dl, ul, dt, dd, li, dir, menu, table, tr, td, th

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.


Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.