Signal-Android
telegram-bot-api
Our great sponsors
Signal-Android | telegram-bot-api | |
---|---|---|
43 | 26 | |
139 | 2,809 | |
- | 4.9% | |
0.0 | 9.0 | |
10 days ago | 29 days ago | |
Java | C++ | |
GNU General Public License v3.0 only | Boost Software License 1.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Signal-Android
-
Signal - FOSS - Issues / Questions When Sharing Location with OpenStreetMap
Haven't used Signal FOSS, but as it happens Molly bas just implemented OSM support, perhaps when it lands you might have better luck with it. Anyway, is there no issue tracker for that fork? I tried looking in their repo and found it disabled
- Signal messenger not receiving messages on Qin F21 Pro
-
Signal doesn't run in background on Qin 21 Pro
Try using the Signal FOSS version from https://www.twinhelix.com/apps/signal-foss/
-
Signal discontinuing SMS support.
Yeah I followed that whole story. Since then some forks have been created that do not care what Signal Foundation thinks about using their servers. Molly and Signal-FOSS for example, both compatible to regular Signal. Those two forks will not keep SMS support, Molly never had it, and Signal-FOSS will most likely drop it because they think it's too much work to keep it while staying compatible and up to date. I hope there is going to be another fork specifically dedicated to keeping SMS support. We'll see.
- L'Europe se dirige vers une fermeture de Facebook après que l'Irlande a déclaré qu'elle envisage d'empêcher Meta d'envoyer les données des utilisateurs européens vers les États-Unis
-
Is Signal %100 open source?
You can get a completely open source version without the Google stuff here: https://www.twinhelix.com/apps/signal-foss/
-
What is the best fork for Telegram and Signal
Signal FOSS removes proprietary google blobs https://www.twinhelix.com/apps/signal-foss/
- Some user recommends Sinal-FOSS (F-Droid) from TwinHelix? I see only some random Reddit users mentioning it.
-
Top rated alternative FOSS apps to access social media with privacy in mind (05/2022)
Signal - Molly , Foss-Signal
-
SMS app supporting Google RCS
Maybe they had outdated info from when the server software was not updated for a long time. Or, it's regarding the dependencies on closed-source Google Mobile Services and Firebase libraries, though those can be removed... and have been in this fork.
telegram-bot-api
-
Hide sender name
Is not that hard, they have amazing documentation about it: https://core.telegram.org/bots
-
Telegram OAuth Authorization for Your Site
You can make authorization via Telegram another way. It works. But today we want to do the classic OAuth Authorization. Before you begin, you need to create a Telegram bot and obtain your bot token. You can do this in @BotFather in Telegram. For more information on initiating a bot, read the Telegram Bot API documentation: https://core.telegram.org/bots
-
Is my idea possible to implement?
Absolutely possible. Here's the github page to the Telegram bot API. You would just need to check for incoming messages, check the body of the message for a word or phrase, and then send a message back with a photo or gif and an encouraging message.
-
How I built an AI-based Telegram bot in 21 minutes with Make and OpenAI
Creating a Telegram bot is fun: there's no website, no sign up, no forms — you just use a... bot. Yes, a bot that creates bots. It's called the BotFather 😂
-
A simple forwarder from WhatsApp to Telegram written in Go
Telegram has a bot API server that provides API to control the bots and get updates. Their own instance has some restrictions like you cannot download files bigger than 20MB. So, using a self hosted bot API server, you can overcome those limits.
- Serverless + JS: Um bot de web-scrapping diário
-
From BotFather to 'Hello World'
General Bot Platform Overview
-
Não consigo abrir api.telegram.org na Claro
$ curl -4 -v https://api.telegram.org * Trying 149.154.167.220:443... * TCP_NODELAY set * Connected to api.telegram.org (149.154.167.220) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): * TLSv1.3 (IN), TLS handshake, Certificate (11): * TLSv1.3 (IN), TLS handshake, CERT verify (15): * TLSv1.3 (IN), TLS handshake, Finished (20): * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.3 (OUT), TLS handshake, Finished (20): * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 * ALPN, server accepted to use h2 * Server certificate: * subject: CN=api.telegram.org * start date: Mar 24 15:21:45 2022 GMT * expire date: Apr 25 15:21:45 2023 GMT * subjectAltName: host "api.telegram.org" matched cert's "api.telegram.org" * issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2 * SSL certificate verify ok. * Using HTTP2, server supports multi-use * Connection state changed (HTTP/2 confirmed) * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0 * Using Stream ID: 1 (easy handle 0x555fdb2de2f0) > GET / HTTP/2 > Host: api.telegram.org > user-agent: curl/7.68.0 > accept: */* > * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * old SSL session ID is stale, removing * Connection state changed (MAX_CONCURRENT_STREAMS == 128)! < HTTP/2 302 < server: nginx/1.18.0 < date: Tue, 18 Oct 2022 00:00:24 GMT < content-type: text/html < content-length: 145 < location: https://core.telegram.org/bots < strict-transport-security: max-age=31536000; includeSubDomains; preload < access-control-allow-origin: * < access-control-allow-methods: GET, POST, OPTIONS < access-control-expose-headers: Content-Length,Content-Type,Date,Server,Connection < 302 Found 302 Found nginx/1.18.0 * Connection #0 to host api.telegram.org left intact
-
Can anyone teach me how to make these?
It's done via bots, which let you add clickable options to posts. Here's an FAQ on bots: https://core.telegram.org/bots
- Desarrollando un Bot para Telegram
What are some alternatives?
TextSecure - A private messenger for Android.
aiogram - aiogram is a modern and fully asynchronous framework for Telegram Bot API written in Python using asyncio
Signal-Desktop - A private messenger for Windows, macOS, and Linux.
Gotify - A simple server for sending and receiving messages in real-time per WebSocket. (Includes a sleek web-ui)
LibreSignal - LibreSignal • The truly private and Google-Free messenger for Android.
python-telegram-bot - We have made you a wrapper you can't refuse
axolotl - A Signal compatible cross plattform client written in Go, Rust and Vuejs
n8n - Free and source-available fair-code licensed workflow automation tool. Easily automate tasks across different services.
nheko - Desktop client for Matrix using Qt and C++20.
Telethon - Pure Python 3 MTProto API Telegram client library, for bots too!
Shitter - Lightweight Android app for Mastodon