61–70 of 147 posts
Team Hoodie here. Happy to answer any questions you might have :)
Hi , from the docs " Hoodie will only sync data to the database if it belongs to a user!" will there be ways to manage some complex ACL scenarios ?
If you have a specific scenario in mind, I'm happy to elaborate.
Team Hoodie here. Happy to answer any questions you might have :)
Is it just me or are there some dependency management issues? Missing boom, shot, now lru-cache...down the rabbit hole.
How does this compare/contrast to Meteor?
Very nice tool, quite convenient .. having just picked up a MeteorJS requirement for a project, this looks like a nice distraction. ;)
Earlier quoted context omitted.
The difference is server-side validation of untrusted client requests.
Hoodie does server-side validation of untrusted data.
"This document describes functionality and features that don't exist yet."
Giving full email privileges to the client is a terrible idea. Even if you do rate limiting, you're essentially allowing anyone to get your mail server(s) blacklisted and all future mail from anyone marked as spam. In general, most people would be naturally apprehensive about federating their entire user authentication system through a third party. However, I suppose that by using hoodie you are supporting a group of…
I'd be also very interested in your basic use cases that you think Hoodie couldn't handle. It would certainly be great input for the project.
Team Hoodie here. Happy to answer any questions you might have :)
So let's just deliver all our business logic as JavaScript to an entirely untrustworthy client! Whats the worst that could happen?
Earlier quoted context omitted.
I looked at pouchdb's website and there's a lot about browser support but I didn't see any docs about the data model. It seems you're expected to know how CouchDB works?
Yeah, it’s a document database, uses UUIDs and revisions for identification and does HTTP-based P2P replication. In Hoodie we abstract that away in a simple to use `hoodie.store` object with the usual `add()`, `update(), `find()`, `findAll()` methods for operations. No need to know about the CouchDB/PouchDB specifics, just store your objects :)
Since that's the heart of the problem being solved, it's weird when the docs leave it out.
Earlier quoted context omitted.
Hoodie works no different than Gmail. What’s the worst that can happen there?
Well you sure as shit aren't going to see "hoodie.account.signUp(username, password);" in Gmail's client-side code. Gmail's code base is not a "offline first, mobile first" platform. The API that is exposed to the client-side is fairly light (watch the traffic). I highly suggest use research "business logic flaws" in web apps. Anything Jeremiah Grossman has said on this topic is good stuff.