Shad API Framework for Python
Homepage
•
Documentation
•
Releases
Elegant, modern and asynchronous Shad API framework in Python for users and bots
Accounts
WebSocket Handler:
from shadapi import Client
app = Client('my_account_auth')
@app.handler
async def my_bot(bot, message):
await message.reply('``Hello`` __from__ **Shad Api**!')
Messages Update Handler:
from shadapi import Client
app = Client('my_account_auth')
@app.updateHandler
async def my_bot(bot, message):
await message.reply('``Hello`` __from__ **Shad Api**!')
OR
from shadapi import Client
app = Client('my_account_auth')
update_delay = 5 # in seconds
@app.updateHandler(update_delay)
async def my_bot(bot, message):
await message.reply('``Hello`` __from__ **Shad Api**!')
Another example:
from shadapi import Client
app = Client("my_account_auth")
async def my_bot(bot):
await bot.sendText('object_guid', '``Hello`` __from__ **Shad Api**!')
app.run(my_bot)
from shadapi import Bot
app = Bot('token')
async def my_bot(bot):
me = await bot.getMe()
print(me)
app.run(my_bot)
OR
from shadapi import Bot
app = Bot('token')
async def my_bot(bot):
me = await bot.sendMessage('chat_id', 'text')
print(me)
app.run(my_bot)
Shad-Api is a modern, elegant and asynchronous framework. It enables you to easily interact with the main Shad API through a user account (custom client) or a bot identity (bot API alternative) using Python.
pip3 install shadapi
(Note: this process has to be done in a pc)
when using this library for fethcing messages from a chat, the library will start a WebSocket channel with the server, and because of the present lag in the server, some of the messages will not be sent by the server and wont be processed by the client (this is not an issue with the library, it's from the server! this problem also do exist in the Android and Web versions of Shad) we can kindof fix this problem by loading every last message every once in a while to ensure that the client have recived every message, but this would make the bot use more internet (around 277MB per day for maden requests every 2 seconds). the problem with this bypass is that the server would consider that as "request spam" (aka DDOS) and will refuse to response to most of the requests, and this would make the bot pretty much slower! i did implement this functionality in the library and with the addition of "request delay", but until shad devs fix the main issue inside the server or until i find an actuall bypass solution, this are the only ways to handle messages in this library.
Request method | advantages | disadvantage |
---|---|---|
WebSocket syncing | instant trigger | ignores most messages |
getChatUpdates request | triggers on every message | slow trigger |
he did an awesome job at making a rubika library which helped alot to make this project! https://github.com/shayanheidari01/rubika