I'd been writing about what we came to call social media since the early 90s (alt.culture.usenet and alt.folklore.urban ftw), but by the middle of last decade, all anyone wanted to talk to me about was marketing on Facebook, which was the boringest possible topic.
At the same time, my wordpress host had lousy security, and my site was getting frequently disabled because of some malicious javascript uploaded through some hole they hand't patched. I wasn't writing there anymore, so it was pure cost at that point, and cost of my time, not just dollars.
Then I moved to Shanghai for several years, working on other stuff, and fixed the site a couple of times again, and one time, my host was like "We disabled your site!" because of their own security flaws had let it get hacked again, which, the whole thing had entered 'ugh field'territory.
I never decided to let the site lapse, I was just tired of dealing with it, and the political circumstances in both China and the U.S. seemed much more urgent than rescuing some historical essays, so one day at a time of not dealing with it became years.
And here we are, me reading my own eulogy. Which is incredibly flattering and touching, I have to say.
I'm not even sure what of it can be resuscitated -- maybe if I want it back, I'll have to copy it from Wayback (and will say "Thank you Brewster", not for the first time), but if anyone here has advice about competent and secure hosting for an old Wordpress blog, hmu at [email protected], because reading this, it makes me embarassed not to have just fucking fixed this a year or two ago.
And thanks, all, for this thread. -clay
Just want to thank you for your great work.
I used to work on a lot of US Department of Defense projects, mostly stuff I can't talk about. One very notable project I CAN talk about was an initiative (pushed by utterly clueless, insular, and frankly corrupt academics) to spend billions of dollars in 2008-2010 timeframe on implementing Semantic Web technologies in various military business systems across the DoD.
As an actual technologist who knew how to build things, I was perpetually in the awful position of having to explain to leadership that these highly credentialed academics were selling garbage. I had tried to implement systems according to their design. The graph databases they pushed (they hated Neo4J, for reasons of purity because it didn't actually use RDF/OWL in the database...... i get a headache just talking about this...) were slow piles of dogshit that couldn't scale. No amount of reality could dissuade the academics. They had their theories, and any collision with reality was merely an implementation detail that I and my team were simply too incompetent to overcome in their eyes. Almost none of them had actual technical experience. A smattering of Comp Sci folks, and a ton of "Library Science" idiots.
Your essays on why the SemWeb was utter bullshit were a potent weapon I used with the generals the academics were pushing, and I eventually got the generals funding the project to see the light. Got them cancelled, and sent the idiot egg-heads packing. I still see them on LinkedIn to this day. They desperately continue trying to push that rock up the hill, and only recently warmed to more practical graph database solutions.
They HATED YOU. It was hilarious, watching them try to refute your obvious points and clear writing with jargon and hand-waving. Utterly unconvincing to the generals.
Thanks for your essays saving my ass back then!
Most of my writing was about social media, back when the web was young, but "Ontology is Overrated" is actually my favorite thing I ever wrote, and it makes me happy beyond measure to know that it helped someone manage an actual argument over whether to buy into the semantic web!
I have never been talented enough to write production code, but I often thought of myself as trying to provide ammunition to people like you who are, when talking to bosses who didn't understand that the phrase "Now it's just a simple matter of programming!" was a bitter, sardonic joke, not an upbeat assessment of possibility.
Thank you for telling this story! This whole thread has been like hearing my own eulogy, but this in particular is just :chefs_kiss:
The response of the academics to your writings was actually a master class for me in the nature of academic corruption and groupthink. What I learned from that experience was that (contrary to my prior beliefs) high IQ individuals are actually far more susceptible to cognitive dissonance than others are, not less so. They are far more adept at mentally constructing rationalizations and false realities that bolster and protect their existing belief systems from new information than most people are. Add to that the fact that they are extremely economically vulnerable to reputational damage, and you have a really toxic recipe.
You see the same with CompSci/tech people treating data like there's no bias in its collection.
100% concure with this view. The semantic web was one of the biggest wastes if time ever and set back the open web fatally.
You'd have to take all of the text from the Wordpress blog and format it into Markdown but that shouldn't take a huge amount of time unless there is a lot of weird formatting or different media types.
No you wouldn't. Just dump it in as-is.
https://docs.aws.amazon.com/AmazonS3/latest/userguide/Websit...
I'm in favor of static HTML myself where possible, but it's not hard to maintain a secure Wordpress install. Keep automatic updates enabled and don't install any third party plugins.
It's that second part that most people screw themselves with.
When the maintenance is "ensure auto updates are on, and don't do anything that would not get updated automatically" it's not like it requires regular effort.
> Whereas if you just have a collection of articles that you want to keep around as an archive, if you convert them to a static site, you can basically forget about them afterward...
Your web server, your operating system, etc. still require at bare minimum the same level of maintenance.
You can outsource that maintenance to someone else of course, but you can do the same with WP as well.
--
My point is that WP alone doesn't massively increase the maintenance burden, it's what people tend to do with (to?) WP that increases the burden and eventually leads to unmaintained sites.
no dog in the fight here but I felt impelled to point out that ensuring auto updates are on solves almost all security holes except for the security hole it opens up.
In almost any computing context, but especially in the context of a personal blog, the vast majority of exploits are against known security holes for which patches have already been released and those with automatic updates enabled are already safe from.
Yes, hypothetically updates can deliver new flaws of their own and even potentially intentional malicious code, but from a practical sense it's not worth worrying about if you're using mainstream software packages on a major OS.
More effort that you'll be able to exert when you're dead.
Although I highly doubt learning a jekyll config would be harder than managing a PHP daemon, web proxy and mysql database.
Thank you for all of it!
Good luck with restoring your site.
Amusingly, nobody here has stated the obvious: wordpress.com.
Do you remember the title or subject or any key words/phrases?
https://www.wired.com/2006/11/meganiche/
"Now that more than a billion people have access to the Web, there is no longer a trade-off between size and specificity. The basic math is simple: A tiny piece of an immense pie is huge. A decade ago, reaching one-tenth of 1 percent of Web users amounted to 36,000 people, a number that compared favorably with the circulation of, say, the daily newspaper in Bridgewater, New Jersey. Back then, reaching a million users required a decidedly mainstream offering (Amazon.com and MSN come to mind). Now, getting niche can be the path to getting big; one-tenth of 1 percent of today's Web audience is a million people."
Whereas in the past, my store might have 1 or even 0 options on peanut butter, but travel 10/50 miles away and there'd be an entirely different option.
We have a little bit left of this with beer, as most places have a "local" beer available.
And it's the same all over the US. The only variation tends to be that some flavors Flamin' Hot Dill Pickle or Wasabi Ginger, e.g., appear more often in some markets than others.
https://web.archive.org/web/20060210230250/http://www.shirky... "Help, The Price of Information Has Fallen and It Can't Get Up"
http://web.archive.org/web/20140117014453/http://www.shirky....
> People who work on social software are closer in spirit to economists and political scientists than they are to people making compilers. They both look like programming, but when you're dealing with groups of people as one of your run-time phenomena, that is an incredibly different practice. In the political realm, we would call these kinds of crises a constitutional crisis. It's what happens when the tension between the individual and the group, and the rights and responsibilities of individuals and groups, gets so serious that something has to be done.
> And the worst crisis is the first crisis, because it's not just "We need to have some rules." It's also "We need to have some rules for making some rules." And this is what we see over and over again in large and long-lived social software systems. Constitutions are a necessary component of large, long-lived, heterogenous groups.
http://www.shirky.com/
I'm not sure when this happened but I see that Wikipedia has adjusted to this and now links to the archive.org link:
https://en.wikipedia.org/wiki/Clay_Shirky
This is yet another example of the history of the early Web disappearing. Shirky's early essays were fundamental to way we understood the potential of the Web back in 1999-2008.
I actually discovered this while looking for another old Shirky essay which, as far as I can tell, is now entirely gone from the Web.