Hacker News Reader

Comment by austenallred | Hacker News Reader

While this is buggy/not ready for release, here's a way to follow this on social media.

http://fastlane.grasswire.com/

PS. Here's our launchrock page if anyone cares http://grasswire.com

I would like a way to filter out everything that includes the word "pray" in it unless it is from a respected news source. 90% of what any person ever says in response to everything that happens in america is "pray for it". It's sort of muddy to look at.

Actually it's just completely obnoxious. I like the site though.

You're absolutely right. "Pray for boston" is trending on Twitter and Instagram right now, so it really muddies up the feed. We'll get a way to put negative search terms in there.

"Favorites" is a morbid word to have on this page. Maybe consider "Highlights" instead.

Good call, thanks for the feedback!

Highlights is pretty bad too.

We used to call it "best of" then went to "favorites." It obviously won't be favorites anymore - didn't think of this use case.

How about "Notable"

as a general rule, avoid the word favorites altogether in any software, unless you are certain it will only be used in the US. We spell it favourites, and "favvOrrittez" as you seem to spell it, really grates. Esp in IE, whereas Net/moz always called them bookmarks. Fayvritz.

Perhaps just a star? You can call them "starred" posts. Seems somewhat more neutral.

JUST FYI: This is camping on a simple dev server, so I'm sorry it keeps going down. I'm doing my best to keep it online. Thanks!

Should be up now

This is incredible.. but at the same time you've exposed me to the multitudes of people that are just so hungry to make a "viral" image. I can't believe it.

One of the many:

http://distilleryimage7.s3.amazonaws.com/a9ba58b6a61111e2901...

Yeah, this is a problem, especially with Instagram. As a random aside, watching this has been a really interesting look into how viral marketing is done.

Love it! This is the future of news consumption: firehose.

You should really have linkbacks to the text/photos you're pulling in.

if it's yours: nice, but consider refresh rate of 'media' a bit lower. I can't read the captions before it's pushed down.

Would be great if mouseover froze the lane underneath. For bonus points you could continue to load new tweets but add them above the screen.

Will do. It is by no means ready for release, but you know...

This looks to be shaping up well. Might I suggest a new word for "Favorites" though. Maybe it is silly but it seems odd to me to Favorite gore pictures et. al. "Important" or "Impactful" or something else might be a better word when the content could be that of loss and suffering.

Aaaaaaaaaaaaaaaand, it's gone... Shouldn't have told everyone about it. Clearly it's quality made it viral.

It's pretty good at holding traffic. Not so much when it comes to curious "stop by, see what's up, open a websocket, leave." But we're working on making it better, and it is back and running smooth now. Thanks for checking it out :)

Congrats. You have a hit!

cool, I get it. I see there is a lot of ux polishing ahead, but I like the overal concept.

an on/off button for auto-refresh may be a good idea.

signed up for the notification email.

I am interested in what this was as it sounds cool, but it is down at the moment. Could you tell us a bit more about it?

Basically it searches and refreshes all of the social media networks in real time (twitter, youtube, instagram, flickr, wordpress, blogger) and shows them in three streams, allowing you to "favorite" the best stuff you see and separate it out.

But the really cool stuff is what we can do with data of what users have favorited.

How do you plan to get around the Twitter syndication rules and regulations once this site takes off?

This is a really good question, and should be referring to all apis and their limits. This was my approach: Create a parser that lives off of apis, just under posted limits. Although we had a few thousand visitors today, there was only one direct line to each data source. There's a viewer server that reaches for data every so often depending on your desired speed (I think it's set to somewhere between 1 and 2 seconds) and broadcasts it. So if the parser goes down, or tags change, or services get mad, you can fix and restart without requiring clients to refresh. I'm still not in love with the solution, but it worked nicely today. Thanks!

Thanks for the explanation. I worked for a one of the eleven companies that still had rights to access the Firehose after the debacle and I saw a lot of great projects stymied by the new rules.

This is fantastic. Truly!

Would you say that your site traffic is blowing up in response to this event?

EDIT: Sorry, sorry--in a weird headspace from the news. In all seriousness, did you actually just launch a product in this thread?

EDIT2: Just remember, when launching a product--it's not a sprint, it's a marathon.

150 visitors on the site right now, so I guess it depends on your definition of "blowing up." We're getting visits from YouTube, Twitter, Reddit, etc. but I haven't dug into where exactly.

Proof: http://d.pr/i/LDao

And as to "launching" in a thread, I don't really consider this a full "launch." Our product is needed, so even though it isn't ready we pushed it live.

I checked it out, and it's a cool product. I agree with somebody elses's comment--this is a useful thing to have in this day and age.

Out of curiosity, how are you picking which things to feed? Your ticker rate for tweets seems fixed, so you are discarding some things, right?

Yeah, like I said the product is brand new. It discards everything with "RT" or "Retweet" as well as a few other things in it (if it weren't finals week it would discard everything with "pray," but we should be taking our exams right now). Soon it will split up different tweets and show them to different people.

I don't really think your "EDIT2" is called for.

Reply on news.ycombinator.com