julien

35 ms·

331.
State of the Realtime Web : the Publishers (blog.superfeedr.com)
23 points by julien 16y ago|2 comments
332.
The Dream Team Quietly Gathering Behind Real-Time Service SuperFeedr (readwriteweb.com)
3 points by julien 16y ago|0 comments
333.
by julien 16y ago
As much as I like your approach, I have this feeling that not everything is butterflies and unicorns. Sometimes, you have to find a way, and the way is clearly a "split-up". However, I dob't agree with Fred's either. This kind of things is
334.
by julien 16y ago
I fully understand and agree with this. All work needs to be paid. In our approach, there are some projects that involves our services, but most of them are about build OSS pieces of infrastructure that may use (or not) our stuff, but that
335.
Ask HN: Best Way to find great interns for the summer?
8 points by julien 16y ago|5 comments
336.
XMPP library for node.js(github.com)
42 points by julien 16y ago|17 comments
337.
Libexpat XML SAX parser binding for node.js(github.com)
1 points by julien 16y ago|0 comments
338.
KumoFS looks like a good Cassandra equivalent(blog.superfeedr.com)
1 points by julien 16y ago|0 comments
339.
Digest and heartbeat notifications(blog.superfeedr.com)
2 points by julien 16y ago|0 comments
340.
Consistent Hashing in Ruby(github.com)
1 points by julien 16y ago|0 comments
341.
20 Million Atom entry per day(blog.superfeedr.com)
2 points by julien 16y ago|0 comments
342.
PubSubHubbub and Synchronization(blog.superfeedr.com)
3 points by julien 16y ago|0 comments
343.
Redis-cluster Design doc(github.com)
1 points by julien 17y ago|0 comments
344.
Ruby Fibers may confuse(blog.superfeedr.com)
2 points by julien 17y ago|0 comments
345.
by julien 17y ago
Nice market segmentation :) As for Superfeedr, we already have a pretty big chunk of the blogsphere and as long as you know what you want (feeds), we can provide that to you. Other services that you mention suffer from spam, because they ha
346.
Gowalla Adds Real-time Feeds and Activity Streams(readwriteweb.com)
12 points by julien 17y ago|2 comments
347.
At last a Ruby Memory profiler : Memprof(blog.superfeedr.com)
1 points by julien 17y ago|0 comments
348.
by julien 17y ago
Micah, I'm sorry the experienced wasn't as smoothed as expected. We can definetely help. I left some comments on your blog. Please get in touch.
349.
by julien 17y ago
Julien from Superfeedr here. Please get in touch wit any issue/question you may have. I'm sorry Micah had so many issues and I'll try to help him find his way.
350.
PubSubHubbub and Twitter(blog.superfeedr.com)
1 points by julien 17y ago|0 comments
351.
Wordpress's blog support PubSubHubbub(en.blog.wordpress.com)
13 points by julien 17y ago|2 comments
352.
On Outsourcing(blog.superfeedr.com)
4 points by julien 17y ago|0 comments
353.
by julien 17y ago
Thanks man, I'm honored. I wish I had more time to write on more of our infrastructure stuff! I think many people use redis, but don't necessarily advertise it, which is also one of the reasons of our "coming out" :)
354.
by julien 17y ago
That's part of what makes life fun :)
355.
by julien 17y ago
I think the only way to is add RAM when your indices grow.. that's what we did up until now. There is absolutely now way a data store to keep this kind of performance as soon as you involve a disk, so, yes, the secret of whatever datastore
356.
by julien 17y ago
So it's actually each of the server that sees this traffic :) And yes, we're nothing (yet!) compared to what the big guys just. However, most of the tim they used their very own software to achieve that; I'm just using out-of-the-box redis,
357.
Redis at Superfeedr(blog.superfeedr.com)
54 points by julien 17y ago|11 comments
358.
Who Implemented PubSubHubbub (blog.superfeedr.com)
1 points by julien 17y ago|0 comments
359.
by julien 17y ago
PubSubHubbub : Bringing an end to the stupid feed polling we're tried to fight for years (see SUP from Friendfeed, AtomStreams... etc).
360.
Feediscovery : feed discovery made easy(blog.superfeedr.com)
2 points by julien 17y ago|0 comments

More ›