Archive of: world wide web
Last night I attended the always excellent JS Oxford, and as well as having my mind expanded by both Jo and Ruth’s talks (Lemmings make an excellent analogy for multi-threading, who knew!), I gave a brief talk on the Indieweb movement.
If you’ve not heard of Indieweb movement before, it’s a push to encourage people to claim their own bit of the web, for their identity and content, free from corporate platforms. It’s not about abandoning those platforms, but ensuring that you have control of your content if something goes wrong.
From the Indieweb site:
Your content is yours
When you post something on the web, it should belong to you, not a corporation. Too many companies have gone out of business and lost all of their users’ data. By joining the IndieWeb, your content stays yours and in your control.
You are better connected
Your articles and status messages can go to all services, not just one, allowing you to engage with everyone. Even replies and likes on other services can come back to your site so they’re all in one place.
I’ve been interested in the Indieweb for a while, after attending IndieWebCamp Brighton in 2016, and I’ve been slowly implementing Indieweb features on here ever since.
So far I’ve added
rel="me"attributes to allow distributed verification, and to enable Indieauth support,
h-cardto establish identity, and
h-entryfor information discovery. Behind the scenes I’m looking at webmentions (Thanks to Perch’s first class support), and there’s the ever-eternal photo management thing I keep picking up and then running away from.
The great thing about the Indieweb is that you can implement as much or as little as you want, and it always gives you something to work on. It doesn’t matter where you start. The act of getting your own domain is the first step on a longer journey.
The web is like the ship of Theseus—so much of it has been changed and added to over time. That doesn’t mean its initial design was flawed—just the opposite. It means that its initial design wasn’t unnecessarily rigid. The simplicity of the early web wasn’t a bug, it was a feature.
Jeremy Keith on the origins of the web and the false idea that it was designed solely for sharing documents.
We were helping test Ruth’s new site in the Digital Oxford Slack a few days ago, and the topic of easter eggs and silly little things came up. Ruth wanted some quotes from us to scatter in amongst the source of her site, and we helpfully obliged.
It reminded me of a little tribute that I added to the HTTP headers of this site when Terry Pratchet passed, and how your site should be a place to play, and experiment.
So I’ve added something else. You’ll have to go find it though.
I’m going to play more.
8. When a company or industry is facing changes to its business due to technology, it will argue against the need for change based on the moral importance of its work, rather than trying to understand the social underpinnings.
10 Rules of Internet – Anil Dash.
That world formed the web’s foundations — without that world to build on, Google, Facebook, and Twitter couldn’t exist. But they’ve now grown so large that everything from that web-native world is now a threat to them, and they want to shut it down. “Sunset” it. “Clean it up.” “Retire” it. Get it out of the way so they can get even bigger and build even bigger proprietary barriers to anyone trying to claim their territory.
Well, fuck them, and fuck that.
Lockdown – Marco Arment.
[Moore’s Law means] that anything that is dismissed on the grounds of the technology-not-being-good-enough-yet is going to happen.
It’s a fantastic speech on pre and post Cold War generations, networks vs hierarchies, and the failure of governments to come to terms to what is happening in society. Highly recommended.
The mistake my VC friends make is they think it’s either/or. Either you support the open web and are a charity, or you build a silo, monetize it, and get rich. What really happens is that the silos are eventually undermined by the open web.
From Dave Winer. More good stuff in his post on what is actually meant by the “open web”.
I received my invite to the beta of Newspaper Club the other day and ever since have been trying to work out exactly which of the many stupid ideas I’ve had are feasible (not many it seems).
Needless to say, we thought about how memorable it would be if you went to look at a house and the home-owner didn’t give you a simple A4 sheet with an address (yeah, thanks we managed to find the house already, so you giving us the address isn’t much help) instead they gave you a 12 page newspaper about the area. How well the school system is compared to other areas, where is the nearest shop to get some milk on a Sunday morning, a list of restaurants nearby, information about the parking discs and council tax, etc. If a home owner gave me a newspaper about the area and the stats looked good, I’d be sold!
The post is full of inspiring examples of this intersection between The Internet, print on demand and hyperlocal data sources.
Now, if only I could come up with my killer newspaper idea.
To criticise Twitter for its content (or, I should say, your perception of its content) makes as much sense as criticising the content of the telephone networks or the postal service. Like them, Twitter is a means of communicating. The content communicated has no bearing on its value.
And as he rightly recognises, they’re not used to being called on their knowledge and veracity.
It’s now possible for columnists and companies to hear what people are saying about them. That’s unnerving for columnists, not least because their opinions are now frequently challenged by people who know more than they do. Instead of responding like adults – correcting when they’ve made a mistake, engaging when someone raises a sensible point and defending themselves from false accusations – they are whining like children and dismissing technologies that they don’t understand.
(Hat tip: John Naughton)
Leisa Reichelt reflects on what Mark Boulton and herself learnt during the D7UX project this summer, and puts her finger on a big issue facing the Drupal community going forward: who is the target audience?
And so we have this tension. Drupal as a ‘Consumer Product’ and Drupal as a ‘Developer Framework’. Currently, the official direction is that the project is going to attempt to be both. I think this is a serious problem.
The target audiences for each of these objectives are so far removed from each other in terms of their tasks & goals, their capabilities, their vocabulary, their priorities. An attempt to devise an interface to suit both will result in an outcome that I expect we’ll see in the release of Drupal 7 – that is a compromise to both parties.