HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
polleverywhere
firehose
HISTORICAL RECORD2013–2013
polleverywhere / firehose · Not publicly available

firehose

Discover this repository through its Hacker News conversations.

2Distinct people
2Mentions
0Explicit recommenders
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week2 dated mentions

Observed mentions: 2013-05-01 03:21:05 UTC to 2013-10-30 07:16:33 UTC. Weeks start Monday, UTC.

012013-04-29 00:00:00 UTC to 2013-05-06 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 292013-05-06 00:00:00 UTC to 2013-05-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-05-13 00:00:00 UTC to 2013-05-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-05-20 00:00:00 UTC to 2013-05-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-05-27 00:00:00 UTC to 2013-06-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-06-03 00:00:00 UTC to 2013-06-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-06-10 00:00:00 UTC to 2013-06-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-06-17 00:00:00 UTC to 2013-06-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-06-24 00:00:00 UTC to 2013-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-07-01 00:00:00 UTC to 2013-07-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-07-08 00:00:00 UTC to 2013-07-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-07-15 00:00:00 UTC to 2013-07-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-07-22 00:00:00 UTC to 2013-07-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-07-29 00:00:00 UTC to 2013-08-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 292013-08-05 00:00:00 UTC to 2013-08-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-08-12 00:00:00 UTC to 2013-08-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-08-19 00:00:00 UTC to 2013-08-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-08-26 00:00:00 UTC to 2013-09-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-02 00:00:00 UTC to 2013-09-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-09 00:00:00 UTC to 2013-09-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-16 00:00:00 UTC to 2013-09-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-23 00:00:00 UTC to 2013-09-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-30 00:00:00 UTC to 2013-10-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-10-07 00:00:00 UTC to 2013-10-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-10-14 00:00:00 UTC to 2013-10-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-10-21 00:00:00 UTC to 2013-10-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-10-28 00:00:00 UTC to 2013-11-04 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsOct 28

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Apr 292013-04-29 00:00:00 UTC2013-05-06 00:00:00 UTC101
May 62013-05-06 00:00:00 UTC2013-05-13 00:00:00 UTC000
May 132013-05-13 00:00:00 UTC2013-05-20 00:00:00 UTC000
May 202013-05-20 00:00:00 UTC2013-05-27 00:00:00 UTC000
May 272013-05-27 00:00:00 UTC2013-06-03 00:00:00 UTC000
Jun 32013-06-03 00:00:00 UTC2013-06-10 00:00:00 UTC000
Jun 102013-06-10 00:00:00 UTC2013-06-17 00:00:00 UTC000
Jun 172013-06-17 00:00:00 UTC2013-06-24 00:00:00 UTC000
Jun 242013-06-24 00:00:00 UTC2013-07-01 00:00:00 UTC000
Jul 12013-07-01 00:00:00 UTC2013-07-08 00:00:00 UTC000
Jul 82013-07-08 00:00:00 UTC2013-07-15 00:00:00 UTC000
Jul 152013-07-15 00:00:00 UTC2013-07-22 00:00:00 UTC000
Jul 222013-07-22 00:00:00 UTC2013-07-29 00:00:00 UTC000
Jul 292013-07-29 00:00:00 UTC2013-08-05 00:00:00 UTC000
Aug 52013-08-05 00:00:00 UTC2013-08-12 00:00:00 UTC000
Aug 122013-08-12 00:00:00 UTC2013-08-19 00:00:00 UTC000
Aug 192013-08-19 00:00:00 UTC2013-08-26 00:00:00 UTC000
Aug 262013-08-26 00:00:00 UTC2013-09-02 00:00:00 UTC000
Sep 22013-09-02 00:00:00 UTC2013-09-09 00:00:00 UTC000
Sep 92013-09-09 00:00:00 UTC2013-09-16 00:00:00 UTC000
Sep 162013-09-16 00:00:00 UTC2013-09-23 00:00:00 UTC000
Sep 232013-09-23 00:00:00 UTC2013-09-30 00:00:00 UTC000
Sep 302013-09-30 00:00:00 UTC2013-10-07 00:00:00 UTC000
Oct 72013-10-07 00:00:00 UTC2013-10-14 00:00:00 UTC000
Oct 142013-10-14 00:00:00 UTC2013-10-21 00:00:00 UTC000
Oct 212013-10-21 00:00:00 UTC2013-10-28 00:00:00 UTC000
Oct 282013-10-28 00:00:00 UTC2013-11-04 00:00:00 UTC110

What Hacker News says

2 sources
This is a great write-up! We learned a lot of these lessons at Poll Everywhere for http://firehose.io/, which is basically an open source version of Pusher. We do things a few things differently though: * We only have two transport layers: http and ws. We don't bother with a Flash polyfill. * We start the connection via HTTP long polling and upgrade to WS if its (a) present in the client and (b) the network supports it. We've seen a lot of firewalls kill WS connections, so long polling always works. * We treat our "push" channels more like a push edge cache. Because of flakey connections you want to hang on to the past 50-100 messages published to a channel so that flakey clients can get messages if their connection drops. Source code is up at https://github.com/polleverywhere/firehose and you can install it as a gem and have it running i
Read the rest
n 2 seconds. I'm happy to answer questions on here if anybody's got them about building a realtime transport layer like Pusher & Firehose!
In How we built Pusher-JS 2.0 – part 2 – implementation

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.