It is my understanding that apps can no longer publish automatically at all ;
"In order to provide users with experiences that meet their expectations, we will no longer approve custom actions that publish stories as people consume content. These apps must use the appropriate built-in actions or create a different sharing experience."
> It is my understanding that apps can no longer publish automatically at all
You are misreading what they are specifically saying. First, we are talking about custom actions. Built in actions that FB provides are still allowed to be auto-published.
Secondly, the restriction is merely on consuming content. You can debate what that means, but performing specific actions can still be auto-shared. However, simply consuming content, using custom actions, will not be permitted.
So, listening to music can still be reported as you listen to music (this is a built in action), but viewing a picture won't fly.
You can easily achieve that by redirecting traffic from facebook to the app request page and simply allowing people through when they chose 'cancel'.
You do not get to show the app permission request as a dialog but that te only way you can put a gate before your contet and still allow ppl that select cancel to go through.
Moved back from coffee-script because event though all its syntactic sugar is really helpful to program faster, it seems to me that CS lacks clarity and still has too many ambiguities.
Unfortunately I do not see incentive for the mass to move from facebook to this new solution.
It is really though already to educate ppl about privacy issues already let alone trying to convince them to migrate from facebook to another solution.
Even in a best case scenario where there would be a general consensus about leaving facebook, the migration task itself is so huge that it would probably make the project fail on its own. Nobody wants to be scatered between FB, Twitter, the other bazillion sites that we're subscribed to and this newer one.
The state of todays base of node (v8) has nothing to do with the concept/paradigm its trying to put forward -- that is event driven web apps. Hence, one must not discard node as a bad solution only because v8 is not optimal in all situations.
