julien

14 ms·

121.
by julien 13y ago
Deck.js
122.
by julien 13y ago
Landslide
123.
by julien 13y ago
Reveal.js
124.
by julien 13y ago
Shower
125.
by julien 13y ago
This is an amazing decision!
126.
Who saved The Old Reader?(scripting.com)
3 points by julien 13y ago|1 comments
127.
by julien 13y ago
Same as hunting for/picking your own food or sending snail mail to tell things to people. It works, but is not very efficient! Efficiency opens the door for innovation and new behaviors.
128.
by julien 13y ago
Show me a service that has static files as RSS :) no matter what a stat() is still more expensive than nothing
129.
by julien 13y ago
Good luck with getting anyone who isn't a nerd to do it!
130.
by julien 13y ago
I don' see how using header will remove the need to fetch the resources, parse them and diff them. Maybe you'll do that less often, but you'll still do it a lot...
131.
by julien 13y ago
Agreed, and we (superfeedr) have been strong advocates of XML for some problems. We are also tired of hearing: give us JSON or we won't care about RSS.
132.
by julien 13y ago
Do you really think people who don't know what their browser is will install an extension or a bookmarklet?... Again, compare that experience to a click on "follow me on twitter" button.
133.
by julien 13y ago
Yes, feedly is a browser extension, that you knew how to install Most people don't and most readers are not browser extensions...
134.
by julien 13y ago
Many people have argued that RSS is too complex compared to JSON... and to be fair it's clear now that every new API from every service is JSON based. At this point, XML is clearly on the way out for web people!
135.
by julien 13y ago
Weird. Any JS error?
136.
by julien 13y ago
HEAD is still a waste of resources. the http body in the context of feeds is usually pretty small and does not consume a lot of resources compared to actually initiating (or even keeping) the TCP connection. HEAD also means the server as to
137.
RSS mistakes: let's not make them again(blog.superfeedr.com)
68 points by julien 13y ago|61 comments
138.
State of PubSubHubbub (subscriber's edition)(blog.superfeedr.com)
4 points by julien 13y ago|1 comments
139.
by julien 13y ago
I'd be interested in knowing about people doing that too :) I am bit tired of Google these days...
140.
Independence Day on the web too(blog.superfeedr.com)
2 points by julien 13y ago|0 comments
141.
SubToMe is now an AngularJS app and localized(blog.superfeedr.com)
2 points by julien 13y ago|0 comments
142.
by julien 13y ago
The second part will stay, while we hope to change the 1st part (pricing per item) really soon into another scheme!
143.
by julien 13y ago
Locking is a no go has we get 2 things: high frequency updates feeds (up to a couple dozen entries per second), which we need to constantly update. Locking them for even a fraction of time could turn into a nightmare and a huge backlog if f
144.
XMPP For the Web with JSON(blog.superfeedr.com)
44 points by julien 13y ago|28 comments
145.
XMPP for the web(xmpp-ftw.jit.su)
1 points by julien 13y ago|0 comments
146.
Digg Reader: We’re Still Learning(blog.digg.com)
3 points by julien 13y ago|0 comments
147.
SubToMe Store: subscribe with your favorite RSS reader(blog.superfeedr.com)
1 points by julien 13y ago|0 comments
148.
How Large Will the Paid Feed Reader Market Be?(rumproarious.com)
37 points by julien 14y ago|22 comments
149.
Introducing Fargo(3xa.r2.ly)
2 points by julien 14y ago|0 comments
150.
Why SubToMe is better(blog.superfeedr.com)
5 points by julien 14y ago|0 comments

More ›