1/1/2024 0 Comments Rss feed to telegram channelAutomatically replace emoji images with emoji or its description text.Automatically replace emoji shortcodes with emoji.Drop annoying icons, they break the reading experience.Long images will be sent as files to prevent Telegram from compressing the image and making it unreadable.Images, Videos, and Audio both in the post content and enclosure Documents in the post enclosure.The content of the posts of an RSS feed will be sent to Telegram. English, Chinese, Cantonese, Italian, and more!.Important: If you have your own RSStT bot (v1), please read the migration guide to learn how to migrate to v2. There are other nifty tricks you can do with automation! They represent endless possibilities! (What if you get plain language summaries for every abstract? It is doable and has been demonstrated! That helps filter out relevance quickly).A Telegram RSS bot that cares about your reading experience I am only placing this on record because I could finally implement it on scale. It is like a conference with multiple ongoing sessions and leaving the open hall for discussions. Anyone topic can have specific AMA’s from respective experts and close the other forums for maximal attendance. You can have a common mutual discussion in any forum you wish to pursue. A hypofractionation using SBRT has been published, which can be piped to Radiation Oncologists. It can be delivered straight to pathologists. Let’s say, for example, a new DNA array for lung cancer detection has been published. I can set up highly topical RSS feeds from PubMed to deliver content straight into topics. It can be divided on “Pathology Discussion” (for pathologists), Surgery for surgical oncologists, Radiation for Radiation Oncologists. Here’s for the oncology professionals: Create a group for e.g.You are only limited by your imagination on segregating topics!.A group participation ensures best content surfaces appropriate to discussion, and granular permissions helps preserve privacy. Some users can be set to view bookmarks alone. The best part of Raindrop is that only one individual requires “pro subscription” and that the folder is visible to all participants depending on their access. Collaborating with bookmarks helps preserve the archive.you can have an image repository topic by using the bot to deliver content automatically and keep discussions switched on. General purpose groups can be divided into topics e.g.Dedicated volunteers and admins can watch/respond to topics. For healthcare, you can have patient support groups.The delivery of each source can be tuned in the bot settings through a simple syntax. Reddit, Coub, YouTube etc) and through RSS feeds. Aximobot further delivers to each topic in its configuration!Īximobot fetches resources from numerous sources (e.g. Each collaborative “public” folder on Raindrop has its unique RSS feed that I could connect to Aximobot. Collaborative folders require email invites. I created a new folder on RainDrop, which allows collaborative bookmarking. (As an aside, my Telegram account is categorised in folders) which allows me even more fine tuned control over how I consume information by granular control over notifications. I follow specific Twitter accounts (in a Twitter list) and read them on Inoreader or fetch high value accounts in Telegram through bots, which helps me reflect on their content. This saves time, as I can consume content (on scale), in specific channels, and without any algorithm determining my watch time (e.g. I won’t get into details at present, but suffice to state that Aximo can deliver to Telegram topics. I needed a solution that would “scrape” the information and then deliver content automatically. IFTTT is my preferred bot for connecting various services, but that requires manual intervention on those websites. I was searching for a solution to automate another private group with information from other websites. What if we allow links, but have a workaround without derailing the discussion flow? However, I soon noticed that users were sending direct messages to each other based on mutual permission, of course. The reason? They end up derailing the discussions. Nevertheless, we were also faced with another quandary-links were not allowed to be posted. For simple queries, I could possibly involve ChatGPT in future. That requires extensive writing and effort (in effect, creating a FAQ). The bots can be configured to respond to specific hashtags (or queries) based on notes. However, that was impractical, because users were unaware of Telegram’s capabilities. I had earlier proposed every query have specific hashtags, which is easier to bunch (or even have the bot auto-reply in busy groups). The immediate upside? Owner can respond to specific queries based on topics.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |