Εκτροχιασμοί
Προ κάποιων εβδομάδων ο Νίκος Σμυρναίος έγραψε στο blog του σχετικά με το ζήτημα της παρακολούθησης των συνδέσεων του διαδικτύου στα πλαίσια της προσπάθειας, τόσο κρατικών όσο και ιδιωτικών φορέων για τη μείωση της ανταλλαγής πνευματικών έργων μέσω του διαδικτύου. Σήμερα διάβασα από το blog του Ματθαίου Τσιμιτάκη ένα παρεμφερές άρθρο που παραπέμπει και εμπλουτίζει το πρώτο. Ας σημειωθεί πως ο Ματθαίος αναφέρει και ένα κείμενο γραμμένο από τον Νίκο Δρανδάκη, το οποίο παρ’ότι συναφές έχει σαφώς διαφορετική θέση και περιεχόμενο και το οποίο δε θα σχολιάσω εδώ.
Ας τα πάρουμε όμως από την αρχή. Όταν διάβασα το άρθρο του Νίκου Σμυρναίου προβληματίστηκα. Η θέση μου σχετικά με την ΑΕΠΙ, τον ΟΠΙ, το copyright και τον επιχειρούμενο δαιμονισμό της μη-κερδοσκοπικής ανταλλαγής μέσων πνευματικής ιδιοκτησίας από τις μεγαλοβιομηχανίες των ΗΠΑ και της Δυτικής Ευρώπης είναι γνωστή σε όσους διαβάζουν τακτικά τα κείμενά μου. Κατα συνέπεια συμφωνώ απόλυτα με και επικροτώ την δημοσιοποίηση της όποιας παράτυπης (πόσο μάλλον παράνομης) ενέργειας από τη πλευρά των εν λόγω οργανισμών και των εκπροσώπων τους σε κάποιο blog ή άλλο δημόσιο μέσο και τη προσπάθεια αποτροπής του στραγγαλισμού των ατομικών δικαιωμάτων στο διαδίκτυο μέσω αδιαφανών, αντικοινωνικών νομοθετικών ή άλλων κανονιστικών πράξεων.
»
Vodafone is currently trialling Wimax in Greece and Malta
Έχει ακούσει κανείς κάτι; Η μόνη περίπτωση δοκιμών με WiMax την οποία γνωρίζω είναι αυτή του ΟΤΕ στο Όρος Άθως. Είναι ειρωνικό αλλά η Ελλάδα, παρά τη διείσδυση της κινητής τηλεφωνίας, παραμένει πανάκριβη σε ό,τι αφορά τη πρόσβαση στο διαδίκτυο μέσω κινητού (γύρω στα 30€/μηνιαίως για 5GB σε ταχύτητες 3.5G/HSDPA) αλλά έχει επιλεχθεί ως πιλότος του WiMax και δη χωρίς να ενημερωθεί κανείς;
Ας σημειωθεί πως η Vodafone έχει ήδη αγοράσει άδεια για το φάσμα του WiMax στην Ελλάδα από πέρυσι και υπάρχει περίπτωση το BBC απλώς να σφάλλει, μπερδεύωντας τη περίπτωση της χώρας μας με αυτή της Μάλτας. Αν κάποιος γνωρίζει περισσότερα ας αφήσει ένα σχόλιο.
Sure, AJAX, when viewed through the prism of the still world of HTML and CSS, can be beautifully dynamic. But, let’s face it, Google Earth — despite its resource-laden design and slow response on slower systems — is a much more natural, a friendlier way to view geographic data. With Microsoft trying hard to reclaim the (tech) lead on mapping (see Virtual Earth, WorldWide Telescope), it’s up to Google to stop the surge.
Enter the Google Earth API and browser plugin — software that opens up Google Earth for use within browsers and accessible by web developers. Sadly, it’s only available for Windows right now — I bet this will change soon.
Web 2.0 was “interface” level people trying to solve “infrastructure” level problems
While flawed in some of its comparisons, the article rings so painfully true and accurately depicts the lunacy of the post bubble renaissance of the web industry.
The Face of Hypocrisy.
Late last year, in an article about the need for interconnectedness of social networks and the ownership of user profile data, I wrote:
If Facebook can connect to another service with your account (and your permission), what’s stopping the creation of a MetaSocial Network. A network to which you provide the login details for all of the major social networks out there for which you already have accounts, it automatically logs in and accesses your profile information, including your friend list and incorporates everything in a single, beautiful environment.
Google went on and actually implemented this (and much more while at it) in its Friend Connect service. And then Facebook, prompty moved to ban the service from accessing its users’ profiles. The reason for doing so was that Google redistributes the data to third-party developers without the users’ consent. Google responded that it only redistributes data that the user has consented to sharing (with any particular site) and, in addition to this, the data is merely links to profiles and photos. Google goes as far as to replace Facebook usernames and numeric ids with its own and purges data every 30 minutes. This is much less than Facebook’s 24hour maximum for data retention by third-party developers, although — to my knowledge — the company has no way of enforcing this. It is thus somewhat ironic that Facebook is concerned with the privacy of its users, especially given its history of trying to exploit it in the most insidious manner (viz. Beacon) as well as its response to Google’s Friend Connect. Someone that wants to harvest data off Facebook merely has to create a trojan pointless application of the sort that adorns most profiles and then start harvesting. Facebook doesn’t seem to care about the privacy of its users. The reason it reacts to Google’s service and invokes privacy as a reason for doing so is because it sees Google as a threat. A threat that might one day showcase how closed, arrogant and — in retrospect — irrelevant it is as a platform. If anything the network has proven to be hypocritical and excessively arrogant, both when faced with criticism by its users and the industry as a whole.
Those using Firefox 3.0 may have noticed that by default when someone scales the content of a page, the images are resized too, a behaviour long-pioneered by Opera. Those using Firefox 3.0 on linux will be sorry to find out that upscaled images are not resampled using anything but what seems to be nearest neighbour (I haven’t checked the code): they are ugly, pixelated and definitely not pleasant to the eye.
This is well documented on the Mozilla Bugzilla repository and sadly it may be the case that it’s not fixed until Firefox 3.0 final is out. Which is a shame, as many people with higher resolution displays, especially high-resolution laptop displays that sometimes reach approximately 150dpi actually depend on the scaling functionality to be able to read stuff properly. Ironically GTK+ offers pretty decent image scaling functionality and hopefully it’s not that hard to make use of it in Firefox in the near future. Here’s an illustration of the problem. The picture on the left shows the original (unscaled) content of the ΜΠΛΟΟΓΚΛ hellenic blog search engine. The one in the middle shows the scaled version, as shown in Firefox 3.0 Beta 5 that shipped with Ubuntu 8.04. The one on the right shows a resampled version of the image using the (pretty computationally expensive) lanczos algorithm, which although not probable as a solution it’s quite close to the (realistically possible) bilinear resampling for upscaled images of this size.

You can follow the progress on this issue on the Mozilla Bug tracking page here.
At last, Linksys just upgraded their SPA (formely Sipura) 942/962 series phone firmware. Among many other bugfixes, the new firmware fixes a number of longstanding and extremely annoying SIP registration bugs (CSCsm28353, CSCsk69012) that afflicted dynamic IP ADSL users whose external (routable) IP address gets changed frequently and necessitated a relatively long process to make the phone behave properly. Kudos to Linksys for fixing this, albeit quite late.
A detailed case study of Magnatune
It was written by ORG’s Michael Holloway, who did an incredible job of synthesizing information from our web site, interviews with me, and my dozens of comments.



