HN user

unbehagen

72 karma
Posts4
Comments9
View on HN

I loved XBMC and still use Kodi to this day. Back then, I even proposed and POCed what's now a part of their Add-On system, essentially a fuse-like virtual file system forwarded to Python. Before that, each Add-On had to bring its own UI. This was basically my first OSS contribution and the community was really supportive and welcoming.

If it is a chrome extension and is installed via the Chrome Web Store, it can be updated silently in the background if I'm not mistaken. So in theory, wouldn't it be possible to serve Google with a NSL and force them to silently push a modified update to a targeted user that reveals the private key?

Here's the technical background: ClickSend consists of an Android App and a Java server. Both register with a Google App Engine backend. If you send a file to the Android App, the Java server opens an HTTP server, generates a random URL for the file and sends this as a push notification (GCM) to your Android device, along with all IP adresses of the server. The client is triggered by the notification and tries to reach the server on all IP adresses and opens the URL. This allows for direct streaming of multimedia content (player App needed) or downloading. The data never passes through our servers, so it only works if server and client are connected to the same network. We are currently preparing to launch this so all feedback is appreciated.

Well, this is not surprising. If you put less content directly on the first page, users have to click on links in order to view the content that is directly accessible in the desktop version, which generates more page views.