Actually, Facebook's 'publish_stream' extended permission, which has existed for 1-2 years, already gave developers the ability to publish on your wall, without getting explicit confirmation on each article.
Similarly, for Spotify to do this Activity stuff, you need to give them an extended permission called 'publish_actions'.
If anything, actions are less dangerous, since the size and visibility of the content is significantly more limited than are wall posts.
Anyone saying otherwise either is linkbaiting or truly does not understand the Facebook platform.
And a consequence of that is my "Facebook stress" everytime I allow an app to publish on my wall. I don't want them to, and I am forced to accept because otherwise I could not get access to the app.
I have to check my Fb profile that nothing gets posted everytime this happens.
In theory you could just not use the app. Also, tell the app owner why you're not using it. However, I'd say that there's generally no consistently way I've seen that FB gives you to give feedback to app owners - certainly ones which you're not actually a user of the app too.
If enough people did that (or started to from now on) the demands for extended app privileges might drop.
Similarly, for Spotify to do this Activity stuff, you need to give them an extended permission called 'publish_actions'.
If anything, actions are less dangerous, since the size and visibility of the content is significantly more limited than are wall posts.
Anyone saying otherwise either is linkbaiting or truly does not understand the Facebook platform.