News for hackers. Stuff that matters.
Re:Meteor is now MIT licensed by heretohelp on Saturday April 21, 2012 @01:31AM (#3870999)
More importantly, how do I keep clients from fucking up my database? How is security being done?

Seriously, if I'm not capable of baking limitations into data persistence/logic at the server level then this entire framework is worthless except for building up a portfolio of cute demos that can't be used for any real work.

Re:Meteor is now MIT licensed by dmix on Saturday April 21, 2012 @01:51AM (#3871045)
As this question comes up every single time Meteor or Firebase is brought up, I think its fair to say that "we're working on it" wasn't and isn't a good enough answer.
Re:Meteor is now MIT licensed by hbbio on Saturday April 21, 2012 @04:31AM (#3871306)
You should also have a quick look there: http://news.ycombinator.com/item?id=3858838
Re:Meteor is now MIT licensed by tjogin on Saturday April 21, 2012 @04:56AM (#3871339)
Reading the documentation would be good start.
Re:Meteor is now MIT licensed by analog on Saturday April 21, 2012 @02:00AM (#3871067)
From their newsletter which just went out, can't find a link online.

"Please make sure it's reasonably secure. Meteor security isn't as hard as people think. Admittedly it doesn't yet have the delicious "candy coating" that the database and DOM update stuff has, but we didn't, like, forget to put any in. Here's what Made With does:

* Use Meteor.publish() and Meteor.subscribe() to control what clients can see (remove the 'autopublish' package first). Actually you may not need to do this for a blog.

* Use Meteor.methods() and Meteor.call() to define secure server functions and call them from the client. Then lock down your app by disabling the "training wheel" methods that let any client do any write."

Also from a quick skim of the server code itself it looks like they are using connect, so you it's possible that you could roll something up using a connect middleware package like everyauth. [1]

That would mean hosting your own server though rather than using the simple meteor deploy.

[1] http://everyauth.com/

Re:Meteor is now MIT licensed by heretohelp on Saturday April 21, 2012 @02:14AM (#3871093)
>* Use Meteor.publish() and Meteor.subscribe() to control what clients can see (remove the 'autopublish' package first). Actually you may not need to do this for a blog.

Scoping isn't enough.

>* Use Meteor.methods() and Meteor.call() to define secure server functions and call them from the client. Then lock down your app by disabling the "training wheel" methods that let any client do any write."

So, I can't make a production-grade app unless I use 0% of the magic.

Re:Meteor is now MIT licensed by foolinator on Saturday April 21, 2012 @03:54AM (#3871259)
You're absolutely right. But all frameworks have to go through these humps. Hell, I remember just 2 years ago having MongoDB in production it would regularly crash. We got rid of it in production, but I'd reconsider using it now.
Re:Meteor is now MIT licensed by StavrosK on Saturday April 21, 2012 @08:43AM (#3871642)
Which features, are making you consider MongoDB? I'm asking because I wrote a (really short and small) MongoDB-ish abstraction layer over SQLite the other day (https://github.com/stochastic-technologies/goatfish), and it seems to me that it's trivial to emulate the MongoDB queries and various other features over SQL without all the hassle of it eating your data or requiring 100 GB of RAM for a few indices.