This particular patent describes the process for 3rd party sites to tell Facebook about something the user did (new Open Graph API, anyone?), which subsequently can be shown as an ad to the user's friends, i.e. "Your friend blah has bought something on This Service, do you want to do so too?" (some peer context for ads, which facebook already tries to do for things like fanning pages).
This is quite different from the meaning implied by this post, which the first 2 quotes were addressing, that Facebook tracks and correlates browsing patterns of users across the internet without their consent.
You're quite right. This is why apps have a new permission dialog to show you exactly what gets shared, which you have to click accept prior to using it. As long as the app isn't facebook only, you can always use it without the facebook integration. and if it is, there will probably A facebook-free competitor you can use.
Well, the fiddly part so far seems to be that's set to a single level (announce/don't announce) and every different app needs its own mute button.
Spotify, for example, will happily announce to the world whatever you happen to be listening to, and there's no simple way to hit "mute". So you're going to need to build a separate "mute" button into every app, on every platform, and have enough trust that it will work ...
You can easily shut down any kind of activity. I clicked on the settings for an Rdio song I auto-posted and the option of "Don't show this kind of activity from Rdio" (paraphrasing) showed up.
I hate to single you out, but the amount of blatantly unresearched, inaccurate statements in this discussion is really disappointing. This is a powerful, well-implemented (easy to opt-in/opt-out of any broadcasting on an app by app basis) feature.
So what you are saying is maintenance! maintenance! and more maintenance.
This is no longer a great user experience and it's not longer a social network... No, this is without a doubt a media venture that will do anything to make their advertisers happy... at the expense of the users.
I wonder if you see your own contradiction? You had to go out of your way to make a point that users need to now attend the settings for every single product they use and maintain additional information. It seems that with every year things get more and more out of hand
Today, as an FB user I'm not happy. For one, I had to download a plug in for the new ticker (a news feed with in a news feed?) just to get rid of the annoyance. Tomorrow we will have to deal with a dozen more ticks.
No contradiction: I had to turn on Rdio'd FB app to broadcast my songs to begin with. Everything is opt in, not opt out. If you're not interested in that, you don't maintain anything.
Real time physics simulations of deformable objects these days tend to be based on fairly accurate physics models. The major issue facing such simulations today is that it's difficult to simulate extremely rigid objects at high frame rates, due to the non-linear aspects of the underlying forces. The challenge is to take shortcuts and find optimizations that gets you decent looking results while not being overly slow or unstable.
Correct me if I'm wrong, but it seems that while using the client-side auth flow does not prevent a malicious program from pretending to be another facebook app, it forces the malicious application to be downloaded and executed as it must be able to catch the redirect to a different url with the access token, which a web app cannot do.
Once you are downloading and executing a malicious native app, you're screwed anyways since it can do whatever it wants like read your cookies and hijack running applications... (I'm not considering java or flash applets, depending on how their security works this may still allow drive-by spammage as a legit app).
It does allow a malicious user to easily write something that impersonates a legit application, though it's limited to spamming his own account.
Content from spammy apps are hidden when the app is disabled. If you think about this it sort of makes sense: if the app is sending lots of crap without user consent, merely disabling an app does not remove all the crap it has already sent out.
I don't think the posted content are actually deleted though, they should be unhidden when the app is unblocked.
The ones prior to 2010~2011 used scheme, and it tracks SICP fairly closely.
http://webcast.berkeley.edu/playlist#c,s,Fall_2010,EC6D76F0C...