td
status-desktop
Our great sponsors
td | status-desktop | |
---|---|---|
19 | 7 | |
6,489 | 257 | |
2.6% | 2.3% | |
9.9 | 9.9 | |
16 days ago | 1 day ago | |
C++ | QML | |
Boost Software License 1.0 | Mozilla Public License 2.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.
td
- India blocks 14 mobile apps used by terrorists in Pakistan (includes Briar, Element, Threema etc.)
-
Building a telegram client with react-native (Part 1)
Add to build.gradle(:app) android - see, https://github.com/tdlib/td/issues/1904
Tdlib pre-built library. Android or build from scratch, see TDLib Android example
-
Please a linux client... I'm missing it more than a mobile app.
It would be a good idea for Proton to write Drive using something similar to Telegram's https://github.com/tdlib/td. That way they could write their official clients more easily, and third party clients could be created with a lot of the work done.
-
possible to use td with golang
https://github.com/tdlib/td is it possible to use td with golang
-
telega.el - GNU Emacs telegram client
The problem there is mostly with how they're doing releases for tdlib: They create proper releases for major versions (like 1.7.0, 1.8.0), and then nothing for all for point releases (like 1.7.1), not even git tags - they're seeing those releases as development releases. They do a lot of (breaking) changes and new features between releases - so while distributions might want to stick with proper releases others might want to follow git (and the author is following git with his development branch).
- Telegram has broken compatibility with old clients
- PHP Extension written with C++. Build and check with GitHub Actions.
-
What libraries from other languages do you wish were ported over into go?
tdlib, but it's huge
-
[Feature Request] Limit/disable/remove option to delete chats on both ends
I think taking advantage of https://github.com/tdlib/td (telegrams library) to build some backup mechanism around it would be the best way forward.
status-desktop
-
[1 Year Review] Status still hasn't released anything or gained any real market share in private messaging
In the meantime, desktop already exists but it's just at the finish line w.r.t. good enough feature set and performance to launch broadly. Go check it out at https://github.com/status-im/status-desktop. This recent tweet also highlights some of the massive performance improvements the desktop team is focused on (which will also immediately be available to the mobile app): https://twitter.com/ethstatus/status/1662857323889524739
- Faster Python with Guido van Rossum
-
Is this project dead?
The application consists of the combined efforts of the Status organisation and community contributors, you can follow our development at github.com/status-im/ — you're welcome to contribute as well! If you're running into any bugs, we'd love it if you could file an issue in our mobile or desktop repositories.
-
FB messenger silently censoring links, claims they were sent
For those looking for a no-censorship-ever-of-any-kind alternative, consider Status:
https://status.im/get/
If you don't need or want a crypto wallet or dapp browser, then simply don't use those parts of the app.
Relevant specs:
https://specs.status.im/
https://rfc.vac.dev/
Relevant repos:
https://github.com/status-im/status-react
https://github.com/status-im/status-desktop
There are trade-offs, for sure: since there's (deliberately) no integration with contacts lists (address books) of the OS or other apps, your social circle probably isn't using the app already, or in any case isn't discoverable.
The public chats facility has turned out to be too spam-prone for "well known" / advertised chats, e.g. #status. However, if you create a public chat that has some unguessable component (e.g. #myfriends-a9e72ab5) and you share it with friends (even lots) in a reasonably private context, then the chances of it being spammed are quite low. Note that public chats, while "public", are still E2EE, using the chat's name as the basis for a symmetric key.
1-to-1 and private group chats are highly secure; the latter have a max size, and depending on their size and your device, sending messages can be a little slow.
Creating a robust alternative to the existing public chats facility has involved a lot of work: the forthcoming Communities features provides a discord-like facility whereby founders/admins of communities can take advantage of various mechanisms for moderation and governing membership. The Communities feature can already be enabled in advanced preferences of both mobile and desktop apps, but note it's a WIP.
The moderation mechanisms for communities don't undermine the no-censorship principle of Status because:
(1) Any user can create a community.
(2) A community's rules are managed by those with a stake in the community, there's no override by Status-the-org nor anyone else.
(3) The underlying nodes of the network form a decentralized p2p network, i.e. there's no central actor/authority that controls the flow of messages.
Re: (3), running a Status node should be easy and incentivized.
The "incentivized" aspect is a challenging problem and not solved yet. Long story short, engineering an incentivized decentralized messaging network (not a blockchain!) is harder than incentivizing a blockchain network.
That being said, the "easy" aspect isn't too difficult to solve, sneak peek:
https://github.com/status-im/status-node
Finally, with pertinent laws and regulations in flux across the globe, there could come a day when binaries aren't readily available (from app stores, GitHub, etc.), but thankfully there's always `git clone` and `make`.
Disclosure: I'm a core contributor at Status.
-
Opinions on Status, peer to peer messager(status.im)
My only big issue is that it does talk to googleusercontent.com. Not sure how that can fit with privacy. Heres the github issue.
-
It looks like Signal isn't as open source as you thought it was anymore
Current numbers re: adoption were discussed in Status' most recent Town Hall: https://www.youtube.com/watch?v=98wsQe6hHHs&t=365s
As for dev support: Status has teams of full-time devs working on various projects related to the mobile[1] and desktop[2] (beta) apps, as well projects that are related to the larger Ethereum ecosystem, e.g. nimbus-eth2[3]. Our teams aren't particularly large, but are working steadily to squash bugs and add/improve features. We also have teams dedicated to UX and design.
[1] https://github.com/status-im/status-react
[2] https://github.com/status-im/status-desktop
[3] https://github.com/status-im/nimbus-eth2
What are some alternatives?
tg - telegram-cli
session-desktop - Session Desktop - Onion routing based messenger
mobilecoin - Private payments for mobile devices.
setup-php - GitHub action to set up PHP with extensions, php.ini configuration, coverage drivers, and various tools.
skybison - Instagram's experimental performance oriented greenfield implementation of Python.
Telegram - Telegram for Android source
libsignal - Home to the Signal Protocol as well as other cryptographic primitives which make Signal possible.
status-mobile - a free (libre) open source, mobile OS for Ethereum
Telegram-Bot-Api-Cpp - Telegram Bot Api C++
cinder - Cinder is Meta's internal performance-oriented production version of CPython.