To navigate the web is to beat a path through a labyrinth of links left by others, and to thereby create associative links yourself, unspooling them like a guiding thread onto a floor already carpeted with such connections. Each thread of connection is unique, individualized: everyone draws their own map of the network as they navigate it.
Austin Kleon expands on Brian Eno’s neologism “scenius”:
Genius is an egosystem, scenius is an ecosystem.
There are some great hands-on accessibility patterns in this talk transcript from Scott.
I think this might be the first large-scale practical demonstration of the InterPlanetary File System: routing around the damage of Turkey’s censorship of Wikipedia.
Photos of analogue interfaces: switches, knobs, levers, dials, buttons, so many buttons.
The Long Now Foundation has been posting some great stuff on their blog lately. The latest is a look at orreries, clocks, and computers throughout history …and into the future.
Is the emergence of a technologically advanced civilisation necessarily contingent on the easy availability of ancient energy? Is it possible to build an industrialised civilisation without fossil fuels?
This thought experiment leads to some fascinating conclusions.
So, would a society starting over on a planet stripped of its fossil fuel deposits have the chance to progress through its own Industrial Revolution? Or to phrase it another way, what might have happened if, for whatever reason, the Earth had never acquired its extensive underground deposits of coal and oil in the first place? Would our progress necessarily have halted in the 18th century, in a pre-industrial state?
A step-by-step guide to building progressive web apps. It covers promises, service workers, fetch, and cache, but seeing as it’s from Google, it also pushes the app-shell model.
This is a handy resource but I strongly disagree with some of the advice in the section on architectures (the same bit that gets all swoonsome for app shells):
Start by forgetting everything you know about conventional web design, and instead imagine designing a native app.
Avoid overly “web-like” design.
What a horribly limiting vision for the web! After all that talk about being progressive and responsive, we’re told to pretend we’re imitating native apps on one device type.
What’s really disgusting is the way that the Chrome team are withholding the “add to home screen” prompt from anyone who dares to make progressive web apps that are actually, y’know …webby.
This wide-ranging essay by Nick Nielsen on Centauri Dreams has a proposition that resonates with my current talk about evaluating technology:
Science produces knowledge, but technology only selects that knowledge from the scientific enterprise that can be developed for practical uses.
Then there’s this:
The most remarkable feature of how we got from the origins of our species to the complex and sophisticated civilization we have today is that, with few exceptions, none of it was planned. Technology was not planned; civilization was not planned; industrialization was not planned; the internet was not planned.
Comparing different ways to hide content accessibly:
There are three reasons behind hiding content in an interface, and it’s important to identify what those reasons are, as they will correlate with the appropriate technique needed to hide such content.
- Temporarily Hidden Content
- Purposefully Visually Hidden Content
- Purposefully Visual-Only Content
There’s a lot of great knowledge in here that can be applied to plenty of other interface elements too.
A small black mirror.
An even thornier problem than the Clock of the Long Now.
Time-shifted reports from the Russian revolution, 100 years on.
All the texts used are taken from genuine documents written by historical figures: letters, memoirs, diaries and other documents of the period.
Every day, when you go onto the site, you will find out what happened exactly one hundred years ago: what various people were thinking about and what happened to each of them in this eventful year. You may not fast-forward into the future, but must follow events as they happen in real time.
Hope is a belief that what we do might matter, an understanding that the future is not yet written.
Rebecca Solnit’s piece reminded me of something I mentioned a couple of year’s back when I referred to Margaret Atwood’s phrase “judicious hope”:
Hope sounds like such a wishy-washy word, like “faith” or “belief”, but it carries with it a seed of resistance. Hope, faith, and belief all carry connotations of optimism, but where faith and belief sound passive, even downright complacent, hope carries the promise of action.
A website dedicated to one of the most, um, interesting solutions to the Yucca Mountain nuclear waste storage problem:
- Engineer cats that change colour in response to radiation.
- Create the culture/legend/history that if your cat changes colour, you should move some place else.
There are T-shirts!
An online training course that will banish all fear of the command line, expertly delivered by the one and only Remy Sharp.
For designers, new developers, UX, UI, product owners and anyone who’s been asked to “just open the terminal”.
Take advantage of the special launch price—there are some serious price reductions there.
This is a nice understandable explanation of the basics of React.
There’s a real skill in explaining something so clearly that even n00bs like me can understand it.
Following on from Ire’s post about linting HTML with CSS, here’s an older post from Ebay about how being specific with your CSS selectors can help avoid inaccessible markup getting into production.