Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

copy_message method and forward_messages with drop_author=True, are the same? #113

Open
3 tasks done
Urkov opened this issue Feb 3, 2025 · 1 comment
Open
3 tasks done

Comments

@Urkov
Copy link

Urkov commented Feb 3, 2025

Checklist

  • I am sure the error is coming from Pyrofork's code and not elsewhere
  • I have searched in the issue tracker for similar bug reports, including closed ones
  • I ran pip3 install -U git+https://github.com/Mayuri-Chan/pyrofork and reproduced the issue using the latest development version

Description

I try to follow the steps to Sctackoverflow but I can't write a post with pyrofork tag because is not popular :-( so that is why I put it with pyrogram tag and I am putting here also:

I am using Pyrofork to send messages and I would like to know the differences between copy_message and forward_messages with parameter drop_author=True. My main usage is to backup so if the origin group is deleted or banned which one is better to not track from origin to backup group?

If in this case are the same which needs less resources or clock time?

I don't find anyone who is capable to explain the differences.

Steps to reproduce

  1. send message with forward_messages
  2. send message with copy_message
  3. no difference noted

Code example

Logs

@yasirarism
Copy link
Collaborator

Yeah almost same, forward message just invoke ForwardMessages raw method and different with copy message that invoke different method. And forward message doesn't have parameter in copy_message, like has_spoiler.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants