Hacker News Reader

Comment by DigitalSea | Hacker News Reader

Amazing. I've only dabbled with Meteor lightly, but this takes it to a whole new level. Telescope is so fast, you've done an exceptional job building this my hat goes off to you and thank you for open sourcing it so others like myself can learn how to build a Meteor app.

My only concern is what about search engine visibility? If I were to build an app like this with Meteor would Google see the page content?

View on HN

Hi, thanks, we appreciate that!

Meteor does have the spiderable package (http://meteor.com/blog/2012/08/09/search-engine-optimization) which means that URLs such as http://demo.telesc.pe/posts/08d0105f-0a1c-43a1-b11a-5ba8875e... will be indexed by google.

(Actually they won't because we haven't enabled spiderable in this deployment of Telescope, but it would be a one-line change to do so).

Oh wow, I did not know that. Well I'm sold, thanks for replying. Meteor looks to be a pretty promising way to build realtime applications, I see what all of the fuss is about now.

Not sure how configurable this is, but would it be possible to have less ridiculous URLs? An idea might be to take the hash (it looks like you're using some sort of hash?) and then encode it base-36 like reddit, or even, (for a bit of individuality and human memorability) take a list of some number of words (preferably large) and encode it in that base where the digits are the words, e.g base-3 with 0 = telescope, 1 = dog, 2 = house, and so 3 = DogTelescope, 5 = (3+2) = DogHouse, 7 = (2*3+1) = HouseDog etc.

Yeah, we're using the default Mongo IDs but we could probably come up with a better URL scheme. I'll add it to the to-do.

Curious about your "fast" comment. Tried to get in twice with the "Login with Twitter" option and things just spun and spun until they timed out. What are you commenting on? Speed of adding new articles or... ?

We might be hitting the limits of Heroku's free instance… Try http://demo2.telesc.pe/ or http://demo3.telesc.pe/ if the site's demo link doesn't work.

how many concurrent requests killed it?

About 150. This seems pretty good to me for a free Heroku instance, it could probably handle more on AWS.

And this is CPU bound or memory bound?

Hard to know since this is Heroku… But the Meteor guys are on it, they take performance issues seriously.

Especially since they've switched to performance and scalability now post 0.5.

Reply on news.ycombinator.com