1
0
Conversion script from various messaging formats to markdown.
Go to file
takunomi-build-bot 5d2dd33697
Some checks are pending
Run Python tests (through Pytest) / Test (push) Waiting to run
Verify Python project can be installed, loaded and have version checked / Test (push) Waiting to run
🤖 Repository layout updated to latest version
This commit was automatically generated by a script: https://gitfub.space/Jmaa/repo-manager
2024-10-31 22:38:57 +01:00
.gitea/workflows 🤖 Repository layout updated to latest version 2024-10-26 13:35:36 +02:00
libpurple_to_markdown Ruff 2024-10-31 22:38:22 +01:00
test Restructure by moving datastructures and libpurple parsing into own module 2024-10-31 19:00:07 +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-10-31 22:38:57 +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-10-31 22:38:57 +01:00

Markdown Message Conversion.

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

From the repository root:

python -m libpurple_to_markdown LOG_DIRECTORY --output OUTPUT_FOLDER

It was made specifically for import into Obsidian, so it might not suite your purposes, but it shouldn't be too difficult to adjust the formatting code.

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.