![]() ![]() So now I am anxious to know if Telegram has done something brilliant again or if this is a turning point. Settings to delete the account if I fail to log in has existed for years, I wonder if they even did this before Google launched it. ![]() Account recovery is almost automagically simple but has some nifty touches to prevent account hijacking. Recently for example when I started my backup of one of the groups I participate in I had to confirm from a mobile client or wait 24 hours to start backup. Very much of what Telegram has done security wise is very well thought out and has improved over time. Unlike the problems that many here worry about regarding E2E-encryption, this can potentially drag Telegram down to WhatsApp levels, sending huge amounts of user data straight into Google. This might (again, if this blog post is correct and I read kt correctly) be an actual dangerous move from Telegram. More interesting is it that Telegram sends user texts directly to Google without any proxying (did I get that right and has the author studied it carefully enough?). While the legal aspects of this might have to be decided by someone more skilled than me I feel they are morally on the same ground as early Google and if Google makes a big case of it it might backfire spectacularly. An instant user base without having to rely on marketing or word of mouth.Īnd could be used to identify monopolies when there's no middleware for a service.Īs someone who has often defended Telegram I am somewhat puzzled by this one. It could even help third party services pull themselves up by their bootstraps, if they get added to one of these middlewares. Some mission critical software could even be certified as using all adversarial interoperability frameworks. This pattern could be used to identify vulnerabilities in software at the conceptual level, by helping developers to avoid marrying their code to individual providers like AWS. So for example, rather than going onto GitHub to download an SDK for something like Mailgun, you'd download a middleware framework built on Mailgun and Sendgrid. That way the developer could switch between them at any time, or even failover automatically. Building as a network of nodes and funding with crypto would make it harder to attack and take down.Īlong those lines: maybe we could use a middleware pattern for APIs, frameworks, etc where the interface/package would be built as a layer above two or more services. Maybe something architected and incentivised like for adversarial intercom and undocumented APIs. If standardised, whole open source apps could be built around them that allow querying and analysis of data from services and aggregating and automating using the services including optimising prices, taking advantage of offers, and using undocumented APIs to the users advantage. ![]() Perhaps companies and projects would not often use these directly because of the risks (hopefully some would, though!) but individuals could drop the library or the URL to a server hosting it into their apps to gain extra features. I’d love to see and give money to a project to create and maintain easy to use and stable “adversarial interoperability” APIs for as many services and products as possible. When a user sends a message to the bot, the Telegram API will make a request to the Google Translate API, clean the the HTML response returned, and if the detected language of the response is not in English, it will send a message to the user with the translated text.Someone deleted an interesting comment about adversarial interoperability When the API is run, it will poll for any messages sent by users of the Telegram bot. This bot can be used in the Telegram app API will run at the same time the Flask server is started. The Telegram API makes use of a private token specifically provided for our bot that will be used. ![]()
0 Comments
Leave a Reply. |