mobilecoin
status-desktop
mobilecoin | status-desktop | |
---|---|---|
26 | 7 | |
1,152 | 262 | |
0.4% | 2.7% | |
9.7 | 9.9 | |
5 days ago | 5 days ago | |
Rust | QML | |
GNU General Public License v3.0 or later | 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.
mobilecoin
-
Is this project dead?
On this day last month, v.4.1.0 of the protocol was released, enabling atomic swaps on the MobileCoin blockchain.
- What's up with MobileCoin?
- Mobilecoin - Private payments for mobile devices.
-
Criticism on the scope and reliability of MOB's reliance on SGX, any thoughts ?
There is a distinction between "begin wrong" and "being so absolutely wrong that making a statement transparently communicates how small one's understanding is". The second applies here. He is absolutely wrong here. SGX is one aspect that has some beneficial contribution to the overall ideas in MobileCoin. It is not at all an elementary part. You can read here in detail what happens if SGX would be totally pwned: https://github.com/mobilecoinfoundation/mobilecoin/blob/master/fog-threat-model-2.1.0.md
-
Is anyone able to withdraw MOB from Bitfinex?
General thoughts for a MobileCoin Fog Threat Model can be found here: https://github.com/mobilecoinfoundation/mobilecoin/blob/master/fog-threat-model-2.1.0.md E.g. you find a summary of what an 'SGX-compromising Adversary with root on Fog Infrastructure' can achieve.
-
There is a new payment feature in Signal (Good!) but the implementation makes me feel slightly cheated about the platform itself.
Since you're passionate about the topic, it might make sense to read a bit about why Signal chose MobileCoin as well as MobileCoin's design goals.
- In defense of Signal
-
Monero fork? Whose mining it then?
You are welcome to audit the code yourself.
-
MobileCoin is incompetent, you need a paid Amazon S3 account to run a validator node.
Link here: https://github.com/mobilecoinfoundation/mobilecoin#consensus
- Signal Just Made One Years Worth Of Server-Side Source Code Available In One Huge Dump
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?
cake_wallet - The open source repository for Cake Wallet, a noncustodial multi-currency wallet, and Monero.com, a noncustodial Monero-only wallet. Need help? Check out https://guides.cakewallet.com
session-desktop - Session Desktop - Onion routing based messenger
td - Cross-platform library for building Telegram clients
skybison - Instagram's experimental performance oriented greenfield implementation of Python.
fog - DEPRECATED: Repo Contents moved to https://github.com/mobilecoinfoundation/mobilecoin
libsignal - Home to the Signal Protocol as well as other cryptographic primitives which make Signal possible.
TextSecure - A private messenger for Android.
status-mobile - a free (libre) open source, mobile OS for Ethereum
Mechanics-of-MobileCoin - Technical exploration of the MobileCoin cryptocurrency
cinder - Cinder is Meta's internal performance-oriented production version of CPython.