1
0
Conversion script from various messaging formats to markdown.
Go to file
takunomi-build-bot 8d1232d48d
All checks were successful
Package Python / Package (push) Successful in 25s
Run Python tests (through Pytest) / Test (push) Successful in 25s
Verify Python project can be installed, loaded and have version checked / Test (push) Successful in 22s
🤖 Bumped version to 0.1.7
This commit was automatically generated by a script: https://gitfub.space/Jmaa/repo-manager
2024-11-28 21:05:24 +01:00
.gitea/workflows 🤖 Repository layout updated to latest version 2024-11-16 18:39:05 +01:00
libpurple_to_markdown 🤖 Bumped version to 0.1.7 2024-11-28 21:05:24 +01:00
test Remove redundant whitespace on end of line (for an even weird edge case) 2024-11-04 22:52:21 +01:00
.gitignore Initial commit for crazy log conversion project 2024-10-26 00:48:59 +02:00
LICENSE 🤖 Repository layout updated to latest version 2024-10-26 13:35:36 +02:00
README.md 🤖 Repository layout updated to latest version 2024-11-28 21:03:50 +01:00
requirements.txt Requirements 2024-10-26 15:18:21 +02:00
ruff.toml 🤖 Repository layout updated to latest version 2024-10-31 22:38:57 +01:00
setup.py 🤖 Repository layout updated to latest version 2024-11-21 19:44:29 +01:00

Markdown Message Conversion

Test program/library

Conversion script from various messaging formats to markdown.

Supported input formats:

Motivation

Messaging applications are mostly good at sending real-time messages to other people, but they generally do not possess any useful archival features. Most messages are write-once read-once, and the apps where built for this use case. More and more through, I am attracted to the prospect of archival; of understanding who I am and who I were when I wrote those messages.

I recently discovered Obsidian and liked the prospect of cross-referencing my notes with my old chat logs. Libpurple uses HTML logs if you haven't configured it to something else (which I haden't).

I no longer use IRC or Pidgin as my entire friend group have switched to using Matrix.

Usage

There are two main import patterns:

  • One-off archival import: For when you have a large set of messages to import for a service that you don't use very much anymore.
  • Recurring import: For when you are still using the service, and want to import on a recurring basis.

This program will be default not overwrite existing files, as the user might have modified it.

Special consideration must be taking for recurring imports if you expect to be modifying the resulting files, for example if you are inserting links using Obsidian's unlinked mentions feature. You might want to use the --skip-this-period flag to avoid importing the current period until it has become the last period. That way you won't accidentally modify the log, because it has been finalized.

One-off

This is the recommended command for the one-off case:

python -m libpurple_to_markdown LOG_DIRECTORY --output OUTPUT_FOLDER

Recurring

This is the recommended command for the recurring import case:

python -m libpurple_to_markdown LOG_DIRECTORY --output OUTPUT_FOLDER --skip-this-period --period month

TODO

  • SyncTech: Decode MMS parts and reconstruct image attachments.

Dependencies

All requirements can be installed easily using:

pip install -r requirements.txt

Full list of requirements:

License

MIT License

Copyright (c) 2024 Jon Michael Aanes

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.