Forwarded from Jago
As of today, the owner is myself, @nysascape. I've assigned @RealAkito here to assist me with the project as one of our lead developers of Paperplane.
New handle for discussion: @tgpaperplane
New channel for Paperplane: @paperplanechannel
Development of the project is started again as of today. Enjoy your stay in these chats!
Source: https://github.com/RaphielGang/Telegram-UserBot/
New handle for discussion: @tgpaperplane
New channel for Paperplane: @paperplanechannel
Development of the project is started again as of today. Enjoy your stay in these chats!
Source: https://github.com/RaphielGang/Telegram-UserBot/
GitHub
GitHub - RaphielGang/Telegram-Paperplane: The Paperplane userbot project - a Telegram userbot helping to improve your Telegram…
The Paperplane userbot project - a Telegram userbot helping to improve your Telegram experience. https://t.me/tgpaperplane - RaphielGang/Telegram-Paperplane
Soon I'll be making some changes. Feel free to fork and pr wherever!
I'd like to make a quick announcement. Due to the likes of COVID 19, UK have now shut schools nation-wide which means that I'm going to be spending time at home with online lessons.
While this does mean I'm looking to spend more time to improve Paperplane, we all should be focusing on staying safe at the moment and spending time with those that you love, practising social distancing where possible.
Stay safe everyone. Thanks ❤️
- nysa
While this does mean I'm looking to spend more time to improve Paperplane, we all should be focusing on staying safe at the moment and spending time with those that you love, practising social distancing where possible.
Stay safe everyone. Thanks ❤️
- nysa
Hello everyone, this is @zakaryan2004. As nysa couldn't manage to continue the project because of some circumstances, a few days ago I have become the owner of Paperplane, and the development will see a great pace from now on.
I have a few things in mind, but one of the main things I put in forward of me is to fix all of the modules and make their basic functionality work and document Heroku support. I will work on fixing the smaller bugs after this, and you can expect new feature to come! Don't hesitate to report bugs or make suggestions!
Group, channel and repo stay the same, nothing is being changed from previous infrastructure.
Contributions are welcome, if you want to put your ounce to Paperplane, feel free to make a Pull Request on GitHub!
Here is the source code link as always: https://github.com/RaphielGang/Telegram-Paperplane/
I have a few things in mind, but one of the main things I put in forward of me is to fix all of the modules and make their basic functionality work and document Heroku support. I will work on fixing the smaller bugs after this, and you can expect new feature to come! Don't hesitate to report bugs or make suggestions!
Group, channel and repo stay the same, nothing is being changed from previous infrastructure.
Contributions are welcome, if you want to put your ounce to Paperplane, feel free to make a Pull Request on GitHub!
Here is the source code link as always: https://github.com/RaphielGang/Telegram-Paperplane/
GitHub
GitHub - RaphielGang/Telegram-Paperplane: The Paperplane userbot project - a Telegram userbot helping to improve your Telegram…
The Paperplane userbot project - a Telegram userbot helping to improve your Telegram experience. https://t.me/tgpaperplane - RaphielGang/Telegram-Paperplane
Hi again, it has been one month since my last announcement (the time when I became the owner of Paperplane), and I would like to make a changelog-like message, showing everything which has been changed so far, and maybe what I plan to do in the future.
So, here is everything which has been changed in Paperplane since April 15th:
* The clipping of -_- meme animation has been fixed (thanks to AvinashReddy3108)
* Filters can now also match words partially
* Fixed the .img module
* Use PyDrive2 instead of PyDrive to fix GDrive module
* Added support for Heroku updates
* Change the Dockerfile in staging to clone staging instead of master
* Fixed issues in the TTS module
* Better error handling, sending the error log to BOTLOG instead of the group the command is triggered in (thanks to RealAkito)
* Update the Magisk module to use new canary URLs, add canary/debug (thanks to yshalsager and RealAkito)
* Fixed an error in .setcity which partially broke it
* Add String Session support and Deploy to Heroku button (co-authored by DragonightFury)
* Fix a few critical vulnerabilities (thanks to penn5)
* Fixed a small bug in system_stats module (thanks to adekmaulana)
* Fix .device and .codename commands (co-authored by yshalsager)
* Nuke auto-linter and auto-merger which merged staging to master every week (from now these are going to be done manually)
* Fixed a small bug in .mirror module (thanks to zainarbani)
* Organize help page by categorizing modules in categories
* Error handler will now log errors in the console too
* Add WolframAlpha module (thanks to zainarbani)
Moving past the past changes, let's talk about the future ones. We now have a TO-DO page on GitHub Issues, where we will write some of the important issues or suggestions. And also, now it's recommended to report issues you find in the GitHub Issues page to make it more visible and easier to track. So, feel free to report any bugs or suggestions you have!
As one of the main "drawbacks" of using userbots such as Paperplane is the fact that some groups don't allow it as it can cause unnecessary spam, one of the most important features planned is excluding Paperplane from a group, thus making Paperplane ignore:
1) Any messages (incoming or outgoing, not allowing you to use any command in that group). This will make Paperplane pretend it's not there at all.
2) Only incoming messages (allowing you to use commands). This will make Paperplane not respond anything not triggered by you (such as AFK, filters, notes, antispam and so on).
You can find more of the features planned for in the future in the TO-DO page.
Messages like this will come every month, so make sure you are following the channel! If you have any questions, don't forget to join our support group.
As always, thanks for using Paperplane!
- @zakaryan2004
So, here is everything which has been changed in Paperplane since April 15th:
* The clipping of -_- meme animation has been fixed (thanks to AvinashReddy3108)
* Filters can now also match words partially
* Fixed the .img module
* Use PyDrive2 instead of PyDrive to fix GDrive module
* Added support for Heroku updates
* Change the Dockerfile in staging to clone staging instead of master
* Fixed issues in the TTS module
* Better error handling, sending the error log to BOTLOG instead of the group the command is triggered in (thanks to RealAkito)
* Update the Magisk module to use new canary URLs, add canary/debug (thanks to yshalsager and RealAkito)
* Fixed an error in .setcity which partially broke it
* Add String Session support and Deploy to Heroku button (co-authored by DragonightFury)
* Fix a few critical vulnerabilities (thanks to penn5)
* Fixed a small bug in system_stats module (thanks to adekmaulana)
* Fix .device and .codename commands (co-authored by yshalsager)
* Nuke auto-linter and auto-merger which merged staging to master every week (from now these are going to be done manually)
* Fixed a small bug in .mirror module (thanks to zainarbani)
* Organize help page by categorizing modules in categories
* Error handler will now log errors in the console too
* Add WolframAlpha module (thanks to zainarbani)
Moving past the past changes, let's talk about the future ones. We now have a TO-DO page on GitHub Issues, where we will write some of the important issues or suggestions. And also, now it's recommended to report issues you find in the GitHub Issues page to make it more visible and easier to track. So, feel free to report any bugs or suggestions you have!
As one of the main "drawbacks" of using userbots such as Paperplane is the fact that some groups don't allow it as it can cause unnecessary spam, one of the most important features planned is excluding Paperplane from a group, thus making Paperplane ignore:
1) Any messages (incoming or outgoing, not allowing you to use any command in that group). This will make Paperplane pretend it's not there at all.
2) Only incoming messages (allowing you to use commands). This will make Paperplane not respond anything not triggered by you (such as AFK, filters, notes, antispam and so on).
You can find more of the features planned for in the future in the TO-DO page.
Messages like this will come every month, so make sure you are following the channel! If you have any questions, don't forget to join our support group.
As always, thanks for using Paperplane!
- @zakaryan2004
GitHub
[TO-DO] Your general TO-DO list · Issue #231 · RaphielGang/Telegram-Paperplane
Project's Current TO-DO BETTER WIKI A new Help implementation Integrate Kantek with Paperplane Not planned Make the mute command check if the user can delete messages in a group before saying t...
Paperplane Exclude is now publicly available in the staging branch, where it will be tested and improved until the full rollout! You can find out more about this feature in the previous message in the channel, the GitHub commit and the Help section.
Commit: https://github.com/RaphielGang/Telegram-Paperplane/commit/774d07b6089dcc0c40eb8baf917f4ea264f4d05b
You are strongly encouraged to test this feature and give suggestions and bug reports. Suggestions are welcome.
Paperplane Exclude is still in early stage, and some features MAY NOT WORK PROPERLY, so don't expect it to be bug-free. We are not responsible for anything which happens during beta testing this module.
P.S. Remember to use BOTLOG, so error messages aren't sent to groups. This will make sure you don't get warned/muted/banned when testing this feature or using Paperplane normally, also you will be able to see all errors in one place.
If you have any questions, don't forget to join the support group: @tgpaperplane
To stay up-to-date on announcements and stuff, make sure to follow the channel: @paperplanechannel
Thanks for staying with Paperplane.
- @zakaryan2004
Commit: https://github.com/RaphielGang/Telegram-Paperplane/commit/774d07b6089dcc0c40eb8baf917f4ea264f4d05b
You are strongly encouraged to test this feature and give suggestions and bug reports. Suggestions are welcome.
Paperplane Exclude is still in early stage, and some features MAY NOT WORK PROPERLY, so don't expect it to be bug-free. We are not responsible for anything which happens during beta testing this module.
P.S. Remember to use BOTLOG, so error messages aren't sent to groups. This will make sure you don't get warned/muted/banned when testing this feature or using Paperplane normally, also you will be able to see all errors in one place.
If you have any questions, don't forget to join the support group: @tgpaperplane
To stay up-to-date on announcements and stuff, make sure to follow the channel: @paperplanechannel
Thanks for staying with Paperplane.
- @zakaryan2004
GitHub
treewide: grp_exclude: Introduce Paperplane Exclude [BETA] · RaphielGang/Telegram-Paperplane@774d07b
Paperplane Exclude is a Paperplane module which allows excluding chats from the Paperplane event handler. More information can be found in the Help section and comments.
This feature is still BETA,...
This feature is still BETA,...
Do you use the Direct Links Generator module?
Anonymous Poll
71%
Yes, I always use it.
11%
Sometimes, removing it doesn't bother me.
18%
No, have never used it, don't see any reason for it.
Strongly recommended to give feedback about the option you chose in our group, @tgpaperplane.
Do you/Would you use the Spotify or LastFM modules?
Anonymous Poll
41%
Only the Spotify module
4%
Only the LastFM module
18%
Both
16%
None
20%
I don't use Paperplane