In the past, Deltik's products site, products.deltik.org, provided demos of the products published by Deltik from 2008 to 2011. Some of these products have serious security or performance flaws that made them unsuitable for demoing on Deltik.
As a result, the old products, now collectively called the "Legacy Deltik Products", have been taken off of the demo site and published as an unsupported archive.
The Legacy Deltik Products can be copied to any web server running PHP 5, and they should run roughly as they did on Deltik. Note that some paths were hard-coded and may break on your web server if you aren’t pretending to use the virtual host products.deltik.org.
Currently, https://products.deltik.org/ just contains a static page explaining what happened to the Legacy Deltik Products. If I choose to make something of the subdomain, I'll replace it with whatever succeeds the Legacy Deltik Products.
Problems with the Demos
The demos ran on the same unprivileged user as the main Deltik website, which means that compromising one of the demos would allow an attacker to take control of Deltik. I provide an example of a partial exploit in the extended version of this news post. (I figured that it would be pointless to demonstrate a full exploit, since the demos are no longer running here.)
It was also possible to do some denial of service attacks and proxy some attacks through this server. I present a high-level overview of some attack examples in the extended version of this news post.
Windows Live Messenger was discontinued a few years ago, and its usage is disabled by default, but there exists a significant community that wants to keep Windows Live Messenger alive. At the time of writing, people can use Messenger Reviver to continue using Windows Live Messenger.
Though a new version of Log2Log v1.x has been released, it is running on limited support. New format converters are being created only on demand.
Tuesday 17 March 2015 - 19:46:01
Thank you Steve! Steve contacted me requesting a converter from his 2200 Digsby logs with AIM, Google Talk, MSN, and Yahoo!, and I delivered. Though a new version of Log2Log v1.x has been released, it is running on limited support. New format converters are being created only on demand.
Saturday 25 October 2014 - 23:27:40
Whaaa...? Google has acquired Meebo, so Meebo Messenger is closing down. On 23 June 2012, Deltik pushed out an update, Log2Log v1.0.1—the last in the v1.x branch. Log2Log v1.x has succeeded in it's original goal to convert Meebo chat logs, but due to very poor programming practices, Log2Log v1.x can no longer be supported.
The Log2Log v1.x branch has been deprecated. This is the final release of Log2Log v1.x (v1.0.1) as of 23 June 2012. You may ask for a custom-built release; Deltik will help you support new format converters if you ask.
What Went Wrong
Unfortunately, the only active developer on the Log2Log team (Deltik) is a really bad computer programmer, and he ruined the v1.x branch. The program is:
ugly (poor coding practices),
inflexible (no foreign language support),
inextensible (no plugin support),
bulky (unoptimized), and
leaky (no memory management).
A Log2Log v2.x branch is planned, but there are not enough human resources to make the project possible.
Version 2 shall:
improve memory management drastically,
take advantage of multiple threads (GUI, reading source data, converting to destination format, saving converted data),
have multilingual support, and
have format converters in a modular plug-in design.
I've talked about Loguntu before...
The Loguntu project might also be started along with Log2Log v2.x. Loguntu is planned to be the ultimate digital life interface for all personal data. It looks really awesome on paper, but guess what? Nobody cares.
Nobody even noticed that Deltik turned 4 years old on 31 March 2012... and the post from Deltik's 3rd birthday is not many posts away from this one... :(
Supporting Loguntu and Log2Log v2.x
If you're interested in the Loguntu project or seeing the Log2Log project go further, just let us know at http://loguntu.com/. (The link works as of 23 June 2012. I'll try to keep it up for a while.)UPDATE 04 July 2012: I bought the domain name LOGUNTU.COM, mm-kay? :P
Monday 25 June 2012 - 11:59:48
We're Still Here Deltik's top priority project, Log2Log, is still very active. We're working on it as hard as we can and will continue to do so until it's production-ready.
What's Taking So Long? Don't believe that we're working hard on it? See for yourself!
Creating a chat log converter is by no means easy. Me? I want Log2Log to be released as soon as possible without sacrificing the originally intended enterprise-grade quality. In order to do that, I have to learn C++ and the Qt framework on-the-fly while programming Log2Log.
Log2Log was intended to be released at the end of August 2011. The development team has underestimated how much work it would take to create it, but don't let that get you down. I really, really, really want Log2Log ready for people by the end of this month, September 2011.
What Works Surely we have made some progress in the several weeks of persistent development. This is the rundown of what works in Log2Log as of 10 September 2011:
Fully capable of reading files from a directory, feeding them through the format converters, and saving the converted files
Interface shows what data may be lost in the conversion process (formats don't store the same data)
Feature to "Check for Updates"
But there are a plethora of things that don't work:
Most of the planned format converters have not been created yet.
Detailed Priorities As of 08 September 2011, here are the priorities for development of Log2Log format converters:
Pidgin HTML -- Log2Log was originally created on 01 January 2011 with this format in mind. Pidgin HTML is complicated, and if I can create a good format converter for it, the others can easily fall in place.
Meebo (download) -- This was the reason why I wanted to create Log2Log. The format would be very easy to convert to and from, but there is a major problem to solve: The chat logs must be downloaded from a remote server. The code for doing this already exists, but originally, I had made it in a different programming language, PHP. It's now a matter of porting it to the language that Log2Log is now programmed in, C++.
Log2Log JSON (standardized export) -- For advanced purposes, I intend to create this format converter. Theoretically, this should take only minutes to create because it directly exports what Log2Log already does in the background.
Trillian -- Trillian stores its chat logs in XML format. Pidgin HTML is also like XML, so with that established foundation, I should have no problem creating a format converter to and from Trillian.
Windows Live Messenger -- By input from an eagerly waiting person, I'll create the Windows Live Messenger format converter. I looked at the chat log format, which was XML as well. Since Pidgin HTML will have been completed by the time I start working on this format converter, it should be very easy to read this format.
AIM -- Also by request, I intend AIM to be the sixth format converter I make. AIM chat logs are in HTML, and they resemble Meebo chat logs, but they're somewhat more detailed. It seems rather easy to create this format converter as well.
Skype -- Personally, I also want a Skype format converter. There is a major frustration, though. Skype thought that it would be funny to create their own eccentric chat log format. The format makes absolutely no logical sense at all, but all the data exists. In order to read it, I have to drop down to a very primitive level and scan the binary data. I started work on it in PHP, but once again, I have to port it to C++ because Log2Log is now written in C++.
Loguntu Loguntu has been envisioned, and some planning has been done. As for a server to host Loguntu on, we are trying to secure one by 04 October 2011.
Igor Cardoso — still sticking with the Log2Log project
John — for helping us know what to work on next in the development of Log2Log
Sunday 11 September 2011 - 15:50:58
Deltik does not know what to put in the center this time.
The Problem Log2Log is programmed in PHP, a language that is not optimized for Log2Log's purpose. PHP isn't designed to handle files, especially not large and plentiful ones.
The Solution In the end, the best solution is to port Log2Log to a multiplatform desktop software.
safer — As desktop software, your sensitive data such as chat logs will no longer need to be sent insecurely over the Internet. Your data sticks with you, and Internet access is only needed for Log2Log services such as MeeboConnect or Loguntu.
faster — Information doesn't need to be sent through the Internet to be processed by PHP. Instead, it'll all be done on your computer.
more reliable — No more relying on an online service, which could go down at any time. With Log2Log as desktop software, it'll be ready when you are.
convenient — Instead of going to a webpage, Log2Log would conveniently be a desktop application.
accessible — Log2Log would be right there on your computer, ready for you at all times.
Huh? What's MuSeSPinger? MuSeSPinger stands for Multiple Server Status Pinger. You can check websites to see if they are online or offline by the masses.?
Why We Made MuSeSPinger Wa-a-ay back in 2008, Deltik was hosted on a webhost called IsMyWebsite. IsMyWebsite was a unique webhost in that it had 16 servers called nodes. The nodes hosted different websites. We created a tool called IsMyWebsite Node Status Checker (IMWNSC), which was a hard-coded system that checked the status of all the nodes.
Over time, IMWNSC evolved from its narrow purpose into MuSeSPinger. MuSeSPinger was then improved and expanded.
The First of Its Kind You may think that we have reinvented the wheel because there are plenty of other services that check to see whether a website is online like Down For Everyone Or Just Me? and CheckSite.us. MuSeSPinger is the first and only service that can:
check multiple URLs at the same time,
render an image that shows the status of multiple URLs, and
use a mirror network to check multiple URLs.
In addition to those unique core features, MuSeSPinger has:
a streamlined interface,
its source code available to anyone,
three different methods of checking URLs,
a user-friendly administration control panel, and
almost three years of dedicated support from Deltik.
What's New? See the changelog for yourself! Or if you're too lazy:
- NEW: Completely rewritten
- NEW: Redesigned interface
- NEW: cURL and file_get_contents for server status checking
- NEW: MuSeSPinger network for worldwide server status checking
- NEW: Option to render without the network: "Work Locally"
- NEW: Status icons for "online with problems" and "status unavailable"
- NEW: "Report Problem" link
- NEW: Administration control center for modifying configuration
- NEW: Fetch MuSeSPinger news from Deltik
- MOD: URL input uses line breaks instead of spaces.
- MOD: Remade status icons
- MOD: Foreign language support removed
- MOD: Automatic update system removed
- MOD: 'update' directory re-purposed to MuSeSPinger news
- MOD: Implemented GNU GPL License
... an online service that converts uploaded chat logs to another format and returns the new format to the user.
Before You Even Think About Using It You probably can't, at least not as of this post, 21 March 2011. Log2Log is on version 0.0.1a1, which is a very early development release. There are bound to be problems and bugs everywhere. We have acknowledged many of them and would like to fix them, but we're quite excited to get the first release of Log2Log out to you.
Why We Made Log2Log Alright, everybody! Storytime!
I, Deltik, love to use Meebo as my mobile Internet messenger. Meebo isn't "good", in my opinion, but one thing that made me choose Meebo over other services was that it has the ability to store chat logs. Now, don't argue "But IM+ saves chat logs too!". Firstly, back then, IM+ didn't save chat logs. Secondly, Meebo didn't cost me a penny. Anyway, I used Meebo often.
Over time, I became increasingly concerned that Meebo did not have a feature to download chat logs. As a personal data hog, I urgently need to have my chat logs with me where I can protect them from harm. Finally, one day, 21 November 2010 at 09:52 PM, I contacted Meebo support to request a feature that had been requested plenty of times before—the ability to download Meebo chat logs. Take a look at my conversation with Meebo Support.
One day, 01 January 2011, I reached my frustration threshold and founded the Log2Log project. (It was officially named on 02 January 2011 at 07:50 PM, a candidate among "AdapChat", "Online Chat Log Converter", and "Log2Log".)
After over two and a half months of work, I finally reverse-engineered Meebo and created a fully automated system that can download all Meebo chat logs.
That's not all, folks. I thought that since I was going to convert Meebo chat logs to the format of my current IM client, Pidgin, I might as well expand Log2Log to a full online chat log conversion service.
In a nutshell, there was a primary reason and a secondary reason for making Log2Log: