public inbox for gwml@vger.gnuweeb.org
 help / color / mirror / Atom feed
From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: Muhammad Rizki <kiizuha@gnuweeb.org>
Cc: Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>,
	GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>
Subject: Re: [PATCH v1 0/4] GNUWeebBot2 Fixes and New Updates
Date: Fri, 19 Dec 2025 05:16:09 +0700	[thread overview]
Message-ID: <20251218221609.GA108062-ammarfaizi2@gnuweeb.org> (raw)
In-Reply-To: <20251215182308.48766-1-kiizuha@gnuweeb.org>

On Tue, Dec 16, 2025 at 01:23:02AM +0700, Muhammad Rizki wrote:
> Hello, it's been a long time since my last contribution to GNUWeeb Community,
> so here are some fixes and new updates for GNUWeebBot2 that I've made.

Hello,

I halted the development of that project. I think maintaining a fast
moving Telegram bot library when I can't move fast is not productive.
So, instead of developing a Telegram bot library ourselves, we had
better use an external actively maintained library and contribute to
it. I recently contributed to this Telegram bot library:

  https://github.com/reo7sp/tgbot-cpp/pull/331

It's also the Telegram bot library I am actively using today. While it
may not fully cover the latest upstream Telegram Bot API methods and
structs, at least we have a good enough framework to keep up the
upstream. You may want to examine the header files here to see how
kept up it is with the upstream:

  https://github.com/reo7sp/tgbot-cpp/tree/master/include/tgbot/types

I think the current state of that library is adequate to create a
Telegram bot with rich features. So, my recommendation is: Let's use
that library and contribute to it.

Another good thing about using an external library is that, we have
more users, so we have more coverage. People report bugs that they find.
It helps us discover problems that we may not be aware yet.

Thanks,

-- 
Ammar Faizi


      parent reply	other threads:[~2025-12-18 22:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-15 18:23 [PATCH v1 0/4] GNUWeebBot2 Fixes and New Updates Muhammad Rizki
2025-12-15 18:23 ` [PATCH v1 1/4] .vscode: add some C/C++ extension settings Muhammad Rizki
2025-12-15 18:23 ` [PATCH v1 2/4] core:lib: fix memory leak and reduce threads Muhammad Rizki
2025-12-15 18:23 ` [PATCH v1 3/4] lib/tgapi: add new properties for type User Muhammad Rizki
2025-12-15 18:23 ` [PATCH v1 4/4] modules: create a `user` module Muhammad Rizki
2025-12-18 22:16 ` Ammar Faizi [this message]

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 \
    --in-reply-to=20251218221609.GA108062-ammarfaizi2@gnuweeb.org \
    --to=ammarfaizi2@gnuweeb.org \
    --cc=alviro.iskandar@gnuweeb.org \
    --cc=gwml@vger.gnuweeb.org \
    --cc=kiizuha@gnuweeb.org \
    /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