antipaucity

A lot of talk has been made in the past couple years (and even currently by one of the fellas running for the 2020 Democratic Party nomination to be their candidate for President) of governments (which really means taxpayers) funding a universal basic income.

Alaska’s been doing something like this for close to 40 years.

So have several other places – including Finland.

In the vein of Scott Adams (sidebar – if you’re not listening to his podcast (or watching it on YouTube (or participating in the Periscopes)), you should), here’s an idea.

At birth, every citizen born in the United States will be granted $100,000 in a safe financial vehicle (T-Bills? Savings bonds? CDs redeemable at a Federal Reserve Bank?) – as a prorated benefit over 18 years (if, God forbid, they die before adulthood – accumulated funds will be designated to their parents or legal guardians in the event they pass before reaching their 18th birthday.).

That’s an accumulating ~$5555 per year for 18 years.

There are about 4 million babies born in the US every year.

Additional cost to taxpayers (ie the Federal budget)? About $22.2 billion per year² (for ~20-25 years, then it would be flat (at ~$550B/year), presuming no major increase in birth rate).

But when you turn 18, BAM!

$100,000 to do with whatsoever your heart desires.

Down payment on a house? Check.

New car? Check.

Tuition to college or trade school? Check.

Invest in stocks, bonds, starting a business? Check.

Roll-over into an IRA? Check.

It’s yours.

Tax-free.

To keep.

To do with whatever and however you like.

What would you do with it?

I want you to watch these 6 movies (in this order):

• The Wizard of Oz
• Ferris Bueller’s Day Off
• Night of the Living Dead (1968 edition)
• The Godfather
• Pi
• Inception

Watch them with a notebook and pen or pencil handy (yes: use physical writing and recording tools; don’t use your laptop, tablet, or phone).

Write things you see that jump out at you about the story – how it is told, what is explicitly stated, what is implicitly hinted-at, what is alluded-to, etc.

Start with the very first thing you see after the title credits finish.

I’ll give you a hint, and highlight a small handful of items from the first ~15 minutes of The Wizard of Oz:

1. Everything is gray (well, sepia)
2. Dorothy is whiny
3. Dorothy is obsessed with her dog
   1. Why is Toto going anywhere with Dorothy off the farm grounds?
   2. Especially, why is Dorothy taking Toto near Ms Gulch’s cats?
4. Dorothy is an orphan
   1. Auntie Em & and Uncle Henry are on the farm, but
   2. no parents anywhere in sight
5. When Dorothy wakes up in Oz, everything is in eye-popping, brilliant Technicolor

Tell me what you find – I’m intensely intrigued to see how your lists compare to mine.

As a society, we have forgotten how to forget. We are addicted to storing everything forever. Why?

New Atlas had an article recently on the demise of skyscrapers in favor of new ones which starts off,

The Great Pyramid of Giza has stood at a height of around 460 feet for 4,500 years, but these days we are ripping down tall structures without even batting an eyelid. A new study looking at the average lifespan of demolished skyscrapers illustrates just how quick we are to pull the trigger, raising the question of how we could reimagine tower design so that they last centuries rather than decades.

I ask, first: why should we design things to “last centuries rather than decades”?

Yes, the future impact of decisions made today must be carefully evaluated (“concrete cannot be recycled, and most of the tallest buildings in the world use concrete for their main structural system”).

But designing for “centuries” is not the answer.

Or, at least, it’s not the answer.

It’s not a panacea – though there may be some occasional use cases for expecting a structure to last generationally.

But since time immemorial, buildings have mostly been built with at least an unconscious knowledge they would not exist “forever”.

Sure, there are interesting historical sites (such as these now-destroyed Mayan ruins) that we might have liked to keep. But reuse of old materials is part and parcel of civilizational progress.

In a recent episode of Paul’s Security Weekly, an off-hand comment was made about documentation: you shouldn’t merely document what to do, nor even why, but also what you tried that didn’t work (ie, augment the status quo).

The upshot being, to save whomever comes to this note next (especially if it turns out to be yourself) effort you spent that was in vain.

This is similar to a famous quote attributed to Edison,

I have not failed. I’ve just found 10,000 ways that won’t work.

In light of my recommended, preferred practice and policy of “terse verbosity“, I would strongly suggest not placing the “doesn’t work” in-line, typically. Instead, put footnotes, an appendix, etc. But always

explain everything you did, but use bullet points if possible, rather than prose form

Loads of other goodies in that episode, too – but this one jumped-out as applicable to everyone.

Schneier has a recent article on security concerns for IoT (internet of things) devices – IoT Cybersecurity: What’s Plan B?

We can try to shop our ideals and demand more security, but companies don’t compete on IoT safety — and we security experts aren’t a large enough market force to make a difference.

We need a Plan B, although I’m not sure what that is. Comment if you have any ideas.

There are loads of great comments on the post.

Here’s the start of some of my thoughts:

There are a host of avenues which need to be gone down and addressed regarding device security in general, and IoT security in particular.

Any certification program could be good .. right up until the vendor goes out of business. Or ends the product line. Or ends formal support. Unless we go to a lease model for everything, you’re going to have unsupported/unsupportable devices out there.

We can’t have patches ad infinitum because it’s not practical: every vendor EOLs products (from OSes to firearms to DB servers to cars, etc).

A few things which would be good:

• safe/secure by default from the vendor – you have to manually de-safe it to use it (like a rifle which only becomes usable/dangerous/operable when you load a cartridge and put the safety off)
• well-known, highly-publicized support lifecycles (caveating the vendor going out of business)
• related to the above, notifications from the device as it nears end of support
• notifications from the device as well as the vendor that updates/patches are available
• liability regulations – and an associated insurance structure – affecting businesses which choose to offer IoT devices across a few levels:
  1. here it is :: you deal with it || no support, no insurance, whatever risk is there is your problem
  2. patches / updates for 1 year || basic insurance / guarantee of operation through supported period, as long as you’re patched up to date
  3. patches / updates for 3 years ||
  4. patches / updates for 5 years || first-level business offering || insurance against hacks / flaws that have been disclosed for more than 90 days so long as you have patched
  5. patches / updates for 10 years || enterprise / long-term support || “big” insurance coverage (up to a year, so long as you’re yp-to-date) || proactive notifications from the vendor to customers regarding flaws, patches, etc

There are probably other things which need to be considered.

But there’s my start.

Just what is journalism going to look like in the future?

It’s a question that’s been bouncing around my head for a while, and articulated in various pieces by Ben Thompson (in a nichification process), my friend Eric Hydrick, and others.

Eric brought up the idea of supporting “special” journalism through services like Patreon.

I think that’s a start … but still limits – as do paywalls, subscriptions, etc – informing the populace to those who care enough to pay intentionally and specifically for that publication / journalist / etc.

I think an improvement upon that is a bucket approach. I outlined one such possible technique in my recent critique of Pi-hole:

Maybe there needs to be a per-hour, per-article, per-something option – a penny for an hour, for example (which, ftr, comes out to a monthly fee of about $7)- so that viewers can toss some scrilla towards the creators, but aren’t permanently encumbered by subscriptions they’ll soon forget about

I’ll go out on a limb and predict “journalism”, as we have known it for hundreds of years, is going to completely disappear in the next 10 years. Now, that doesn’t mean it’s completely going away (though, with the general willful ignorance of people…maybe it will). It does mean, though, that it’s going to be radically different in form.

With the rise of decentralized (and, now, recentralized) publishing with widespread adoption of the world wide web, everyone can (and, maybe, should) be a publisher.

The overwhelming majority of publishers are not receiving anything from their writing – except personal satisfaction (that includes myself .. in 20+ years of having websites, blogs, etc, I’ve made about $35 online). And publishing for “free” (ie, self-funded) should always be an option: as a content creator, it should always be up to you as to whether you wish to charge for what you’ve made.

But if you want the possibility of getting paid for your work, that should be an option, too: and while you might be “worth” subscribing to, the odds are very good you are not. And that leaves a quandary: how can you get paid for your work (if you want), without encumbering your audience into either leaving instantly, or succumbing to pressure to subscribe.

Which is why I think a bucket approach could work well – you’d know how much you had available in your balance, recharging would be simple (could even be automated – hit a threshold, recharge to some preset amount), and you’d know exactly who was getting your money, and, more importanly, for what – it’s not some ambiguous “subscription” to a “site”, but paying for precisely the content you see (or want to see).

In many ways, it’s extending the Patreon idea, which is really just a modern reimagining of patronage, from mere individual shows, sites, etc, down to a granularity of specific pages, articles, images, etc.

And let’s not even talk about the analytics that could be performed on payments and page views under such a model: identifying regions that are interested in certain content, audiences that like certain things, what are immediate turn-offs, etc. Incorporate some form of solid feedback/interaction mechanism, and you could possibly develop healthy gamification of your site: maybe even waiving monetary contribution if you hit certain levels of interaction on the site.

Active community building via people who actually care (and that just happens to fund the service).

Now that would be something.

Back in November, I was really up on Pi-hole.

But after several more months of running it … I am far less psyched than I had been. I’m sure part of that is having gotten better internet services at my house – so the impact of ads is less noticeable.

But a major part of it is that Pi-hole is just too aggressive. Far far too aggressive. Aggressive to the point that my whitelist was growing sometimes minute-by-minute just to get some websites to work.

Is that a problem with the site? No doubt somewhat. But it’s also a problem of blacklists. When domains and IPs are just blanket refused (and not in a helpful way), you get broken experience.

Pi-hole has also gone to a quasi-hijack approach: when a domain has been blocked, instead of it just silently not working, it now returns a message to contact your Pi-hole admin to update the block lists.

I hate intrusive ads as much as the next person .. but that shouldn’t mean that all ads are blocked. I have unobtrusive ads on a couple of my domains (this one included).

But even with Pi-hole, not all ads are blocked.

Part of that is due to the ever-changing landscape of ad servers. Part of it is due to the inherent problems with the blacklist/whitelist approach.

Content creators should be entitled to compensation for the efforts (even if they voluntarily choose to give that content away). Bombarding visitors with metric buttloads of advertising, however, makes you look either desperate, uncaring, or greedy.

The current flipside to that, though, is the pay-wall / subscription approach. Surely subscriptions are appropriate for some things – but I’m not going to pay $1/mo (or more) to every site that wants me to sign-up to see one thing: just today, that would’ve encumbered me with over $100/mo in new recurring bills.

Maybe there needs to be a per-hour, per-article, per-something option – a penny for an hour, for example (which, ftr, comes out to a monthly fee of about $7)- so that viewers can toss some scrilla towards the creators, but aren’t permanently encumbered by subscriptions they’ll soon forget about (though, of course, that recurring subscription revenue would surely look enticing to publishers).

As with the per-song/episode purchase model that iTunes first made big about 15 years ago, you could quickly find out what viewers were most interested in, and focus your efforts there. (Or, continue focusing your efforts elsewhere, understanding that less-popular content will not garner as much revenue as popular content will).

Imagine, using my example of $0.01/hr, how much more engagement you could end up garnering while visitors are actively on your site! A penny is “nothing” to most people – and probably just about all who’re online. Maybe you’ll have a handful of people “abusing” the system by opening a thousand pages in new tabs in their hour … but most folks’ll drop the virtual coin in the nickelodeon, watch the video / read the page / whathaveyounot, and move on about their day.

And not everyone will opt for the charge model. Sites that do utilize it can have some things marked “free” or “free for the next 24 hours” or “free in 7 days” or whatever.

Ad companies like Google could still work as the middleman on handling transactions, too – any time you visit per-X content, there could be a small pop-up that indicated you’d be withdrawing Y amount from your balance to view the site (I’m sure there’ll be competition in the space, so PayPal, Facebook, Stripe, Square, etc etc can get in on the “balance management” piece). And at the end of whatever period (day, week, month), Google can do a mass-settle of all the micropayments collected for each site from each visitor (with some percentage off the top, of course).

No ads. You’d actually Get What Your Pay For™, and issues like the recent Admiral thing would go in a corner and die.