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

Using Equinox CommandProvider to make OSGi console interactive.

After fiddling with the First Bundles that "Hello World"-ed upon Activation, You want to see more interactivity in OSGi. Although Using OSGi for an interactive Command Line Application would be like this one would be, well, a callable over-kill, I am going to start with an example and Expand it in later posts. So, please Welcome CommandProvider. CommandProvider is an EQUINOX specific API for extending the Console. This basic Example illustrates how to get a command from console and do something in java and also gets your feet wet on Service Registry package com.so.examples.commandconsole; import org. eclipse .osgi.framework.console .CommandInterpreter; import org.eclipse.osgi.framework.console.CommandProvider; public class DisplayMessageCommand implements CommandProvider { public void _say(CommandInterpreter ci) { ci.print("You said:" + ci.nextArgument()); } @Override public String getHelp() { return "\tsay - repeats what you say\n"; } }

How to Make a Local (Offline) Repository in Ubuntu / Debian

If you are in a place where you dont have internet (or have a bad one) You want to download .deb packages and install them offline. Each deb file is packaged as a seperate unit but may contain dependencies (recursively). apt-get automagically solves all the dependencies and installs all that are necessary. Manually install deb files one by one resolving each dependency would be tedious. A better approach is to make your own local repository. Before you actually make a repo, You need *all* deb files. You dont practically have to mirror all of the packages from the internet, but enough to resolve all dependencies. Also, You have to make sure, you are getting debs of the correct architecture of your system (i386 etc) # 1. make a dir accessible (atleast by root) sudo mkdir /var/my-local-repo # 2. copy all the deb files to this directory. # 3. make the directory as a sudo dpkg-scanpackages /var/my-local-repo /dev/null > \ /var/my-local-repo/Packages # 4. add the local repo to sour

javascript maxlength for textarea with \r\n breaks in java (esp Firefox)

Textareas allow new lines to enter. These are represented by \n (1) or \r\n (2) characters. But when you save to DB you have a limit to certain length of chars. There is no maxlength attribute in HTML that will stop you from entering data. This is generally acomplished by Javascript. You do a onkeyup hook and stop event or trim after textarea.value.length > maxlength. There are many other solutions out there.. But.. Here is the problem that most of those solutions overlook, How do you deal with the count on \n and \r\n representations. Lets first see how it matters. If the text entered has new lines, the length is calculated differently in Firefox and IE. When you enter a Text like 01234 567890 You expect the textarea.value.length to be 11. (10 chars + new line).On the backend, however, java would recieve it as 12 chars (10 chars + \r\n) (this is irrespective of FF or IE). So you are effectively saving 12 chars to DB. Worse yet, IE seems to figure textarea.value.length as 12 (