Skip to main content

FaceBook Privacy – reality check

Many privacy evangalists, like Dan Yoder, have taken facebook to a beating, as far as recommending you quit. This follows a series of Privacy policy changes from Facebook on an excuse to protecting themselves. It turns out Dan's points have quite a few compelling reasons to actually quit.

However, personally, I would not - but would definitely advice a lot of caution to use ANY of FaceBook's features. Always protects yours and your friends' information. Reduce the visibility of any information to minimum or atleast only to your friends. And if possible omit it all together. As a general rule of thumb – only let that information go into facebook that has NO implication whatsoever, if revealed. To ANYONE – And I mean - your boss, collegues, girlfriends, wifes (ex-wifes :P).

For  quick reality check how much can be dug out of your facebook profile WITHOUT logging in, you can head on to http://zesty.ca/facebook/. And remember, this is as much information ANYONE can get.

As a matter of fact, The Applications (read farmville, flirtmeter, *What/How do you think/do/feel @#!$#* quizes) you approve and Sites you do *Facebook Connect* with have even more access to data (yes, probably even the ones you have reduced visibility. As a Developer, I know, how much information is available. And if its in the wrong hands (read *Those stupid Quiz* apps) – it will haunt you and your friends.

So please. We all love the social benifits. Like they say – To earn some you have to lose some. Just be vary, you are losing a lot for a lot less to earn, by not keeping secrets on facebook.

p.s. This also applies to all other Social Sites. Especially those which dont have enough credibility, inadequate privacy policy. These sites are predators harvesting your information for their monetary gains. My advice – be knowledgeful – and dont send me a friend invite otherwise!

Popular posts from this blog

Appcache manifest file issues/caveats

Application cache (appcache) is a powerful feature in HTML5. However, it does come with baggage. Many (see links below) advocated ferociously against it due to tricky issues it comes with. For someone who is just testing waters, these issues may throw them off grid. Knowing them before hand helps reduce some unpredictable effects.

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value>