Internet Privacy - what is that?

Networking used to be totally private. In the early days prior to www you probably can only join BBS (Bulletin Board). Unless you talk a lot, nothing was revealed about you.

Come WWW. It still worked the same until people start to find out about you so that they could send you advertisements. Google, Yahoo etc got their finances doing just that.

How do others find out about you. Simple. Every search you do is recorded. It will show your habit, your liking, your interest. A good profiler can construct a personality trait just from your search habits.

You think that is about all? Think again. It is not just your search that is recorded. Internet service provider practically knows every internet activity that you do over the internet. Internet snoopers can also sniff out network packages pertaining to you. That's why privacy proponents insists that internet access be incognito.

Recently the great news about the killing of Osama bin Laden showed that the house he lived in has no internet or mobile connection. He is probably aware of the snooping capability and thus only rely on human courier.

There are talks about terrorist watch list. How in the world would they form the watch list unless they track your activities. For example, once I looked up information of AK47 (Assault Riffle) because I want to know where is the "safety catch". By just looking up this information, I probably end up in the watch list as normal people don't look up information of that kind. I showed that I have interest in fire arms and thus may link to killing or terrorist activity. This is how scary it is.

To us common people, we don't really need to fear such collection of information unless we are doing something covert and don't want others to know about it. The information collected about us are probably used to send us ADS. Obviously, you will be profiled to see if you have criminal traits or even terrorist traits.

Many privacy advocates don't even want to be profiled. They want to have the freedom to surf the internet incognito. Many internet browsers start to provide "incognito" window ( a browser window that will not record your activity). They even have a "do not track" setting. The former make it slightly less easy for people to track you. The latter is almost useless unless companies respect your setting and don't track you. The end result is just some meager efforts to placate users. There is no stopping others from tracking you especially government agencies. Unless you totally refrain from surfing net, you will be tracked.

Internet users knows that they are being tracked so they have counter measures. Virtual Private Network (VPN) is used to surf net under "total" privacy. You access to the VPN server and then surf from there. Since you only access to the server and the connection is encrypted, it makes it very difficult to track what you do at the server. Obviously, your activity is still know by the VPN server but it is still better than nothing.

Some VPN server even provide free access. I am not that paranoid thus I never subscribe to it. Just do a search for VPN and surf to find the number of providers available.

I really don't care about being profiled as I am just a poor nobody. What I hate is the ADS. Well, I use Firefox that have good plugins that blocks most ads. In Chrome, I don't surf with it. It is just used for mails and social networks (my Firefox even blocks Javascript from running). I do have Facebook adBlock installed plus the not-so-effective ABP. It is good enough for me.

Communicating with Apple Web Services (GSX) via Filemaker

Web services according to WikiPedia is "a method of communication between two electronic devices over a network." There are websites that provide information as a service. Sites like Google Language API which allows you to translate your website directly without you having to create the translation yourself. This means you could translate your web site to hundreds of languages just with the web services code.

In plain language, web services allows you to call a web site from your website by providing a request, or consuming a request ( a most confusing term), with some data. The web site will then provide you with the result. For example, I send a request to Google Language API with "Japanese" as the required language and "How to speak Japanese" as the data. Google Language API will understand your request and responds with the result as "日本語を話す方法". When you change the language to Korean, and use back the same data, the API will respond with "일본어를하는 방법". Isn't that easier than you writing three different pages each with a different language?

Some web sites provide more than just one functionality. You can actually use the service to perform various actions by using it like a "function" with "parameters". In layman language, it means you need to tell the web service what you want to do with the data provided by you. The web services will understand your request and perform the exact action then return you the result. For example, I can go to a plant information web site and do search, update, create, delete, etc. just by calling the same address with different info.

In a web page, we will normally use Javascript to do the calling and showing the response using the technique call AJAX and a newer technique called JSON as data. It has all the functionality available to do it. You just need to compose what to send and get what is returned.

I have the opportunity to write programs using Filemaker (A database program owned by Apple). It has very good interface that allow very easy creation of database interfaces and web pages. However, its scripting facility is a bit lacking. This is especially true when trying to use the technology above to do translation. You practically have to write a code to do the functionality then write the code that make use of the functionality. That is double the work. Luckily there are plug-in that expand the capability of the application.

The following is a description of what I did to call a Web Service from Apple itself using Filemaker. It is a web service provided by Apple to its agents that provide repair services to its customers. The service provides a number of requests with its associated data. For example, if I need to order a spare part, I will call the web services with the request "orderPart" and "xxxxxx" as part number. Apple will then create an entry in its database that records your request and then send the part to you.

The request is send as a XML that contains the "request action" and the data. The response is also a XML that contains the result of the request. In this way user will see the same display yet the transaction is made in the back ground. The Filemaker program will then display the respond data so that user can see the result of the transaction.

Actually it is easier said than done. There is no such functionality available to talk to web services. Filemaker does have a "insert from URL" function that could call a web site and display the result in a field (a place where you can type in a form). However, it only shows the XML returned from Apple directly which is mostly not understood by user. Its XML facility is also not suited for manipulation with XML in this way. Thus the task is to create a code that could call the web services, send the request in XML format and translate the result to user in a readable format.

The very first task is to create the proper XML. Since there is no such function, it has to be created. XML node is generally in the form "<node>value</node>". As you can see, creating it is not a problem. So instead of typing the "node" and the "value" manually, you just need to call the subscript and pass it with the correct parameters.

Problem is that Filemaker (FMP) cannot pass multiple parameters. It does not have arrays too. There is, however, a "List" function that you can use like "list(value1,value2)". Thus you must combine the two information into one by using "list" before passing it as a parameter. You can even create a sort of array by creating a list within a list.

The XML example above is the basic format. XML, like HTML, also can contain properties. It is in the form "<node property='xxxx'>value</node>". Obviously these nodes can be nested. Setting the property nodes aside (as it is normally not used in "body"). There are four ways to create the XML.

1. The beginning node ("<node>"). With this and the ending node, you can create a nested node to what ever level you want.
2. The ending node ("</node>")
3. The complete node with value ("<node>value</node>").
4. The NULL node ("<node/>")

It is very easy to take the first parameter and treat it as a node by enclosing it with "<" and ">". The value is placed next then the first parameter is used again by enclosing it with "<" and ">".

For those that only need the node name like 1,2, 4 above. It is constructed accordingly.

The value must not contain characters used by XML itself like "<" and ">". Therefore all the values have to be filtered or modified to ensure that the value does not end up as the XML itself. This is called "escaping". With this we are able to construct any XML body. This script will then be store as a script by itself. It always write to a global variable like $$xml so that it does not even need to return a value. The script then becomes a function that create xml nodes.

How then should we add headers. It is very simple. Since we always access to the same address, the header seldom changes. Why not just store it as a plain variable? This is exactly what I did.

In another script we will assemble the xml step by step. Fist we store the header into the variable $$xml. Then we use "run script" to run the script that creates the xml by passing the appropriate values beginning with a code that define what type of nodes we are creating. Repeat the subscript till the whole xml is complete. The result is then a well formed xml. You could even test the output by storing the $$xml in a field or just a custom dialog to ensure that the xml is correctly form by copying and pasting the result in a xml editor.

With the xml available, the next task is to send it to the Apple web services (GSX). Luckily, this functionality is available as a plug-in. BaseElements has the plug-in that could do a post to a website and get a respond into a variable instead of a input field. This functionality is exactly what we need to talk to the server.

The last part is to get the result out of the xml. This functionality is again not available. However, BaseElements does have the functionality to extract values from the xml. It may not be the functionality that I am looking at but at least it can be done. The best way is to transform the whole response xml into something  that is humanly manageable like an array without having to write long codes to do it. But then with the limitations, it is still better than nothing.

The conclusion is that Filemaker can talk to web services. With the database capability, getting chunks data out of the web services is a possibility.

MBS has an excellent example of communicating with GSX. MBS Blog.

Apple will be changing the format used for sending and receiving data.  Please go to part 2 to see how it could be done.