サクサク読めて、アプリ限定の機能も多数！
トップへ戻る
アメリカ大統領選
blog.superfeedr.com
When Google announced it was shutting down Reader on July 1st, we took a couple days to announce that we will be offering a replacement for its API as well as back up as much of the data that we can. Finding the right tool to store all this data was tricky and as we have finally deployed that backend store we wanted. We have also started backing up significant amounts of data. Requirements We trie
A recent post by Progrium (aka webhook’s biggest evangelist) reminded me that I needed to show how easy it was to plug Superfeedr in a network of webhooks. Here is what you can do, quite quickly! One of the great things with webhooks is that they’re litterally just HTTP urls that can run some arbitrary code. Once you understand that a given hook can also call another hook, it’s obvious to think th
In the last couple weeks, there’s been a lot of hubbub (again!) around Twitter’s latest move with its ecosystem. Twitter is more and more of a media company and less and less of a communication company Generally, on Twitter you’re interracting more and more with twitter itself and less and less with your friends. People claim that this decision is driven by the fact that Twitter’s business model i
You may have heard of WebIntents. At least, here. We’re proud to say that msgboy now supports WebIntents completely: it triggers intents (sharing stories), and handles them (subscribing). Sharing Stories Sharing stories is a key feature of many readers. People just don’t read for themselves only. Up until now, Msgboy offered our users the ability to share stories on Twitter and Facebook. This is g
At Superfeedr, we’ve always been great fans of node.js. We believe the ability to use the same language on both servers and clients will breed a whole new generation of web developers that can do amazing work on both ends. Last year already, we released node.js code a couple hours ahead of NodeKO, and this year, we’re doing it again. A node KO treat In the context of the msgboy (request your invit
One message a month is clearly not as much as we wanted. There is so much going on right now, but we’re also working on an amazing new product that we an’t wait to get our the door. For this new product, we needed to work on a lot of little things and we decided to open-source them all. Last month, we released an ejabberd module to use Websockets instead of Bosh. Today, we release an IndexedDB ada
You know we’re great XMPP fans : it’s by far the greatest protocol to “push” content from a server to client. It comes with stuff like identity, authentication, presence, and many awesome features. Yet, it is not as widespread as HTTP. HTTP’s massive adoption was driven by some great server software : Apache, but also by the ubiquity of web browsers. Unfortunately, XMPP never had clients that coul
Today, GNIP and Twitter announced a deal where GNIP will be able to resell some of the Twitter data. Twitter repeated several times that they didn’t want to use PubSubHubbub and prefered closed and proprietary solutions. I believe that, from the beginning, we were not clear enough that PubSubHubbub was just a technical protocol. It’s a mistake that I’m trying to repair now. If you’re a subscriber,
At Superfeedr, our biggest focus is to make RSS/Atom feeds consumption much easier than what it was, just a year ago. Of course, the “transportation” part of it is a big issue. Polling was the only way up to a few months ago. It’s now less and less the case and pushing the PubSubHubbub protocol for publishers is a way to solve this pain. Another pain is to parse the XML, not only because there are
Superfeedr is growing, and we want to add value for our clients. Our newest feature requires us to store a lot of data, so we went out to look for appropriate solutions in the NoSQL ecosystem. The first decision was Riak, featuring persistent storage on disk and a very tunable clustering layer. The current use-case consists of simply pulling a feed from the database, extend it with the newest entr
A lot of the problems we had to tackle in the last months were directly related to the data stores we used, as well as the schema of the objects we stored. We’ve been using MySQL and Memcached from day one, because it’s always good when you have 50 different problems to tackle to use tools that you know (read this article by @mcuban if you’re about to take the red pill). However, given our growth,
Working with publishers and polling hundreds of thousands of feed has taught us a few lessons and best practices for people who publish RSS or Atom feeds. You might disagree with some of them, so please, let us know in the comments. I want to emphasize that these best practices are technical, not business related. Don’t use RSS and ATOM. There is no good feed parser that doesn’t accept both. Provi
PubSubHubbub is now more or less 6 months old. We have daily talks with people who wonder whether they should implement it in their feeds. Obviously, it matters for publishers to know who will subscribe to their feeds if they use a hub for their feeds. Our monthly list market numbers show a pretty interesting image in terms of how many feeds are PubSubHubub enabled. Here is some more “qualitative”
We weren’t quite sure how to build these analytics. We slowly established a set of requirements and constraints Zero performance impact Fully decoupled from the current infrastructure Results at most hourly Data is more important than graphs Easily-extensible, in case we want to measure more things Collecting There are 2 ways to collect data : on the fly, when things happen, or by just collecting
There is not a day where the real-time web isn’t growing. It’s now time to change how our web services consume information from each other and we’re quite proud to say that Superfeedr is helping services like Tumblr pave the way. Today, we’re announcing a hub for Tumblr, one of your favorite blogging platform is publishing their feeds as PubSubHubbub via Superfeedr. I was very impressed when I met
“Why make things simple when you can make them complex?”. It was probably just too easy to have a common open protocol that everyone would share and use for push notifications of feed changes. At Superfeedr, we chose PubSubHubbub, for obvious reasons, and we’re quite happy with it. Yet, some publishers have made a different choice and since it always eventually comes down to the customer’s experie
I have always been a great fan of the iPhone (I had mine on June 29th 2007 : iPhone D-day), but I haven’t found many applications that were making good use of the “notification” feature that Apple added in its last iPhone OS, until today. AppNotification is an app that allows you to receive any notification. Its creator, Fabien just spent the last day interfacing his app with Superfeedr and the re
PubSubHubbub is a free, open and decentralized protocol. It relies on webhooks to push feed updates in real-time from publishers to subscribers (feed readers). Most importantly, PubSubHubbub builds on existing infrastructure: implementing it won’t change or break your current polling infrastructure, and if for some reason something fails, you can still resort to polling (like you probably already
With more and more users, we get more and more feedback and we’re slowly but surely improving our service to take into account all that feedback. As a consequence, every once in a while we need to push a new codebase with slight changes in the API. Hopefully these changes should be backward compatible, which means they shouldn’t affect any of the existing applications. This changes will be release
このページを最初にブックマークしてみませんか？
『blog.superfeedr.com』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
