not sure if telescope is a good boilerplate for meteor.
I think it tends towards unnecessary abstraction complication and ends up rather brittle in the end.
Try changing the post frequency from "daily", for example. The code complexity, in this case, making a previously non-existing abstraction (post frequency) difficult to alter... better to start with the basic meteor 3-file default app (or something similarly simple) and build one's app (and knowledge) from there...
I'm a pretty experienced Meteor dev and I find telescope to be confusing...
As a front-end developer, I cringed when I saw how much Telescope (or is it Meteor?) relies on global scope. To see what I mean, inspect the window object in their first example site <a href="http://crater.io/" rel="nofollow">http://crater.io/</a><p><pre><code> Object.keys(window).filter(x =>
window[x] instanceof Function &&
!/native code/.test(window[x].toString()))
</code></pre>
120 user-defined global functions, and that is not counting all global variables... yikes!<p>(edit: if you're using Chrome, `Object.keys(window).length` gives you 260)
great but I did not like the UI at all. it feels sluggish and too glamourized. Part of reason what makes HN discuss so great is the lack of any UI. no flat or glossy designs. Everythign is texty, so you focus on the text not the buttons or peoples avatars.<p>Another minus is that its written in Meteor.