Bot API was updated to version 6.4
Forums
• Bots can now open, close, edit and toggle the visibility of the General Topic.
• Added support for new service messages, like ForumTopicEdited, GeneralForumTopicHidden and more.
• The method sendChatAction can now send actions to any thread or topic via the message_thread_id parameter.
Spoilers
• Added spoiler detection via the new has_media_spoiler field in the Message class.
• Bots can send media covered by a spoiler animation via the has_spoiler field in sendPhoto, sendVideo and sendAnimation.
Web Apps
• Added a native QR scanner popup, controllable via showScanQrPopup and closeScanQrPopup.
• Web Apps launched from the attachment menu can request clipboard text via readTextFromClipboard.
• Added a platform field, showing which platform the web app is being used on.
General
• Added the is_persistent field, to keep ReplyKeyboards open by default.
See the full changelog for details on the official website.
#update#BotAPI
https://t.me/+VMLgtEPNL49jZmNh
https://pypi.python.org/pypi/oauthlib
A generic, spec-compliant, thorough implementation of the #OAuth request-signing logic for python
OAuth often seems complicated and difficult-to-implement. There are several prominent libraries for handling OAuth requests, but they all suffer from one or both of the following:
They predate the OAuth 1.0 spec, AKA RFC 5849.
They predate the OAuth 2.0 spec, AKA RFC 6749.
They assume the usage of a specific HTTP request library.
OAuthLib is a generic utility which implements the logic of OAuth without assuming a specific HTTP request object or web framework. Use it to graft OAuth client support onto your favorite HTTP library, or provide support onto your favourite web framework. If you’re a maintainer of such a library, write a thin veneer on top of OAuthLib and get OAuth support for very little effort.
https://aaronparecki.com/2012/07/29/2/oauth2-simplified#others
OAuth 2 Simplified
Sun, Jul 29, 2012 9:30am -07:00
Many services such as #Facebook, #Github, and #Google have already deployed OAuth 2 servers, and deployed implementations win.
The #OAuth 2 spec itself leaves many decisions up to the implementor. Instead of describing all possible decisions that need to be made to successfully implement OAuth 2, this post makes decisions that are appropriate for most implementations.
This post is an attempt to describe OAuth 2 in a simplified format to help developers and service providers implement the protocol.