PWRTelegram API channel
16 March 2020 12:11
I'm also announcing some updates for the MadelineProto social channels.
- Introducing separate OT chat groups, to allow chatting about tech, politics and memes.
- Introducing a new international MadelineProto support group, for MadelineProto help and support.
- Finally introducing the official MadelineProto meme channel, full of only the dankest based memes!
- Introducing an official discussion group for AMPHP, the async, high-performance parallelized PHP library!
Also, finally introducing an official farsi MadelineProto channel: @.
This channel will post farsi translations of the posts sent on the main channel, along with MadelineProto sources, AMPHP tips and much more!
Also, check out the official arabic MadelineProto channel: @
Читать полностью…
PWRTelegram API channel
01 January 2020 00:00
I wish you all a very happy new year!
❤️❤️❤️
Читать полностью…
PWRTelegram API channel
29 December 2019 21:36
MadelineProto was updated to v5!
Introducing upload by URL, file renaming, parallelized downloads and uploads!
You can now use MadelineProto to rename Telegram files or upload them by URL: all uploads and downloads will be made 100% in parallel, 20 chunks at a time for maximum speed (value tweakable in the settings).
For more info, see the new file documentation.
Also introducing:
- Strictly typed, camelCase public API, now all methods can also be called in camelCase, with PHP type hinting for most parameters and return values.
- Full PHPDOC documentation for all the public API, for perfect documentation in your favorite IDE :)
- Several internal bugfixes, refactoring and general performance and stability improvements.
- Improved tests, to avoid backwards compatiblity issues with previous sessions when pushing.
- Clean composer dependencies, now you just have to require danog/madelineproto ^5.0 and nothing else in your composer.json!
Breaking changes:
- NONE :D; you don't have to change your code!
Читать полностью…
PWRTelegram API channel
23 December 2019 18:41
Finally, feel free to take a look at my submission to the TON contest: https://github.com/danog/toncontest
The repository contains well-documented code for multiple TON smart contracts, a testing suite based on the official TON validator, and a build toolchain for TON.
Читать полностью…
PWRTelegram API channel
23 December 2019 18:41
Next, I am proud to announce support for the TON protocol in MadelineProto.
MadelineProto is now capable of integrating with the Telegram TON blockchain, thanks to a fully native implementation of ADNL and the lite-client protocol.
It allows async interaction with liteservers in the same manner as the official lite-client, only with way more abstractions and ease of use.
Читать полностью…
PWRTelegram API channel
23 December 2019 18:41
I am extremely proud to announce the release of some projects I've been working on for the last three months, in the context of the Telegram Contests.
Читать полностью…
PWRTelegram API channel
19 June 2019 17:40
Internal API improvements:
- I created a unique, reliable, fast and extremely simple update handling system based on MadelineProto's loop API, not present in any other MTProto client, not even tdlib.
- Brand new async Stream connection stack
- Unique async message handler stack
- Abstract TLCallback API
- File reference database
- DNS over HTTPS
With MadelineProto 4.0, each update is handled in parallel using a separate thread, and everything is done in parallel (even on restricted webhosts, perfect for creating file downloader bots!).
To learn more about parallel processing with async, see the following tutorials:
- Async basics
- Async HTTP (file_get_contents)
- Async helper functions (p. 1, 2)
- Async forking
- Async background loops
- Async libraries by AMPHP
I am really happy with how MadelineProto 4.0 turned out.
I had an absolute blast working on this update, and implementing async really opened a whole sea of possible innovations and features I can implement in MadelineProto now.
(this is just a TL;DR of the full changelog, see the original posts for the full feature list)
Читать полностью…
PWRTelegram API channel
05 June 2019 23:22
About this project: PWRTelegram might come back very soon with PWRTelegram 2.0 (now asynchronous!), thanks to the help of a friend ❤️❤️❤️
Читать полностью…
PWRTelegram API channel
05 June 2019 22:32
You can start reading here :)
P.S. If your code still relies on the old synchronous behaviour, don't worry, there is backward compatibility.
However, old synchronous behaviour is deprecated, and I highly recommend you switch to async, due to the huge performance and parallelism benefits.
In a few weeks I will set MadelineProto 4.0 as default with madeline.php: in the meantime, I do not provide support for the old version.
Читать полностью…
PWRTelegram API channel
05 June 2019 22:32
To use MadelineProto 4.0 w/ async, you have to load the latest version of MadelineProto from the master branch by loading it through composer (dev-master) or with madeline.php:
<?php
if (!file_exists('madeline.php')) {
copy('<a href="https://phar.madelineproto.xyz/madeline.php">https://phar.madelineproto.xyz/madeline.php</a>', 'madeline.php');
}
define('MADELINE_BRANCH', '');
include 'madeline.php';
In a few weeks I will set MadelineProto 4.0 as default with madeline.php: in the meantime, I do not provide support for the old version.
Читать полностью…
PWRTelegram API channel
05 June 2019 22:32
- Async forking (does async green thread forking)
Useful if you need to start a process in the background and you want throwed exceptions to surface up.
These exceptions will exit the event loop, turning off the script unless you wrap $MadelineProto->loop() with a try-catch.
Use it when you do not need the result of a method (see ignored async), but you want eventual errors to crash the script.
Otherwise, just use the method without yield.
// Exceptions will surface out of the event loop()
$MadelineProto->callFork($MadelineProto->messages->sendMessage([...]));
// Exceptions will be ignored
$MadelineProto->messages->sendMessage([...]);
// Like the first one, but the call will be deferred to the next event loop tick
$MadelineProto->callForkDefer($MadelineProto->messages->sendMessage([...]));
- I also created some wrapper functions to work asynchronously with console/browser output
Async sleep:
yield $MadelineProto->sleep(3);
Async readline:
$res = yield $MadelineProto->readLine('Optional prompt');
- Logging is now completely asynchronous and easier:
$MadelineProto->logger("Message");
No need to yield here, because the logging must be done in background.
- Simultaneous method calls:
yield $MadelineProto->messages->sendMessage([
'multiple' => true,
['peer' => '@', 'message' => 'hi'],
['peer' => '@', 'message' => 'hi']
]);
This is the preferred way of combining multiple method calls: this way, the MadelineProto async WriteLoop will combine all method calls in one container, making everything WAY faster.
The result of this will be an array of results, whose type is determined by the original return type of the method (see API docs).
The order of method calls can be guaranteed (server-side, not by MadelineProto) by using call queues.
- Exceptions:
NOTE: Due to the async nature of MadelineProto 4.0, sometimes the exception that is thrown and logged may not be the actual exception that caused the crash of the script.
To let me properly debug the issue, when reporting issues you also have to provide full logs.
- Finally, async loops.
MadelineProto provides some very useful async loop APIs, for executing operations periodically or on demand.
They are the perfect solution for implementing async cron loops, signal threads and much more!
I'll just link you all to the documentation: it has full examples for each and every async API (you can also check out the code, it's full of PHPDOC comments).
Читать полностью…
PWRTelegram API channel
05 June 2019 22:32
To implement async, I wrote loads of new async APIs in MadelineProto, as you may have seen above.
I used the awesome amphp async framework as base, on which to build the new MadelineProto APIs.
I heavily modified amphp coroutines and wrapped all of the AMPHP event loop methods to add native support for yielding generators.
I have also wrapped multiple amphp async libraries for ease of use and compatiblity with MadelineProto settings:
- MadelineProto artax HTTP client:
I wrapped the amphp artax HTTP library for greater security, and to add support for socks5 and HTTP proxies: the proxy settings are automatically extracted from MadelineProto settings.
Soon, MadelineProto's artax will support DNS over HTTPS by default.
I also provided a wrapper version of file_get_contents:
$file = yield $MadelineProto->file_get_contents('https://url');You can use this library to asynchronously download files from the web.
- ALL internal MadelineProto methods were converted to async automatically using
an automatic script: with some changes and conversion to use
php-parser, it can be used to automatically asyncify
any script (will implement in a future version of MadelineProto).
- I created a custom async API to asynchronously construct objects:
This allows you to create multiple instances of MadelineProto
asynchronously, because each instantiation will be done asynchronously.
$com = new \danog\MadelineProto\CombinedAPI('combined_session.madeline', ['bot.madeline' => $settings, 'user.madeline' => $settings, 'user2.madeline' => $settings]);
$com->async(true);
$com->loop(function () use ($com) {
$res = [];
foreach (['bot.madeline', 'user.madeline', 'user2.madeline'] as $session) {
$res []= $com->instances[$session]->start();
}
yield $com->all($res);
yield $com->setEventHandler('\EventHandler');
}
$com->loop();Internally, the combined event handler does
new \danog\MadelineProto\API, but it isn't blocking:
this means that later, when I combine all the async `start()`s into one array and yield it using the
async combinator function, initialization of sessions is done in parallel, and not one after the other.
A
side effect of this is that you must not access or modify the
settings property, at least not until the instance is ready; also, only non-namespaced methods can be called while the instance is still initializing.
To
avoid these problems, simply
yield $MadelineProto->start() before doing
anything else (put a
$MadelineProto->async(true) before that, though).
- I wrapped amphp's helper functions, and created some more:
The
all function you saw above is one of the many combinator functions that can be used to execute multiple async operations simultaneously and wait for the result of all of them.
Each method has different error handling techniques, see the
amphp docs.
Note that if you just take the result of these methods without yielding it, you can use it as a normal promise/generator.
Note: this is
not the recommended method to make multiple method calls on the same instance of MadelineProto; use this only for non-API methods like
start(); for API methods, use
multiple async.
$promise1 = $MadelineProto->messages->sendMessage(...);
$promise2 = $MadelineProto->messages->sendMessage(...);
// $promise3 = ...;
// Equivalent to Amp\Promise\all(), but works with generators, too
$results = yield $MadelineProto->all([$promise1, $promise2, $generator3]);
// Equivalent to Amp\Promise\first(), but works with generators, too
$results = yield $MadelineProto->first([$promise1, $promise2, $generator3]);
// Equivalent to Amp\Promise\any(), but works with generators, too
$results = yield $MadelineProto->any([$promise1, $promise2, $generator3]);
// Equivalent to Amp\Promise\some(), but works with generators, too
$results = yield $MadelineProto->some([$promise1, $promise2, $generator3]);
Читать полностью…
PWRTelegram API channel
05 June 2019 22:32
Even if most of MadelineProto's logic is now concentrated in the new loop and stream APIs, some parts like the TL parser are still there, albeit with many changes.
For example: now the TL parser is fully asynchronous (that may sound a bit weird to some of you, but for dynamic TL parsers, this greatly increases performances and allows parallelism).
The TL deserializer now uses yet another well-structured API called the TLCallback API to automatically populate internal databases directly on deserialization: again, this paradigm greatly reduces complexity, increases performance and is absolutely unique to MadelineProto; no other MTProto client has it, not even official clients.
One of the completely new modules that I created for MadelineProto async is the file reference database: a very complex module, required to handle files in the newer versions of the Telegram API.
It makes full use of the TLCallback API to map files to their origins, to be able to refetch them at any given time when the file reference expires.
Another new module I've implemented is the PasswordCalculator, that is used to calculate the new password hashes for the 2FA login, really cool.
I've also rewritten the APIFactory, the abstraction layer that stands between you and MadelineProto when you do $MadelineProto->method(): it is now fully async, and MUCH faster thanks to a new cached method mapping system.
The same cached method mapping system is also used for the event handler, which means that now the event handler is the fastest update management method.
Читать полностью…
885