What, you didn’t see this coming?
That is all. I’ve got writing to do that largely doesn’t involve English.
What, you didn’t see this coming?
That is all. I’ve got writing to do that largely doesn’t involve English.
Feels great to not have anything to write about.
In reality, they always keep popping up in my mind. But at least, on paper, my mind is free to do what I deem is awesome.
And that’s that. I thought I was going to make this blog into something more than just a personal reflection, but the time is not now.
So we’re reverting back to my personal thoughts and shenanigans, rather than trying to become a tech blogger by any means.
I’ll share links as I find them, and maybe comment on them, but that’s pretty much it.
I’m going to probably use this podium, more so as a chronicling of how I’m going to fail at building a feed reader, but we’ll see where this one leads. I’ve still got time, and fingers to type code with. Money’s running low, but I can’t focus on that just yet.
I’m ready to give it my all, another push.
It’s been tough, and there’s only two and a half weeks left until a private beta.
Go big, or go home. Fake it ’till you make it. Shut up and ship it.
One of the few key features I’d like to implement on FeedSt is real-time updating feeds. Or as real-time as I can get them.
Thanks to PubSubHubbub (PSHB), this is actually going to be possible. I’ve been working with Superfeedr to make the backend work. Add Heroku into the mix, and I’m left to wonder, why there aren’t at least 10 companies doing the same thing. (Unless there are, and I just haven’t found them yet.)
What drives me up the wall is when I post something on this blog, and it takes about half a day to a full day before it shows up in my Google Reader.
It’s not Google Reader’s fault, exactly: They’re merely saving their resources for feeds that are more popular or more updated. It’s more of the problem with the requirement of polling of feeds.
Sidenote: And actually, if you were using a desktop feed reader (like NetNewsWire, of which the beta works with Google Reader), this isn’t a problem at all. You can personally set the time interval that the application grabs and parses the feed. Of course, there’s are plenty of Pros and Cons for going online and offline.
In my opinion, the fact that not all feeds are hit with the same time interval breaks the fair access model that the Internet has become widely known for. I will always get a kick out of the fact that you can visit google.com as easily as you can visit joshkim.org.
PSHB is the fix for this. And actually, Anil Dash talks a lot more about the Pushbutton Web, definitely worth the read.
They’re exciting, and they’re new. Now to make something awesome with them.
fav.or.it | fav.or.it is Dead, Long live favorit.
I remember when fav.or.it was just getting started, and thinking about the ways that it would make my life easier. I didn’t hear this until today, but it’s being shut down, and their efforts are going towards TweetMeme.
Particularly interesting are the reasons Nick Halstead (CEO) list for having not succeeded in their endeavor. I love learning from people’s successes and in this case, failures.
1) The commenting market shifted to what I call ’surface comments’ – these are comments that appear inside other networks, i.e. Facebook, Google Connect, Twitter, FriendFeed (to name just a few) and although some of these have open platforms from which to aggregate from, the problems of context and also a rapidly shifting market soon made it extremely difficult for a small team to continue to compete (for which whole companies have dedicated their resources to notably backtype + ubervue).
I’m not all that knowledgeable on the subject of handling comments across multiple platforms, but I do know that Backtype is awesome. I’m using it right now for the blog.
As a sidenote, what I believe to be much more interesting are the comments made privately. Private and exportable comments are what I feel like is missing. I guess you could email or IM or Direct Message a link to someone with some commentary, but it seems like there would be a better way to do it. And if you do share a link that way, a lot of metadata is lost.
And I love me some metadata.
2) RSS is DEAD – back in early 2008 I presented at thenextweb conference in Amsterdam, and said that RSS was dead for the mainstream market. It was clear to me that as a technology it worked, but that adoption was never going to go mainstream. We attempted with fav.or.it to remove the need to know what feeds you needed to read (you created ’slices’ of content), but it became clear this intention was ahead of it’s time but also poorly implemented, and I doff my hat to the people at lazyfeed for getting it right.
Maybe for the mainstream, “RSS” is dead. (And I hope he meant “feeds”, unless he’s saying that Atom is alive and well. Oh dear, I think I just played into the “correcting Internet geek” stereotype. [Cue Conan O'Brien adjusting his fake glasses]) But since I’m mainly focusing on the power feed users who know what’s going on with feeds in general, I think I have a better chance. This is also why I can get away with not caring about IE 6… and maybe even 7 or 8.
I do agree that feeds are dirty. The implementation is a hack. You know what else is a huge hack? The Internet. When did the ARPANET become a tool for commerce and entertainment? Okay, did I just stretch it a bit there? Ahem.
In any case, I personally use feeds nonstop, even in the midst of this world of Twitter/FriendFeed… uh… yeah, in the midst of the world of Twitter. As long as I’m designing an experience for people like me, I’m sure I’ll be okay.
3) The site has also not been without controversy for re-use of content (through public RSS feeds), and although we put massive effort into support of licensing models (such as auto-detection of creative commons) our approach to aggregation of content for which we could not detect a license, and that required the publisher to opt-out (rather than opt-in) was in hindsight misguided.
Was it for the money? I don’t know… but it’s a bit shady, in any case.I stopped tinkering with fav.or.it when the site became more of a public aggregator, which is why the news of their closing got to me a couple days after the fact. How could I become a supporter of your dream if you take some very interesting routes to becoming awesome?
It’s hard, starting a company. And knowing when to quit is probably harder. Well, easier in my case, because it’ll be when I run out of money and have to find a job.
Oh, to be young and foolish… maybe I’ll eat these words later.
Official Google Reader Blog: A flurry of features for feed readers.
I love this. I can’t win.
It’s like someone’s telling me to give up on FeedSt.
Shift + t to share to Twitter, Facebook, Blogger, and many others.
And look, you can follow actual people’s worth of feeds.
Sigh.
No. But I’m pretty sure I can do something awesome in the world of feeds.
FeedSt, as an idea, has been in the back of my head, ever since I started using feed readers. (I actually need to sit down and piece together some history.) From the get go, I knew the dangers of creating a me-too company, a situation where the basic features of the original company are copied plus some additional feature set.
It’s been many months since I started thinking about FeedSt, but I still feel like there’s enough people out there demanding there is a better experience dealing with feeds. I hope to show these issues through blog posts and code.
Them: A seven person engineering team from Google, with stacks of cash and years of dev time. (I’m assuming that the number of contributors on the Google Reader Blog maps directly to the people who are working on it.) The majority of this team is probably incredibly smart and experienced.
Me: A single dev, with very little runway left and a couple months of time left. Not so experienced, and actually is lacking in a huge chunk of the skillset needed to pull this off.
And it’s not just Google Reader. With the sale of FriendFeed to Facebook, Streamy.com is probably going to become the darling “social feed reader”. And I’m sure those people are extremely smart.
Regardless, yes, the odds are tremendously against me. But it’s never been this clear to me that I should be doing this. Foolish? Probably. But I only live once. I definitely want to make what seems to be my last chance count.
So with this post, I hope to kick off a series of posts pertaining to this project. Hope to keep you updated as stuff gets done.
Four weeks. I can have something awesome in four weeks, right? Most definitely.
I see more and more demand for a better feed reader. I’m not going to lie, this is making me very antsy.
While feeling superior for knowing that there would be an increasing demand for something better, I feel like a lamer for not having actually release a product that is a solution to this problem.
Starting with this week, I’ve increased my efforts in releasing FeedSt. I hope to get it finished in the midst of all the fun things that are happening in the world.
Let’s see this project through. Seriously.