Privacy and Applications
Topic: Privacy and Applications
Displaying all 7 posts by 5 people.
Post #1
Sharlene wroteon February 20, 2009 at 5:14pm
Do the developers of applications also adhere to the same privacy rules outline by Facebook?
Post #2
1 reply
Allen wroteon February 21, 2009 at 11:18pm
I'd like to know the answer to this as well.
I found this question/topic which is in the 'deleted' section:
http://www.facebook.com/to
both go together, imho
I found this question/topic which is in the 'deleted' section:
http://www.facebook.com/to
both go together, imho
Post #3
Neill replied to Allen's poston February 21, 2009 at 11:34pm
Good point - I've added the below wording into our "Proposed Terms of Service (TOS) Amendments and New Privacy Features Requirements" v1.15.
This is being created/maintained under the discussion topic:
Facebook Users Proposed Terms & Conditions - DRAFT v1.0
Does the following wording cover a potential solution in your opinion?
"For FB applications or add-ons, FBU's should be notified of what personal data will be used by the application, not a generic applications can use any and all of your personal data. When a FBU decides to look at an application, FB will present a description of what the application does first, then after FBU agreeing to go further with another button click, FB will present a checklist of all available personal data types (name, birthday, inbox, chats, wall posts, etc...) and it will be up to the FBU to check which data they are willing to share with the application as described. Being asked to give up all personal data access before knowing what the application does is not acceptable."
This is being created/maintained under the discussion topic:
Facebook Users Proposed Terms & Conditions - DRAFT v1.0
Does the following wording cover a potential solution in your opinion?
"For FB applications or add-ons, FBU's should be notified of what personal data will be used by the application, not a generic applications can use any and all of your personal data. When a FBU decides to look at an application, FB will present a description of what the application does first, then after FBU agreeing to go further with another button click, FB will present a checklist of all available personal data types (name, birthday, inbox, chats, wall posts, etc...) and it will be up to the FBU to check which data they are willing to share with the application as described. Being asked to give up all personal data access before knowing what the application does is not acceptable."
Post #4
1 reply
Allen wroteon February 23, 2009 at 3:31pm
Indeed. Were that added, I'd have no problem allowing applications access that *I* define. This goes right to the heart of control over my information.
As it stands, I can't understand why a bit of flare, for example, needs *any* access what-so-ever. It's an image, for goodness sakes.
As it stands, I can't understand why a bit of flare, for example, needs *any* access what-so-ever. It's an image, for goodness sakes.
Post deleted on February 23, 2009 at 3:49pm
Post #6
Allen wroteon February 25, 2009 at 4:44pm
1. scroll to the end or last page of comments
2. nope =]
2. nope =]
Post #7
Agner wroteon March 23, 2009 at 8:24am
Third party applications is a big security hole. Some applications even require that you accept the application before you can see the terms of use or who is behind it or what information it can access. And even if you can see who is behind an application, you don't know if this information is faked.
Any hacker can make an innocently looking FB application and use it for all kind of evil purposes.
It is a problem that you don't want to say no to an application that a friend has invited you to because you don't want to insult that friend. The nature of FB is to build friendships and it is against this nature to say no to something that a friend offers you.
Furthermore, you can't expect an average FB user to understand the complicated security issues or even know who is behind an application.
We need an approval process or at least a list of applications with known behavior and certified security.
Any hacker can make an innocently looking FB application and use it for all kind of evil purposes.
It is a problem that you don't want to say no to an application that a friend has invited you to because you don't want to insult that friend. The nature of FB is to build friendships and it is against this nature to say no to something that a friend offers you.
Furthermore, you can't expect an average FB user to understand the complicated security issues or even know who is behind an application.
We need an approval process or at least a list of applications with known behavior and certified security.