GNU/Weeb Mailing List <[email protected]>
 help / color / mirror / Atom feed
From: Muhammad Rizki <[email protected]>
To: Ammar Faizi <[email protected]>
Cc: Muhammad Rizki <[email protected]>,
	Alviro Iskandar Setiawan <[email protected]>,
	GNU/Weeb Mailing List <[email protected]>
Subject: [PATCH v1 0/7] Fix some bugs and add some features
Date: Tue, 18 Oct 2022 15:16:28 +0700	[thread overview]
Message-ID: <[email protected]> (raw)

Hi sir,

This series is to fix some bugs, improve some codes and add some new
features. These bugs should have been fixed now, and the email file
attachments should have been removed after all attachments have been
sent.

Known bugs:
1. Email payload extraction result become unicode if the email payload
   contain non-UTF8 characters like chinese, japanese, and similar
   like that.
2. remove_patch() doesn't remove all file attachments properly.

Improvements:
1. Improve fix_utf8_char() to make it stable for both Discord and
   Telegram bot.
2. Improve remove_patch() to make it all file attachments removed
   after sending them.
3. Fix `/lore {raw atom url}` to add a "telegram" onto the
   create_template() platform parameter.

New features:
1. Add send_text_mail_interaction() for the `/lore {raw atom url}` slash
   command.
2. Add send_patch_mail_interaction() for the `/lore {raw atom url}`
   slash command.
3. Add `/lore {raw atom url}` slash command.

There are 7 patches in this series:
- Patch 1 is to add send_text_mail_interaction()
- Patch 2 is to add send_patch_mail_interaction()
- Patch 3 is to add `/lore` slash command
- Patch 4 is to improve fix_utf8_char() code
- Patch 5 is to improve remove_patch() code to make it more stable
- Patch 6 is to add manage_payload() for manage email payload extraction
- Patch 7 is to fix the Telegram `/lore` command

How to use:
1. Execute the db.sql file in the daemon directory,
2. Setup .env file, the example is there with suffix .example, this
   file name must remove the suffix name .example,
3. Set up the config.py in each bot directory, such as dscord and
   telegram. The example is there with suffix .example & the file name
   must remove suffix name .example,
4. Run `pip3 install -r requirements.txt` in each bot directory,
5. STORAGE_DIR env value must `storage` to make it work fine,
6. Run the bot by `python3 dc.py` or `python3 tg.py`.

Both tested. But, I want to make sure if it's already fixed and stable.
So, don't forget to test it too, thanks.

Muhammad Rizki (7):
  discord: Add send_text_mail_interaction()
  discord: Add send_patch_mail_interaction()
  discord: Add get lore mail slash command
  atom: Improve fix_utf8_char()
  atom: Improve remove_patch()
  atom: add manage_payload()
  telegram: Fix get lore command

 daemon/atom/utils.py                          | 31 +++++++++++----
 daemon/dscord/gnuweeb/client.py               | 23 +++++++++++
 .../plugins/slash_commands/__init__.py        |  2 +
 .../plugins/slash_commands/get_lore_mail.py   | 39 +++++++++++++++++++
 daemon/dscord/mailer/listener.py              |  4 +-
 daemon/telegram/mailer/listener.py            |  3 +-
 .../packages/plugins/commands/scrape.py       |  5 +--
 7 files changed, 92 insertions(+), 15 deletions(-)
 create mode 100644 daemon/dscord/gnuweeb/plugins/slash_commands/get_lore_mail.py


base-commit: d9b20dab81202b93f48d5365ad680796e5839d80
--
Muhammad Rizki

             reply	other threads:[~2022-10-18  8:17 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18  8:16 Muhammad Rizki [this message]
2022-10-18  8:16 ` [PATCH v1 1/7] discord: Add send_text_mail_interaction() Muhammad Rizki
2022-10-18  8:16 ` [PATCH v1 2/7] discord: Add send_patch_mail_interaction() Muhammad Rizki
2022-10-18  8:16 ` [PATCH v1 3/7] discord: Add get lore mail slash command Muhammad Rizki
2022-10-18  8:16 ` [PATCH v1 4/7] atom: Improve fix_utf8_char() Muhammad Rizki
2022-10-19 16:59   ` Ammar Faizi
2022-10-19 17:23     ` Muhammad Rizki
2022-10-19 17:27       ` Ammar Faizi
2022-10-19 17:35         ` Muhammad Rizki
2022-10-19 17:42           ` Ammar Faizi
2022-10-19 17:46             ` Ammar Faizi
2022-10-19 17:51             ` Muhammad Rizki
2022-10-19 17:53               ` Ammar Faizi
2022-10-19 17:55                 ` Muhammad Rizki
2022-10-19 18:11                   ` Ammar Faizi
2022-10-19 22:34                     ` Alviro Iskandar Setiawan
2022-10-20  4:26                       ` Muhammad Rizki
2022-10-20  5:02                         ` Ammar Faizi
2022-10-20  5:06                           ` Muhammad Rizki
2022-10-20  5:10                             ` Ammar Faizi
2022-10-20  5:10                               ` Muhammad Rizki
2022-10-20  5:16                                 ` Ammar Faizi
2022-10-19 18:04                 ` Muhammad Rizki
2022-10-19 18:14                   ` Ammar Faizi
2022-10-19 22:44   ` Alviro Iskandar Setiawan
2022-10-20  4:24     ` Muhammad Rizki
2022-10-21 11:31       ` Ammar Faizi
2022-10-18  8:16 ` [PATCH v1 5/7] atom: Improve remove_patch() Muhammad Rizki
2022-10-18  8:16 ` [PATCH v1 6/7] atom: add manage_payload() Muhammad Rizki
2022-10-19 17:04   ` Ammar Faizi
2022-10-19 17:23     ` Muhammad Rizki
2022-10-19 17:28       ` Ammar Faizi
2022-10-21  7:04       ` Ammar Faizi
2022-10-21  7:37         ` Muhammad Rizki
2022-10-21  7:40           ` Ammar Faizi
2022-10-21  8:22             ` Muhammad Rizki
2022-10-21  8:33               ` Ammar Faizi
2022-10-21  9:58                 ` Muhammad Rizki
2022-10-21 10:47                 ` Muhammad Rizki
2022-10-21 10:53                   ` Ammar Faizi
2022-10-21 10:54                     ` Muhammad Rizki
2022-10-18  8:16 ` [PATCH v1 7/7] telegram: Fix get lore command Muhammad Rizki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox