Skip to main content

Forums, Feeds, and Foundations for Answers

The web forum. Mailing lists. Newsgroups. They all boil down to the same thing: digital forums of discussion. We have relied on these mediums to carry the Internet from prototype to fad to craze to necessary base of our culture. The discussions we enable through the web (and its friends) drive everything we do in the digital world. How can we pay tribute to this with an upgrade?

We have migrated from discussing to just broadcasting our opinions. Maybe we'll tune in to some other opinions on similar topics. Maybe some of them will have read ours, who knows. We are deviating from the formula that has driven us to everything we think models the technology we desire. We need to move back to real discussions, bringing what we've learned from feeds, blogging, and content subscriptions.

Forums, beloved as they are, have lost their way. Unfortunately the number of Internet users has risen so high that no forum can carry nearly the percentage of knowledgeable users they once could. This leaves all forums at a loss for intelligent information and leads to a loss for anyone using them. Either we must spend eternity locating the perfect forum for each exact question, or we cross post dozens of forums and monitor them all for updates. This simply does not cut it.

Everyone has at least one feed these days, and what we feed the world with is still pretty limited. We write little posts, usually barely enough to call an article. We can post anything. We can feed the Internet our pictures, voices, or our minds. We can send out our questions, formatted for consumption, and allow everyone subscribing to our feed or receiving the questions through aggregation and search engines to get a full range of questions from the curious and in need. Instead of browsing to a forum page, we can find those in need through the same feed readers we already enjoy.

For the responses to the questions, the same feeds can be used to broadcast responses with meta-data attaching them to the right questions from the current feeds. The questions can even be posed with information on HTTP requests the responder can make to inform the original poster of a feed with a response.

No, this isn't even a draft of any idea for a technical spec. It is just a few ideas, and maybe even just enough for a micro-format. It would not be a lot to put together, would be less to pose the questions like this, and most of the work would be in informing those asking of the answers, but not much work.

Comments

Popular posts from this blog

On Pruning Your Passions [MOVED]

We live in a hobby-rich world. There is no shortage of pastimes to grow a passion for. There is a shortage of one thing: time to indulge those passions. If you're someone who pours your heart into that one thing that makes your life worthwhile, that's a great deal. But, what if you've got no shortage of interests that draw your attention and you realize you will never have the time for all of them?

If I look at all the things I'd love to do with my life as a rose bush I'm tending, I realize that careful pruning is essential for the best outcome. This is a hard lesson to learn, because it can mean cutting beautiful flowers and watching the petals fall to the ground to wither. It has to be done.

I have a full time job that takes a lot of my mental energy. I have a wife and a son and family time is very important in my house. I try to read more, and I want to keep up with new developments in my career, and I'm trying to make time for simple, intentional relaxing t…

The Insidiousness of The Slow Solution

In software development, slow solutions can be worse than no progress at all. I'll even say its usually worse and if you find yourself making slow progress on a problem, consider stopping while you're a head.

Its easy to see why fast progress is better: either you solve the problem or you prove a proposed solution wrong and find a better one. Even a total standstill in pushing forward on a task or a bug or a request can force you to seek out new information or a second opinion.

Slow solutions, on the other hand, is kind of sneaky. Its insidious. Slow solution is related the Sunk Cost Fallacy, but maybe worse. Slow solutions have you constantly dripping more of your time, energy, and hope into a path that's still unproven, constantly digging a hole. Slow solutions are deceptive, because they still do offer real progress. It is hard to justify abandoning it or trying another route, because it is "working", technically.

We tend to romanticize the late night hacking…

Finding "One Game A Month"

I was really excited about the One Game A Month challenge as soon as I heard about it.
For about two years I've struggled in fits and starts to make my way into game development. This hasn't been productive in any of the ways I hoped when I started. Its really difficult to be fairly experienced as a developer, which I believe I am in my day job as a web developer, while struggling really hard at an area in which your experience just doesn't exist.
Its like being a pilot who doesn't know how to drive.

But this challenge provided a new breath to this little hobby of mine. It gave me a scaffolding to experiment, to learn, to reflect on finished projects. I had spent far too much time on game projects that stretched on far past their exciting phases, bogged down by bad decisions and regret.
And it has worked.
I have a lot to learn. I have a lot of experience to gain through trial and error and mistake and discovery. I have a lot of fun to be had making more small games t…