status-desktop
session-desktop
Our great sponsors
status-desktop | session-desktop | |
---|---|---|
7 | 301 | |
257 | 1,401 | |
2.3% | 1.8% | |
9.9 | 0.0 | |
3 days ago | 4 days ago | |
QML | TypeScript | |
Mozilla Public License 2.0 | GNU General Public License v3.0 only |
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.
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
session-desktop
-
How does SonoBus compares to Signal with regards to encryption, quality and latency?
https://github.com/oxen-io/session-android https://github.com/oxen-io/session-desktop https://github.com/oxen-io/session-ios
-
"message deleted" prompt still appears after months
This is the correct place to raise feature requests and bug reports: https://github.com/oxen-io/session-desktop/issues
-
session wont connect. is anyone else having issues?
We're at 1.10.8. Please update: https://github.com/oxen-io/session-desktop/releases
- Multiple accounts on session?
-
Signal impersonation risk?
Session's reasoning seems much more... cagey. Telling people to recreate their identities themselves sounds a little like the Threema stopgap solution, but it's much sloppier (I can't imagine end users WANT to recreate their account and communicate this to all their contacts via a third party). They're talking about implementing this eventually, but the ticket for doing so was closed right after saying this.
- Session: ISP can tell when you use the messenger, right?
-
⟳ 6 apps added, 93 updated at f-droid.org
Session F-Droid (version 1.15.4): Encrypted private messenger
- PGP ile elinizde bulundurduğunuz gizli lozan anlaşmalarını (dosya veya metin, ikisi de olur) şifreleyebilirsiniz. Resimdeki dosyanın şifresinin kırılabilmesi için en az 20 yıl gerekiyor (bu da en az, 20 yıldan fazla bile olabilir) Bu programın ne işe yarayabileceğini yoruma attım. (Kaydırgaçlı post)
- Iranian here responding to the signal post: clarifying the internet situation in Iran
-
Help people in Iran reconnect to Signal
Or Briar, Session, Tox, Element/Matrix, Jami...
What are some alternatives?
mobilecoin - Private payments for mobile devices.
Tox - The future of online communications.
skybison - Instagram's experimental performance oriented greenfield implementation of Python.
qTox - qTox is a chat, voice, video, and file transfer IM client using the encrypted peer-to-peer Tox protocol.
libsignal - Home to the Signal Protocol as well as other cryptographic primitives which make Signal possible.
jami-cli - Jami client for terminal
status-mobile - a free (libre) open source, mobile OS for Ethereum
berty - Berty is a secure peer-to-peer messaging app that works with or without internet access, cellular data or trust in the network
td - Cross-platform library for building Telegram clients
Signal-Desktop - A private messenger for Windows, macOS, and Linux.
cinder - Cinder is Meta's internal performance-oriented production version of CPython.
Speek - Privacy focused messenger that doesn't trust anyone with your identity, your contact list, or your communications