Dan Dean

What should this thing be?

Aug 31, 2013

What‘s the point of this website? Why do I bother keeping and nominally maintaining it?

There are a few reason, all of which range from completely unrealistic to somewhat reasonable. The first and possibly most unreasonable is that I dislike the idea of my content – the web-facing record of my daily thoughts and life – existing soley within an array of proprietary walled gardens:

I genuinely enjoy what these services do, and how they allow me to interact with my friends, family and acquaintances without much effort. The chances that these same people are going to come find “my content” here on my website is so close to zero that I might as well not even consider it an option.

But STILL, jesus fucking christ, I hate that these services essentially own my content, and have it within their means to control who gets to see it, and if it continues to exist into the future. The only reason they choose to maintain a record of my life on their servers is to figure out a way to squeeze a few pennies out of it. Sigh…

So, keeping this in mind – that very few will ever see content posted here, but that it is at least within my full control – what exactly can I do with this space? The ideal format for what is posted here should be in the format of a tumblog:

Is low-friction convesion and publishing possible?

How to update and post to this without while creating as few barriers as possible? I should be able to, for the most part, post to the other services I use and have them automatically get cross-posted to this website. How could that work? Probably the easiest way would be to mark posts on other services in a way that could tell an automated script to pull them down and generate the files necessary to push here.

Content from specific services could be targeted, converted and posted:

If any post contains geodata, a map should be embedded on the page.

The automatic posting processs

Building it

This is the shitty (but really FUN) part. It takes time to build these things. The most realistic thing to do would be to implement one service at a time, starting with the most used. The endpoints themselves could exist as a single application on my own server, or live on a single and tiny application on a cloud provider like EC2 or Nodejitsu.

Separate projects:

Now, we get to see if I actually do this.

blog comments powered by Disqus