Projects Update

<code>git clone https://github.com/Deltik/products-legacy.git</code>

<code>curl -L 'https://github.com/Deltik/products-legacy/raw/main/products.tar.xz' | tar -xJvf -</code>

<code>curl -L 'https://content.deltik.org/products/legacy/products.tar.xz' | tar -xJvf -</code>

• Ability to convert to Windows Live Messenger chat logs
• A slightly more readable incompatibility description box

• The Pidgin source converter malfunctioned and gave zeroed timestamps due to poor programming practices combined with Qt framework updates.
• The Windows Live Messenger default log path has been corrected.

• Download: https://sourceforge.net/projects/log2log/files/
• Project Site: http://log2log.sourceforge.net/

• Ability to convert from Digsby chat logs
• Ability to convert to Pidgin chat logs

• Update checker is now compatible with the SourceForge web server by sending a user agent.

• Download: https://sourceforge.net/projects/log2log/files/
• Project Site: http://log2log.sourceforge.net/

• 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"

• Most of the planned format converters have not been created yet.

1. 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.
2. 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++.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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++.

• Igor Cardoso — still sticking with the Log2Log project
• John — for helping us know what to work on next in the development of Log2Log

• 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.

• There are disadvantages? O_o

They had a script driving up the server load consistently for about 5 minutes to 2.00+

• 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.

• 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.

3.0.0 (2011/05/20)
  - 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: No JavaScript compatibility
  - 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

• MuSeSPinger
• MuSeSPinger v3.0.0 Demo
• Download MuSeSPinger
• Deltik Docs Article: MuSeSPinger