BPI inside

You may remember that about half a year ago I had some thoughts about how to change the photo hosting platform for this blog. Up to that day I used Flickr when I recognized that they had changed their licenses and external linking policy. The new conditions in the license and policy did not allow embedding of photos from external locations anymore. Since that time I've been using a workaround (by embedding Google Photo images via the legacy Picasa Web albums interface) for the images in my blog postings.

Well, it seems that Flickr/Yahoo has revised their decision again. I guess it has something to do with their tries to get back into mainstream again and is very probable connected to their incredible 1TB Flickr relaunch.

But not only do they allow external embedding again, they even reenabled that functionality at a much more accessible location than before. Via the "Share" symbol, which is available at any location within Flickr, you can immediately access the sharing/embedding menu for photos or albums on Flickr.

For me personally this makes the decision not easier. Back in November I began using Googles services for photo hosting which allows embedding but is not really straightforward as it requires the workaround I mentioned above (via the Picasaweb-interface) to retrieve the sharing HTML code. And that code wasn't 100% correct as it contained some invalid links which I had to fix manually.

I guess, I'll switch back to Flickr again for new albums in the future but continue to use Google Photos/Picasaweb for the ones which I created there. It's nice to see that there are still some companies out there who reconsider past decisions and revert them. Enabling integration of provided services at independend locations instead of locking in any data/files/information the users provide is in my opinion a key factor to make it possible for others to leverage the services to otherwise impossible solutions.

Posted by Kosi2801 on 5:34 PM tagged as Flickr, Google, Personal, Photography | Permalink

Quite a while ago I compiled a list of Skype chat commands from the ones available in the Skype help as well as from various sources all across the Internet. Later on I got curious and decided to inspect Skype a bit more in depth and I was able to retrieve another list of hidden or mysterious Skype commands from the application.

I have been asked a few times how I did that and I thought maybe it would also be interesting for some who didn't ask and compiled a short step-by-step guide how I extracted the list of commands from Skype which were (at that time) documented or known nowhere else. Maybe it's also interesting and applicable to inspect other applications but I'll concentrate on Skype in this posting. The process is pretty much the same for most other applications.

Tools

For the analysis of Skype there are only two tools needed:

• Process Explorer - the #1 tool for working with all running processes on your Windows machine. Part of the excellent Sysinternals Suite written by Mark Russinovich. No installation required.
• Notepad++ or any other texteditor of your choice which can handle really large textfiles and search efficiently in them.

Analysis Steps

For a short summary that's a rough overview how I inspected Skype: loaded up Skype normally, dumped it's memory image (or better: string extract) with Process Explorer and did a manual search for command-like strings in the dump. The detailled process is as follows:

1. start up Skype normally
2. start up Process Explorer, confirm first-time dialogs etc. until you see the process overview

   From Skype Memory Analysis

3. locate "Skype.exe" in the process list and double click it
4. switch to the "Strings" tab in the occouring process window (could take a few seconds)
5. select the "Memory" option on the left bottom of the window (could take again a few seconds to complete)

   From Skype Memory Analysis

6. save the strings dump to a textfile via the "Save" button on the right bottom of the window
7. load the resulting textfile in the text editor (Notepad++ in my case)
8. search for one of the already well known commands (e.g. "/help")

   From Skype Memory Analysis

Now you should be in a region of the file where several commands are visible. Looking for additional commands is merely a try&error of the strings around that location and observing possible effects. The same approach can be used for in-text replacements like smilies, flags or similar. From that on things get pretty inconvenient. Some of the commands or usable strings are clearly identifyable as such (like "/help") but not all of them are prepended with a "/". Examples for such are the flag-identifiers ( eg: (flag:uk) ) or the smilies. Looking for such strings in a file with more than 400k lines becomes pretty tedious after a while. But using some of the known strings as anchor points makes it a bit easier.

So, all in all that's how I approached the Skype app and found out about (up to that point) aparently unknown and undocumented commands, icons and shortcuts. Maybe I'll make a run again sometime and look if something as changed but for that there has to be a chunk of spare time available.

Posted by Kosi2801 on 10:31 AM tagged as Analysis, Development, Hack, ProcessExplorer, Skype, Sysinternals | Permalink | Comments (1)