<major snip> I have thought about plugin sandboxing and then I had to open the windows because the smell of overengineering was killing me.
I like to fix problems we have. One problem we have: we don't have a decent mail app. One problem we don't have: inexistent plugins crashing the aforementioned inexistent app. I'll be the first one to call for better plugin sandboxing when they start crashing the app. Until then, I think all we can strive for is keep future plugin sandboxing in mind when developing the core. *I believe an all open approach is the correct path for 1.0*, because we don't want to prematurely limit what can be done (much less, write the code for it). Once we get a feeling for the Flashes of our ecosystem, we can investigate what deserves some sandboxing. Regardlessly, with a technically able community and a plugin website with the appropriate social features, I'd say we may be able to weed out the bad plugins without a complex technical solution. In addition to that, open plugins, say, on github, will be easily patchable. _______________________________________________ [email protected] mailing list List help: http://lists.ranchero.com/listinfo.cgi/email-init-ranchero.com
