I found that it was difficult to deal with a web client connection dying, then reconnecting, and recieving messages it may have missed while disconnected. There's a flag you can set for this in Rabbit when creating a queue, but I couldn't really get it to work.
The way Firehose works the client gets a sequence ID per channel that's always counting up. If the connection drops when the client is on sequence 1, then 4 new message come in, and the client reconnects, it will get the rest of the messages up to sequence 5 and wait for new messages.
Nice idea! It could use some design improvements, you should collaborate with a design! Or copy the product hunt style, they've done an amazing job and it's part of their success!
We are the creators of Vista Point an iPad app for travel enthusiasts. We are currently looking for someone helping us in shaping our vision to offer new digital products in the travel sector. We want to create interesting content and travel guides and bring communities (photos, travelblogs,etc.) together with products in the mobile sector.
We would collaborate remote.
If you think this can be interesting for you, visit our homepage and shoot us an email: