I agree, this post doesn't address any of the real feedback. I'm a fan of Signal, and I think a crypto wallet inside Signal could work, but it should:
- Not be MobileCoin or any small-cap coin
- Support Bitcoin/Litecoin/Etherum/other popular and trusted coins
- Sync private keys using the same mechanism as messages
Signal has had some questionable choices in the past, but this is over the line for their goal of privacy/security/trust. MobileCoin does not belong in Signal.
> - Support Bitcoin/Litecoin/Etherum/other popular and trusted coins
The post explains their requirements which these cryptocurrencies don't fit. Do you take issue with their requirements?
> Sync private keys using the same mechanism as messages
AFAIU it's non-custodial and it stays on the mobile client, meaning that there's no synchronization so far (the desktop client does not support these features). This could come eventually, but it's part of their requirements to stay out of the way and let the user handle their coins without trusting Signal.
> this is over the line for their goal of privacy/security
Because the price of small cap coins is insanely volatile, and even more subject to manipulation than cryptocurrencies in general. Mobilecoin's price changed by 1000% over the course of a couple weeks last month.
If this was a public rollout I'd be more inclined to agree but as a opt in beta for a limited number of users who explicitly opted in to provide feedback this is less of an issue.
The future volatility of MobileCoin is to be seen. Past performance is not indicative of future performance and whatnot.
Wether they should have used a test net, MobileCoin should have only released a limited portion of the coins or whatnot is another question entirely.
> Mobilecoin's price changed by 1000% over the course of a couple weeks last month.
It's not even really used right now, it's hard to tell how much it reflects what will happen later.
With a centralized cryptocurrency there's a lot they could do to make it less volatile, and it's still to be seen what will happen in practice. It's a hard problem, but I don't think we can easily conclude that they will fail, or that a better solution already exists.
Why should it not be all those same things, except also a stablecoin, so that the price can't fluctuate and the owners/speculators can't make massive profits off of manipulation, exploitation of others' manipulation, and social dynamics?
The goal is to transmit money through a mobile messaging app. If the MobileCoin wants to take donations to support the platform, or even wants to take a tiny cut of each transaction, that seems fine. But I see no justification for their platform to be based around a volatile speculative asset which generally serves no purpose but to create a new gambling market and enrich the founders.
A mobile-friendly alternative to Monero seems like a really cool, valuable idea. But I don't think it's acceptable that it's both a volatile security to speculate on and the payment system for a supposedly non-profit privacy-and-freedom-oriented messaging app.
The problem isn't cryptocurrency; it's penny stocks and all the zero-sum bullshit that comes with them. You don't have to make your new cryptocurrency a penny stock if you don't want to. Here, it seems they probably want to.
In short it's a a hard problem and area of active research.
Stablecoin mechanisms have tradeoffs whether that's being on a public blockchain, a centralised party, collateral risk or lack of privacy. Monero is the current gold standard when it comes to privacy but trades off speed (confirmation blocks), mobile friendliness and a volatile price. On the other end of the spectrum Tether is very stable but is produced by a centralised entity and is on a public blockchain.
From Moxie's 2017 interview (https://www.wired.com/story/mobilecoin-cryptocurrency/) we can safely assume that their list of requirements existed from the start (MobileCoin didn't have much to show at this point). Since then it's been public knowledge and since the market cap of MobileCoin is dictated by the market so I'm not sure about your penny stock comment, it seems more sensible to direct criticism at their lack of distribution transparency.
Maybe they should rename MobileCoin to SignalCoin since it appears that was the purpose all along.
As for the conflict of interest, Moxie appears to (currently) have a "name your price" reputation so he could have chosen any cryptocurrency and they'd probably pay him the same advisor fee. When he says that he chose/founded MobileCoin because in his opinion it's the best (in his value system), I actually believe him.
Isn't that still a huge conflict of interest? As a key person of a foundation he should not be charging a private advisor fee from a company whose products the foundation plans to promote in the future. That seems like an excellent (and immoral) way to use a foundation enrich yourself.
Woah so MobileCoin implements everything Monero has but with the Stellar/Ripple consensus model and uses intel SGX coprocessor?
That’s kind of interesting, cheap fast transactions, not proof of work, and only the validators have the SGX burden (Secret network does something like this with SGX for private-ish smart contract execution)
So we dont like the premine and the forced integration and pump, which is meh to me, everything is premined these days I cant care much about that.
I’m actually surprised it has some cool technology involved, most “privacy” coins dont pass the smell test and with a name like MobileCoin I just assumed the worst, but I still have to laugh that the purchasers had to do KYC then.
Oh crypto.
Its pretty clear that they omit some information to give people less to disagree with. They pump it and sell, thats going to happen. I don’t care much about that either, speculators are going to get sold into, that’s not even controversial.
The Signal forced integration is grimy.
I still wish there was a stable privacy coin. USDC and DAI on Tornado.cash is okay, but too few inputs to mix with. Mobilecoin doesnt solve that, just another volatile asset.
Perhaps you'd be interested in TUSD on SCRT[0] (or any bridged stablecoin) that can be wrapped in SNIP-20[1]. As far as I know this is as private as you'll get when it comes to a stablecoin.
Partisia[2] (currently in beta) and Tari[3] could provide something similar.
I think by being SNIP-20 they would hide the amounts by nature of the private smart contract execution but would still show the sending address, perhaps the receiving address would be hidden as well due to the private smart contract execution.
I haven't used it yet because I havent acquired any SCRT for the transaction fees on that blockchain, but any variable should be hidden for a smart contract (of which tokens are), while the initiating address writing to the blockchain would by visible for consensus purposes and state management.
Sadly, the LAST thing I ever wanted the signal foundation to do. And this adds to the PIN & cloud "features", insistence of a phone number, refusal to work with 3rd-party apps...
I'd rather them have done _nothing_ at all.
Oh well.. further proof you really need federation.
Open protocols is the way. Then if a client starts acting sketchy or bloaty, you can ditch it for a better one.
Plus, an open protocol changes the risk calculus for the group that manages the client implementation, in a way that would prevent situations like this one.
However, open protocols beget federation, so I don't think you're at odds with the above poster. Email, DNS, etc are all open protocols with federation built-in, but we trade away some centralization of servers (GMail, Cloudflare, etc) in exchange for nice things (DoS protection, spam filtering, etc).
In the worst case, where a server starts acting scammy (like embedding ads in your email) or tries to diverge from the protocol, you can always go back to hosting it yourself, or paying a small and trusted shop to host it for you.
In the arena where Signal is competing, Matrix [1] is probably our best bet. (Assuming irc is too barebones for your needs, in 2021). It has also supported end-to-end encryption for some time now [2].
No, you do not need federation. You need an organization and leadership in it that is focused on their mission.
For example, Let's Encrypt reliably, like clockwork, distributes certificates and maintains related PKI infrastructure. That is what Signal was supposed to be (at least, my interpretation based on their PR) with regards to secure messaging, and they have utterly failed to maintain the focus you'd expect of a non profit with their mission.
If I want payments (unregulated payments at that), I would use and donate to a payment app, not a messaging app. But heh, report it to regulators and let them be the bullwhip to Signal and their poor choices if they ignore the community (who are their stakeholders as a non profit entity). Of all the ways to kill your project, this doesn't seem like the "hill to die on." Don't drag secure messaging into your fight against nation state currency regulations, and have some common sense about compartmentalizing around regulatory risk.
Which is why you need to see "where's the money coming from" because a non-profit that can't survive will go looking for it. Let's Encrypt is small enough that it can entirely exist under the donations of some of the large internet companies - Signal doesn't have that and so the temptation to look for money will be there.
No, I'm talking about the company/organization itself. A non-profit like Signal can be all high and mighty and principled as long as the bills are being paid (by whom?) but once that dries up (or never materializes) the temptation to monetize by doing things that go against the original mission becomes greater.
Let's Encrypt doesn't have a reason to try to blockchain their certs because their bills are being paid. Signal clearly wants more money (they openly state that the coin will pay $1m/yr to Signal).
As far as I know Signal has no issues with funds. I feel this is more about Moxie and potentially other employees who want to make money for themselves, not for the foundation.
I'm not a fan of any kind of crypto, but the handwaving excuses for why they aren't pursuing alternative currencies are laughable. You could say the same about MobileCoin, and you don't provide any other justification other than blanket statements without citations.
Signal, your bias is showing, and it makes me wonder what other vendors will get your ear and be integrated in the future.
I’m in the crypto field and no, it’s not laughable, it makes sense to me. Very few cryptocurrencies are good at targeting mobile users unfortunately. I think both Celo and Diem have good chances due to the fact that you can prove everything pretty easily to the client (and Celo does it with recursive zero knowledge proofs) but they are not privacy coins.
This explains the issues fairly well. tl;dr most blockchains require a CPU and/or network expensive sync which is prohibitive on mobile. As a fix/hack many web and mobile apps have a SPOF gateway which the client must trust absolutely.
The whole point of cryptocurrencies is that you don’t need to trust that your bank and all the other banks have settled funds correctly, you can verify that they’ve done it (to some extent). In the case of your experience, you have really no clue if the number your bank is showing you is accurate (and indeed errors are frequent, you probably have seen double charges or transactions that later disappeared).
In the context of a cryptocurrency like bitcoin you also have to trust the server you’re talking to, if you’re a light client (a client that doesn’t want to download the whole history). So Bitcoin is not a great choice for mobile clients that don’t want to have to trust another third party. Which in general is the threat model of Signal.
So, in short, a mobile-friendly network is a small network with simple algorithms and fast transfers, where every address is pseudonymous and may drop in or out at any time with no reputational results? These are very bad properties for a blockchain to have, from an integrity context.
That’s not what I said: a mobile friendly cryptocurrency is a network you can query and that gives you a response you can fully verify: this is your account balance at this point in time, and it’s correct you can verify it with this proof of a small size (because in some coutries you’re paying for every bytes you’re downloading).
Now fast transactions (finality) is an upside for any type of currency really.
In addition to the conflict of interest Moxie has (and, honestly, I can see that side -- of course he'd want to be involved in the cryptographic design of a privacy-preserving payment system -- but he still needs to come clean about his relationship with MobileCoin), the most disturbing thing to me remains that the source to the server wasn't publicly updated for nearly a year while they added this feature, the timing of when the source went dark clearly indicates that specific intent, and Moxie's statement as recently as January that they didn't have specific plans to add payment/cryptocurrency when it's clear from the server source that they had been working on it for many, many months at that time.
What is up with people thinking he's not "come clean" about his relationship with it? He/Signal have noted they own no MobileCoins, and that he's been a paid advisor to MobileCoin. Doing anything behind the scenes feels like it'd be inviting SEC attention, which MobileCoin seems to want to actively avoid by trying to keep Americans off of it.
What lack of transparency do people feel is missing (beyond the server source not being updated - I agree that's a big miss)?
As the server source drop showed, they had been working on it since April 2020, publicly downplayed the idea just three months ago, and then... launched the beta. I would describe that as pretty deceptive.
"Marlinspike played down the potential of crypto payments in Signal, saying only that the company had done some “design explorations” around the idea. But significant engineering resources have been devoted to developing MobileCoin integrations in recent quarters, former employees said."
It would be an enormous conflict of interest if Moxie had a financial stake in MobileCoin, and then drove signal to adopt this random crap coin.
These guys keep on claiming just to be technical advisors with no financial interest or benefit from mobilecoin. BS.
Let's get some auditors into Moxies / Signal Foundation stuff, figure out how this decision was made, if signal foundation received fair value for pushing their users this way etc etc.
I got voted down before for saying this, but will keep on saying it. You can't use a charity and then leverage that charitys assets to enrich yourself outside of the charity.
What's interesting is despite all the claims of "trust" and "security" vs using google etc these guys turn out to be what appears to be scammers.
"Signal Messenger LLC. was founded simultaneously with the Signal Technology Foundation and operates as its subsidiary. Its CEO is Moxie Marlinspike and it is responsible for the development of the Signal messaging app and the Signal Protocol."
These single member LLC's are considered disregarded entities in most cases. Many nonprofits use LLC's to own property, do app development etc for liability reasons. That doesn't obviate their need to act in a manner consistent with their parent entities objectives and public purpose.
You claim to be judge, jury and executioner in one. I agree it all looks odd, but I can also see why no other integration might easily work. Would be good to dig for any possible issues but it might well be that that they write is actually the real set of reasons. I won't leave signal anytime soon both 1) because I see weirdness but no proof of wrongdoing and 2) because there is literally no better alternative.
Strongly agreed. And Moxie has not denied being paid in stocks or stock options for his "technical advisor" position. But even if he was just paid in cash it would still be a conflict of interest. If MobileCoin needed him a a technical advisor they should have paid the Signal Foundation a consultancy fee for Moxie's time, not Moxie himself.To an outsider it looks very much like he used a donation funded foundation to enrich himself.
Telegram's just better and doesn't need a centralized shitcoin.
Instead of using the battle hardened technology that Monero is, Signal chose to create a *99% garanteed coin full of bugs to come in the future.
- Privacy and Software ain't easy and monero is the best example of it and the many upgrades it has had and bug fixes during all these years.
Have fun losing your customers money!
Telegram tried to create their own cryptocurrency _twice_ :
Gram which was cancelled due to the SEC cracking down on unregistered ICOs and TOM which is no longer affiliated with Telegram at all.
People's insistence at bringing up Telegram as an alternative to Signal seems to be as incoherent as bringing up Go on a Rust thread. Their similarities end after the level-0 description as "recently-ish released messaging app / programming language". Telegram's requiring users to opt-in to encrypted messaging on a per-thread basis does not enable claiming feature parity with Signal's always-encrypted threads.
- Moxie's involvement with MobileCoin (could be as simple as saying: "for the same reasons Signal's interested in MobileCoin, moxie is as well").
- The concerns about regulatory risks/attention involved with a cryptocurrency integration.
- Why it involved hiding the server source code.
The idea of privacy-friendly transactions easily available within an app I'm already using is attractive, but I very much hope the obvious concerns won't play out in practice (which time will tell), and it would be good if they'd also addressed the above.
> - Why it involved hiding the server source code.
My guess: to reduce the noise and speculation. Much better to deal with it now that there's something to be gained (feedback from beta testers and actual deployment). There was little to gain before, since the server accepts very few contributions anyway.
I wander enough on GH to see how much time big open-source project maintainers spend addressing toxic comments. Open-source is nice when you get relevant contributions and constructive feedback, but it's really not free, you have to deal with all the rest as well.
Well take it further – is is still open-source if you update the public repo once every 10 years?
For the vast majority of people, OSS in 2021 means having a public repo hosted somewhere that all commits are pushed to, or PRs are made to. Periodically updating a public repo with changes made to a private repo is not really what people have in mind.
The biggest example I can think of projects that worked this way was how WebKit and Android would publish code dumps with every release. You can't go longer than that: if you put out releases without updating the source you're not open source.
Interestingly one of the comments in that thread refers to the server code as a reference implementation. This implies that Signal's server code isn't opensource, and that this code is just a reference implementation.
The readme.md on the repo doesn't really clarify one way or another on the matter.
Signal claims they shipped server updates without releasing code? Do you have a link to that?
When others were complaining about the lack of an update to server, they're complaining about the client and server APIs being out of sync. Reading through these comments, I don't get the impression that the server code published is what's actually running. In fact the following comment even refers to it as a reference implementation:
At the end of the day, it doesn't really matter much what server code is running since the Clients manage encryption and the Server has no insight into the messages being exchanged.
Can they? First they'd have to never have accepted contributions, then if they ran an updated version on their server wouldn't they be in vialation of AGPL (not providing end users, in this case specifically those who use Signal an updated codebase).
If they have never accepted contributions, then they are the sole copyright holder, and thus can do whatever they want with the code. Including not providing the source code to users.
You can't sue the copyright holder for infringing their own copyright.
They have a CLA, the legal side of things is clear. They can use their code however they want, the licenses are only relevant for others. When you contribute, you basically license your code under a permissive license to Signal (because of the CLA).
It is not about how often you update your project.
To be open source, you need to publish the source of applications you run. It's as simple as that: "we developed this app, and it's running on our servers, and the source can be found here".
They kept updating their server app for a year, without publishing their source. This is not open source. Signal server code was not open source for a year.
Isn't the allegation that they made changes to the deployed version of their production server that were not pushed to the GitHub project? (i.e., that they stopped updating the server repository for around a year, but not just implausible but contradicted by evidence that they never changed the server code for about a year?)
If so, then the code quite simply is not open source by any possible definition. I agree with you that a project that is dormant, or even receiving internal development that is still under review, can defensibly be called "open source" even if the development isn't happening in the open. (For instance, your favorite begrudgingly-GPL-compliant hardware vendor who releases .zip files every time they release a new product is releasing "open source" code.) But if the source code to the Signal server isn't even published, it can't be open.
I sympathize with this. On the other hand, you have to consider the big picture:
- the open-source argument was mostly meant for everyone to look at the sources and draw their conclusions regarding privacy and security
- these guarantees are mostly client-side (and you can't check what's running on the server anyway, even with the code)
It's fair to say that the server code was proprietary for one year. Most of their code was still open-source during that time, and most of it (now that they push to the server repo as well) is now.
I feel they would have taken less flak over this if their server code had never been open-source to begin with, or if they just released it now.
Why do you think more transparency would lead to noise and speculation? Exactly the opposite is the case. They could have gone the open route and maybe even gotten help from the community at implementing their payment feature.
But the way they did it they left everyone wondering whether their server is now spyware or what other reasons there could be for them to not update the public repo.
> Why do you think more transparency would lead to noise and speculation?
Because of the current situation: people argue about whether Moxie lost it, if Signal is still the right solution, etc.
If the feature had been implemented in the open, this debate would have taken place since the beginning, again with little benefit.
> maybe even gotten help from the community at implementing their payment feature.
Signal does not have an open development model. They're a small team, and most things beyond bug fixes are done by them. You can debate whether that's the most efficient approach, I'll just say it's an open question, and that's the model right now. So contributions to this brand new feature by the community would not have been possible.
> But the way they did it they left everyone wondering whether their server is now spyware
If people misunderstand that most of the security guarantees come from the clients, there's little an up-to-date repository on GitHub can do. I think the noise and complaining that has been happening for one year about the closed-source server is still negligible to what's happening now.
I would have preferred if they had kept it open, but I can definitely understand why they thought it was a better course of action.
Also: why Mobilecoin, which is as far from "an alternative payments infrastructure" as most other cash-grab cryptocurrency ?
It isn't known how much of it was premined, and from an early version of their whitepaper, the founders might have as much as 80% of the total supply of the coin. This isn't fine for a cryptocurrency which aims to be "an alternative payments infrastructure", and it isn't fine for Signal to try to promote them as such.
To play Signal's advocate, MobileCoin is one of the only cryptocurrencies that meets their requirements. The only other cryptocurrency that I know of that might come close is Grin.
The details of the distribution are lacking but as a beta it meets the experience they're going for - it's not as if they'd choose something that doesn't meet their requirements for the beta.
To clarify the only coins that meet their privacy requirements are ZCash, Monero, and MOB. The only subset of that that meets their transactional speed requirements is MOB.
At least AFAIK. There's a ton of alt coins so I might have missed something.
Their "privacy" is strongly based on the confidentiality of SGX. If you're willing to trust SGX for your confidentiality and security, as they have, they could use any cryptocurrency in a highly private and instant manner.
MOB is transparently a scheme to generate a windfall from shoving a pre-mined coin into a mass-market application. One could debate the ethics of that with a straight face, I suppose, but to argue that it is anything but is just dishonest.
My understanding is that SGX is only a layer. As in that it acts like ZCash or Monero and then has SGX as an additional layer. Even Signal uses SGX. But breaking SGX isn't going to break Signal. Also, my understanding is that these speculative attacks are still difficult to pull off in the first place. I mean everything is hackable, question is how easy it is to pull off.
The monero like part effectively runs on their servers inside SGX for performance reasons. If the SGX were completely insecure the users would have no privacy against the operators at all.
The client fully identifies itself and its keys to the server, the wallet is entirely implemented server side. Without SGX there is no privacy what-so-ever.
Usage of ringct is incidental. It's like claiming that your documents are private when your operating system submits them all to the NSA because the NSA encrypts them after receiving them. :) (and, of course, we trust the NSA to behave honestly...)
You got sources for that being how the construction works?
From various telegram groups with the devs in them , my understanding is 1) rings are constructed client side 2) uploaded to the server inside SGX. This has two major weaknesses 1) it doesn't specify how payment notification happens, which can be a massive privacy hole 2) if SGX is broken you are subject to all of the long term intersection attacks on Monero's/k-anonymity because the rings are now public.
This is a very limited threat model and worthy of serious scrutiny.
Also, _even if_ we steel-manned the design and imagine SGX is truly only used as a "defence-in-depth" layer on top of a ringct blockchain, using SGX to prove that SGX Lightning nodes weren't keeping transaction info would still be better privacy under many circumstances.
Lightning transactions are ephemeral: once the transaction happens, _no_ data about the transaction actually needs to be kept by anyone, let alone on a public blockchain. And only the peers directly involved in the route ever learn about the transaction directly.
Whereas with SGX, if SGX is broken in the future - and it will be - the statistical analysis on the underlying blockchain data is still possible. And unlike MobileCoin, this design wouldn't put SGX in any kind of trust or custodial position at all: if SGX failed, you'd just close the Lightning channels the same way any other Lightning implementation would, and open new channels with non-SGX peers.
I clearly misunderstood you but can you explain how you've come to that conclusion?
I'm trusting their whitepaper but it looks to me that fog provides similar security guarentees between MyMonero (shared view key) and other light wallets (computation on device).
I don't see how the privacy could be any worse than MyMonero even if SGX was compromised.
At best we know that he (claims to) have no coins. But that he was an advisor for them and focused on what he saw as a problem with crypto payments: speed. But yeah, there are still a lot of open questions here.
> The concerns about regulatory risks/attention involved with a cryptocurrency integration.
They addressed this before and the code reflects it. They whitelist country codes that allow it.
> Why it involved hiding the server source code.
This was weird and I'd like it addressed but probably not relevant to this particular topic/post.
> The idea of privacy-friendly transactions easily available within an app I'm already using is attractive,
Same. I mean it is a core element of the cyperpunk manifesto[0]. But I don't want to use a payment system that is volatile. If I have to choose to be beholden to services that collect my data or use a currency that is volatile, I'm going with the former every time. This is the question that I would have liked to be further addressed.
Even if he has no coins personally, that's a very narrow claim. Far more likely is that he has an interest in the company which happens to have pre-minted and owns most of the coins.
I mean, regardless of whether they addressed it before, to me this blog posts reads like their attempt to address all concerns raised in a single place, and these are all concerns I've seen raised. Thus, it seems to be like it would be very relevant to address them in this post, and would help restore some of the trust that some people already lost, and that others are at risk of losing.
After the last discussion I have been trying Element. It has some rough edges still but it has vastly improved since the last time I tried it.
Additional bonus, no electron based client, native apps for ios, Android, Web, Mac and even Linux.
If they can make the verification process for a new device smoother, I can recommend to folks. My worry is the amount of influence I used to get people to switch over to Signal only to ask them to switch again
The "Element" branded desktop apps are actually based on Electron, but since the underlying Matrix protocol is open, there are a plethora of fully native third party clients in varying stages of development.
Oh no problem at all -- I think it's a great counterpoint to closed ecosystems like Signal and Discord which are actively hostile to third party clients.
It's still early days, but Element is genuinely committed to Matrix's success as an open protocol, and I find the community enthusiasm to be very encouraging.
I have found instructions to reverse-proxy matrix service, which satisfies my need for a minimal cloud presence and private (behind enforced NAT) homeserver. Combined with p2p via SQLite dendrite, that might solve my whole problem. (Is Dendrite considered ready for personal use, e.g. p2p, even if not a replacement for Synapse? What should I watch out for?)
I have not found details about identity portability vs. Synapse version. Can identity be ported out of a Synapse 1.29 homeserver?
The problem with Element is that the matrix.org main servers can already often be slow with message delivery, and will only get slower as more people onboard.
And self-hosting Matrix is hard and requires pretty hefty hardware. If performance improves, it will certainly be a great option. For basic chats though, XMPP+OMEMO is still a really great lightweight option.
It's not something that is always reproducible, and I suppose it depends on traffic and location as well to a certain extent. I've certainly found it satisfactory for general conversation but I do often see delays in delivery.
This is, however, something I also see with Signal. Texts can often take 5-6 seconds to deliver.
I'm excited for Dendrite, their new homeserver written in Go which will hopefully solve at least some of these performance issues. I've hosted a Dendrite server for a couple months now, but haven't had the chance to use it much.
With that said, it's been disappointing to see how slow development has been on it. Hopefully it picks up and they can get it out of beta this year.
Im looking forward to Dendrite, I think that changes the game for them in terms of performance. If im not mistaken at least one server was running on dendrite
They have https://dendrite.matrix.org, and they use Dendrite to test new features (like Spaces). But its issue is it's not feature complete so I don't think it sees that much usage.
To all those complaining about this feature in signal, can you answer this question- how is a non-profit dedicated to providing a safe messaging supposed to make money to drive that mission? Do you think they will be able to compete with those deep pocket ed competitors to achieve their goals? Have YOU donated significant money regularly to signal to support them? If not why the hell are you cribbing about this change?
This is not an argument. I do support XMPP developers who do great work with a budget that is less than 0.1% of signal’s , without vendor lock-in, and without partnering with dubious cryptocoin schemes. Granted, they do not have the "hacker extraordinaire" moxie vibe, but they get work done.
Because of the lack of transparency. Signal users are not naive and can deal with the truth. If they need money, or want to be profitable why is there zero mention of in in the explanation? Whatsapp was dead to me the instant zuckerberg said it will always be free.
Thought experiment: If the payments feature was based on a fork of MobileCoin that distributes all pre-mined coins evenly to all existing Signal users, rather than the status quo, would people be still upset?
I think it would address some concerns, but personally, mixing concerns of secure messaging and cryptocurrency payments would still make me too uncomfortable.
Something somewhat similar already happened: Stellar gave away XLM to Keybase after Keybase added an integrated Stellar wallet. Many people didn’t like it[0], even I was not too impressed despite working in the Stellar ecosystem. Some people didn’t like the mix of cryptography and cryptocurrency (at least, I certainly didn’t)
It's getting harder and harder for the tech elite (including HN) to denigrate crypto as something that is worthless. Bitcoin 60k, Ethereum innovations, NFTs, Coinbase IPO, every bank and financial company having a crypto / blockchain plan, and tens of millions of Americans owning cryptocurrency... not sure how much longer the blockchain haters can claim that all of this is 100% worthless.
I think this point is too technical to be addressed in this blog post, and it's already addressed in technical documents / talks from MobileCoin. In short, and IIUC, no Intel SGX means a bit less privacy but is still ok. In particular, it's not a kill-switch. Happy to be corrected though, I still know little about MobileCoin.
It's true an SGX compromise means most of the MobileCoin privacy goals are still met. But dsome compromises would open up new methods of traffic analysis, and the SGX-dependency still makes the consensus process dependent on Intel's trustworthy key-management.
If I understand correctly, Intel could (if compromised or untrustworthy):
* revoke any node's SGX keys - knocking any number of consensus nodes out at zero cost
* create false attestations of what code was run (which would presumably be detectd eventually)
* dominate the consensus mechanism with its hand-picked SGX nodes
Among other things, this means Intel could turn off the MobileCoin chain, if commanded to do so.
(I could be somewhat off on some of this – if so, corrections with explanations very welcome.)
So, if your threat model is "Intel Inc is always trustworthy & secure", Signal & MobileCoin are wonderful. If you have doubts about Intel's trustworthiness/security, the designed privacy properties start to degrade.
Signal's increasing reliance on SGX is the elephant in the room. They keep announcing new features that require sending your cryptographic keys to someone else's "super trustworthy" computer.
You don't think the sealed sender feature is an improvement at all?
Nobody relies on it. But if we can make an attack 10 times more expensive (because we can't prevent it completely), why not do it?
Secure remote computation is better than nothing. I'd start having problem with it when people rely on it when there are better solutions, but that hasn't been the case so far, AFAICT.
What a handwavy article full of stuff that's not addressing the real issue in discussion; collusion with MobileCoin.
WhatsApp management must be really happy with this sudden move from Signal. Signal has lots of detractors who would like to discredit it, and Moxie and co. just handed it on a platter to them.
Although the relationship isn't clear and not clarified I find the article does a good job at addressing why they chose MobileCoin - the list of requirements.
Generally people probably wouldn't be so hostile about making a new cryptocurrency in general, there's well over 1000, but premining and bring up front about the premine is very important info.
> I’m not a beta tester, but cryptocurrency is the worst
100% this. I'm not a beta tester, but I am a signal user. I reeeally don't want to have to hedge my recommendation of signal because it's involved with some cryptocurrency BS. Please, just be a chat app.
Ever heard the expression “do one thing well”? Unix applications were built on this principle, if you need a reference.
Let the chat app be a chat app. Let the payment app be a payment app.
Or, to put it another way, do you recognize that a chat app and a payment app have different incentives? Combining them means now your chat app has payment app related incentives. Do you see this as a good thing? If so, why?
This is an often said criticism but the reality is that the mobile app ecosystem fundimentally breaks this principle.
When was the last time you saw an mobile app taking advantage of another one apart from tre camera? The only and most common time Android apps communicate is with Google Play Services.
Context switching on mobile or GUIs in general also don't follow this principle. Modern GUIs integrate plenty of things (file explorer, image editor, basic camera, etc) becuase mobile package management doesn't resolve dependancies automatically or allow for a great deal of UI customisation. Especially in a messaging client imagine not being able to send photos, videos, audio, or files!c
GUIs are here to stay so until we figure out a composable and we'll adopted GUI solution "doing one thing well" is not really an option.
> When was the last time you saw an mobile app taking advantage of another one apart from tre camera? The only and most common time Android apps communicate is with Google Play Services.
I do this all the time when I use mobile payment apps. Website has a link that opens the app, I do my payment, back to the safari afterwards. It also works from within other apps.
It would have been more interesting to read your reaction to their answer to this concern, which is:
> We’ve only been testing this in beta in one country, so lots of people haven’t seen this yet and are imagining the worst. Don’t worry, it’s an opt-in feature, so if you don’t ever want to use payments in Signal, you never have to.
Of course it's opt in, it'd be patently absurd for it not to be. Nobody would use a chat app where some kind of weird crypto payments were mandatory. Advertising its opt-in nature as a feature is like advertising your cereal as asbestos free.
> Advertising its opt-in nature as a feature is like advertising your cereal as asbestos free.
I fail to see how, care to explain?
It's opt-in as any other feature which is not the core of the app. You don't have to send stickers or GIFs. If you don't want to receive messages at all, you shouldn't install Signal because it will be hard to avoid, it's a core feature, it's not really opt-in.
Except it's not enabled or visible by default. It will take the user navigating the settings to enable it. We all know non-tech users rarely if ever change default settings they don't understand.
"Bad guys" already use Signal to communicate and some countries try to ban encryption, I'm not sure much will change here.
Whether you should be able to transfer money in a private manner is a political choice. Signal is mostly showing that it's technically feasible. I don't see braving regulations to provide this feature to everyone, but time will tell.
But before integrating payments, Signal was not a good way for phishing/ransom. Look at all the scams and whatnot where people have to go and buy some kind of coupon and pass the codes to the scammers and whatnot...
Signals now integrates all of this right into the app.
Signal is still not a good way for phishing/ransom anyways.
Users would either have to already have the attacker in their contacts list or enable sealed sender. Enabling and funding a cryptocurrency wallet is going to be difficult. Even for WeChat who's payment service is popular it only captures 40% market share and as a result generally people are more educated about the risks.
Bad guys use WhatsApp to communicate but that's not given it a bad image, in fact just the opposite. When it was revealed that WhatsApp encryption was used by terrorists in the UK and the government wanted a backdoor the image improved as more people learnt about it and learnt that it works.
I think it's a non-answer that doesn't need a new response. "You don't have to use it if you don't want to" doesn't address the GP's concern around recommending the app to people who might not know better.
So will their be a version of the app that doesn’t have payments built in at all? Because if not it will only be a matter of time before someone comes up with a playbook convincing nontechnical users they need to send mobile coin to them in order to keep using signal.
Even my non technical relatives know not to install another app that some stranger tells them they need. Trying to explain what cryptocurrency is and how not to fall into that trap if using signal sounds like a nightmare.
> someone comes up with a playbook convincing nontechnical users they need to send mobile coin to them in order to keep using signal.
This sounds pretty unlikely, as long as signal does not integrate a payment processor (and they've made no indication they will) the majority of users will not have enabled or funded their cryptocurrency wallet(s) (whichever cryptocurrency they settle on).
Funding MobileCoin requires steps of non insignificant difficulty, not to mention Signal's trust model of using your contacts by default.
If I wanted to use the external money app they're piggybacking on, I can use that. I don't need it to be all one app. I have a web browser app for all-in-one app when I want that.
Yeah, you get to choose if you're the one sending the money. But sometimes people who want to send you money think that they're being helpful and find you on Venmo before you've had the opportunity to talk about payment privacy.
If you're using a privacy focused app, it should guide you towards defaults that maintain that level of privacy. Explicitly choosing a medium that has different privacy profile should be non-default behavior.
Letting people who don't want to think about it say "good-enough-for-signal-is-good-enough-for-me" and use the built in wallet is totally in line with Signal's mission.
I somewhat disagree. Sometimes I need to send payments internationally; in the US most chat apps allow for this. Or people use CashApp/PayPal. Sometimes I'm chatting with friends outside of the US and the choices to send money are very limited and problematic (e.g.: Argentina inflation, low PayPal adoption outside US and I think CashApp isn't available)
I don't know the specifics of the cryptocurrency being used, but adding the ability to send money is welcome
That list is global, and the US list[0] seems weird, but I'll go over some apps that are and aren't on the list:
FB Messenger (#1): looks like it does
Snapchat (#2): did, but killed it in 2018. Don't think it ever had significant traction
WhatsApp (#3), Instagram (not listed, probably because it isn't primarily a messenger, but from personal experience it is commonly used as one): nope, but might be getting it soon[1]
Messenger by Google (#4): looks like it does from their website, but I don't use Android
Discord (#5): nope
iMessage (not listed, but hard to believe that's correct): does, via Apple Cash
So yes, messengers with send-money features are fairly common in the US. That being said, at least in my experience (college age, PNW) nobody uses them—we use use dedicated apps like Cash and Venmo.
Yeah in the US CashApp/Zelle/PayPal works great. FB/Apple/Google messenger apps support this but adoption is relatively low especially compared to something like WeChat
> having yet another weird cryptocurrency is not the right solution though.
Maybe we disagree on the problem. From the US one of the most convenient solutions is Xoom; in my experience the turnaround is around 24-48 hours depending on the country and institution that's receiving funds. First there is a transaction fee, I usually pay $3 - this seems to be flat so 3% if I'm sending $100 and 1% if I'm sending $300 (I've sent $300 maybe once, more commonly I need to send <$100). Then they double dip by using a favorable exchange rate. I would be surprised if we can't do this better with crypto (note I am not a huge crypto supporter in its current state)
How are you going to a cash a crypto whose value is very volatile, like unless you cash out immediately its value in "real money" is in loss or is much higher?
Over time the standard expectation for a chat app has become send text + online status + image + gifs + video + link previews + typing indicators + @ mentions + emoji reactions + stickers
Fundamentally I don't see why adding "send money" violates it being just a chat app.
You're right, chat apps have evolved. That's the problem; Signal is good, but it's not the best. I wish it'd focus on matching or overtaking WhatsApp feature-wise rather than getting distracted 10 meters from the finish line.
When I'm trying to convince people to switch, privacy isn't the main draw, but if the features they care about are there, then privacy can push them over the edge to switch. I view this foray into payments as a sign that Signal feels its already "good enough" in the chat app department and will be spending its effort elsewhere.
Learn from SnapChat: if you're going to shoot the king, don't miss.
I think signal is and have been very clear that they won't remain "just a chat app". I don't have anything against cryptocurrency but I'm taking this as an opportunity to evaluate my alternatives.
I'll not be using this cryptocurrency, but whether I continue to use Signal seems to be down to how much effort I have to put into trying to explain away the apparent conflicts of interest here. They certainly don't seem to be putting any effort in. "hey, relax, guy!" is not an explanation. They seem to be happily spending the Foundation's credibility on this though, so I guess the clock has started.
In all of the previous discussions, josh2600 has very pointedly avoided answering the question of what financial interest Moxie has in the MobileCoin companies. He's only said that Moxie doesn't personally own any of the currency, without saying whether he has any financial interest in the company that owns most of the coins. This does not engender trust.
I had a look to Element after seeing it mentioned here multiple times. Sadly it' is too complicated for me to ask my friends and my family to switch to it. Signal was just so simple to use in comparison. Here even the name, Element/Matrix, needs explaining. Matrix is much more that a chat app, it's too much to be a Signal or Whatsapp replacement.
Element's security UX is a disaster. They either have no UX team whatsoever or the team they do have are incompetent. Average users have no idea what it means to "verify" another user and the UX is baffling to them.
Engineers are running the show, and poisoning the UX so that only other engineers know what the hell is going on.
Explaining federation (it's just like email, but we put the @ at the front and a : between uncertain nods) and key management, especially with multiple devices is the hard part.
This is just such a staring, atypical comment of someone who has spent their entire career as a technical bod, and hasn't the faintest idea how an ordinary person uses technology.
This forced integration is the worst decision Signal ever made (assuming they're sincere in their attempt to remove phone numbers as IDs).
If we really need a payment system, why not use GNU Taler? It's not a coin but just a distributed way to move real currencies around. Also, it does not run afoul or taxing and does not allow pump and dump or price speculation. (maybe this question just became rhetoric)
> Oh, something it does very well is to waste energy.
That's not the case for MobileCoin though. Energy waste does not seem to be direct a requirement by Signal to integrate a cryptocurrency, but the user friendliness and the fast transaction validation make it hard for a good candidate to be wasteful (there's only so much energy you can waste if your transaction is validated within 5s).
> Yep. GNU Taler should be enough for all needs of a decentralized payment system.
Not really. Unfortunately GNU Taler has distinct customer/merchant accounts so it is more alternative to specialized service-payment systems like visa/mastercard, than to general peer-to-peer payment systems like bank accounts.
Exchanges go down for a reason. If you don't want to be in it, you put yourself outside of the national economic scheme.
I can see the reason why, but if everybody does the same then the whole economy goes "informal" and you deprive the state from any income.
That what is happening in most West African countries (95% of the economy is in the "informal") and for exactly the same reasons (No trust in the state and want to avoid taxes. And note that money devaluation because of money printing is another form of taxation, with delaying time effects.)
And the net effect in those African countries is that you cannot even enforce the law, there isn't at all any budget for anything. If you're robbed then you will have to pay the police yourself in order to have them do the work to catch the culprit and find your stolen goods.
>>tax evasion and illegality hiding (which it isn't even good at).
This is just a Big Brother smear against privacy, with a socialist twist emanating from those with a financial stake in empowering the state and its dependent industries over the private citizen.
Exactly your arguments are made in the campaign to criminalize the use of cash:
Credit card company representative's statement on it in 2014:
>There's huge interest in cryptocurrencies and what perhaps they can create in the market place. Now we at MasterCard are not completely comfortable with the idea of cryptocurrencies largely because they go against the whole principle that we've established our business on which is really moving to a world beyond cash and ensuring greater transparency.. If you think about it, cash is a problem for a number of countries. Cash really facilitates anonymity, it facilitates illegal activity, it facilitates tax avoidance and a range of other things that aren't going to drive efficiency in an economy
Or it could have just been Monero, which is the most common privacy coin. The fact that they went with some no-name premined shitcoin is mind boggling and screams money grab.
The article directly addresses this with it's list of requirements. Perhaps another privacy coin like Grin would be a better suggestion that at least fits most of their requirements.
A common trick in government is to identify the preferred solution first, and then reverse engineer a set of requirements only met by that one single solution.
I presume the real unstated requirement boils down to "Moxie is associated with the cryptocurrency." Not disclosed is whether he or Signal have financial interests in its adoption (they have said they don't "hold" any of these pre-mined coins, but that's all they'll say).
Taler is not private at all. It gives the government a backdoor, like the old Clipper chip that some in the government wanted to put in processors to decrypt communications.
I don’t use Signal, nor do I really know much about this situation. But on a quick glance, it sort of reminds me when Keybase added Stellar Lumens wallets.
Of course, a lot of the friction with Keybase & Stellar was due to the magic ‘airdrop’ of coins, and all the craziness & flood out outsiders not interested in the Keybase mission itself.
But, the part that stands out to be, is many of the long time users or ‘die hards’ being very vocal about their distaste for the move. They say it doesn’t fit here, or ‘we don’t need this’, or whatever.
But the way I see it, who really cares? Some people will use it, some will ignore it. But if you’re a dedicated Signal user, and you don’t need or want this, why can’t you just keep using Signal the way you are now and not let it affect you?
Why does everything have to be some big philosophical nightmare when a feature you don’t care about gets added?
Trust. No one's judgement will be impaired by bolting a GIF pack onto a messaging app. VC-backed crypto wants a seat at the table and want you--exclusively--to facilitate the market for the coin? Different story maybe? Can you make the same impartial decisions regarding integration when you are not impartial? (Well, as far as we can divine from the various allusions, hints and allegations .. I mean even needing to ask these questions is weird.)
Trust in regards to what? It’s an encrypted messaging app. I presume that’s why you, or any other user has chosen it. You trust your messages are secure, and nobody unintended can read them.
What are you suggesting? Are you afraid they will give a back-door to the VC backed crypto vendor? Because my point is, unless you think somehow adding a crypto wallet to some obscure coin is going to jeopardize the security of you messages, I just don’t get it.
Just pretend like it’s not there, and keep using it the way you use it. That’s what I did with Keybase. Yeah there is stellar wallet sitting there that I never click on, but I’m still a happy user.
I’m just not interested in sitting around and fuming about business practices I have no idea about. They are a big company, and in this world all companies have to ’grow’ year in and year out. Yeah maybe it’s misguided, but I think it’s wasted energy to sit around and be outraged over how some company decides to run their business.
And if it is so outrageous, then find an alternative. It’s just so exhausting to read comment after comment of people who think they know better than the people who created the thing. It’s there business they can do what they want with it.
At some level you always have to trust whomever is vending the software you use.
If you don't audit and re-audit every bit of code in the whole stack for only alternative, as flawed as it is, is doing calculus based upon the reputation and character of the people producing the code. We differ in that I stopped using keybase when the stellar airdrop occurred. That company is now an appendage of Zoom, another company I've watched closely from a security point of view. I imagine you are also a happy user of that, whereas I'm a begruding/throw-away-laptop-under-duress user. I haven't seen the code from either product but have made a judgement based upon their behaviour.
This is the topic of this debate. If you find it exhausting reading comments from people trying to explain why they might be losing trust in a piece of trusted software, you are free to not read the comments and spend more time auditing code.
ps. There are literally thousands of encrypted messaging apps. That Signal claims to be another is a small differentiator. How does it back up the claim? These lines of reasoning always lead back to the people running the show and how they behave. Short of a State actor using gagging orders to insert back-doors, which is way outside at least my thread model, I moved to Signal because of its claims plus its aggregate reputation.
I’ve never touched Zoom and nor will I. Thanks for the rude assumption though, you can jump off that tall horse.
I don’t use Keybase much anymore but for some fun stuff. I still find the the file system useful.
Sounds like you will be quitting Signal soon too. Time to spend more time & energy researching which company to jump to next, splitting hairs, agonizing over business practices. Reading blogs & Twitter feeds of company officers and forcing opinions of them. Until 6 months later they do something egregious, and you have to start all over.
My main avenue for anything secure now is self hosted Matrix Synapse server. I’m in full control, and I don’t have to waste energy and mental cycles on getting mad about how other people run their business and stirring up outrage in forums.
It’s fantastic, low effort and low stress :) I’ve gone down the rabbit hole you describe before, I don’t need a lecture on it. But I decided it’s not worth it.
I believe I am happier by skipping all the stuff you’re taking about. Which was really my main point, I didn’t really say it very well though.
Isn't the biggest question: Why not a different app with some sort of signal integration? If that takes off and is successful, it could eventually be merged to be one application I suppose. But leveraging a huge user base from Signal (a messaging app with a sales pitch of a certain purity and no bs attitude to the problem at hand) to push a cryptocurrency payment system?
Don't tell me anyone involved in doing this felt like this was 'the right way to go'. Which makes exact motivation behind it all the more questionable.
> But leveraging a huge user base from Signal (a messaging app with a sales pitch of a certain purity and no bs attitude to the problem at hand) to push a cryptocurrency payment system?
> Don't tell me anyone involved in doing this felt like this was 'the right way to go'. Which makes exact motivation behind it all the more questionable.
If this feature is to stay relevant, it has to be integrated within Signal. Otherwise competitors (who do integrate a payment feature) will just have a better UX.
I don't think that's honest. Signal has the reach to get plenty of beta-testers on board, enough to maybe grow it from there. I'm not saying that it isn't tougher to do this way, but it's not like a "Signal Payments" App with a similar Logo by the same outfit trusted by many people for secure messaging already, starts at absolute zero. Plenty of outfits would kill for the Signal IP to create something like a payments app.
> Signal has the reach to get plenty of beta-testers on board, enough to maybe grow it from there.
I think we need a reality check here. When I check the Playstore, Signal has 50M downloads. WhatsApp has 2B. Signal is still largely the underdog.
I could definitely imagine a few people using a "Signal Payments" app instead of whatever WA offers. But to actually compete with WhatsApp (which won't create a separate app), you can't afford to split the app in two. The aim is not that HN users are able to transfer money in a privacy-preserving way, it's that everybody can.
If the illusion is that it's Signal's ultimate goal to dethrone WhatsApp (and Paypal for payments?), I think I'm not the one in need of a reality check (forgive the provocative wording, I have no ill will towards you).
Signal's (meaning the app) goal should be to be a long-term, secure, honest alternative for more privacy minded users, no matter their technical expertise? At least that's what I'm thinking.
I see it more like setting the baseline for the whole ecosystem. If Signal allows me to do X privately, why can't WhatsApp? To have this clout, they need to keep a non negligible market share and remain a threat to other messengers, which you can't do if you miss features your competitors have and that users value.
> It currently requires a wire transfer for people in the UK to get funds in and out
Did it appear to these clowns that if I have to use a wire transfer anyway, I can just use a fucking wire transfer?
The best part about this is that besides all the obvious criticism for hooking up your chat app to a pump&dump cryptocurrency scam, the cryptocurrency is also just a legitimately terrible way to implement this feature. Manual wire transfers? 50p per transaction? Fucking price volatility?
> Did it appear to these clowns that if I have to use a wire transfer anyway, I can just use a fucking wire transfer?
You may have misunderstood what they're saying. The full sentence from which you quoted:
> It currently requires a wire transfer for people in the UK to get funds in and out of cryptocurrency exchanges that support MobileCoin, which costs money.
They're saying that you need a wire transfer to buy and sell MobileCoin using the currently-available exchanges. Once you possess MobileCoin, you can then send or receive it using the app without further wire transfers unless you choose to cash out. A wire transfer isn't necessary for a transaction in Signal.
No, I did not misunderstand at all. I care about solving my problem which presumably is sending money to my buddy in the easiest, most straightforward way. That is what a solution is going to be measured on.
(Hint: you can just give people contingents of your make-believe currency. But it's a better scam if they wire transfer money for it!)
You have a point in the case of a volatile cryptocurrency: if 1 MOB is worth USD 10 one day and USD 1 the next, nobody will want to keep their MOB, so you have one bank transfer for one MOB transfer. It sucks.
If MOB becomes less volatile over time, you could imagine people having USD 100 in MOB that they would trade for small debts, and they could be fine leaving this sum in MOB. In this case, you'd have several MOB transfers for just a few bank transfers, and it'd be an improvement.
How stable they'll manage to make it, frankly I can't say, I believe it's still an open problem for them.
> In this case, you'd have several MOB transfers for just a few bank transfers, and it'd be an improvement.
It'd be less inconvenient that a worse cryptocurrency, but more inconvenient than hitting a button in your bank app (the uk has instant transfers already).
These are standard things people have when they are savvy enough to own a mobile phone. In UK/EU they don't solve a problem tiny bit but rather make it more risky because of volatility and more difficult abs expensive to cash out.
I should have been clearer with the IBAN point. In particular I was not talking about people outside of the banking system. I'll respond here to most replies I got so far.
What I meant is that you need the IBAN of the person you want to send money to (of course you need to have an IBAN, as in, you need a bank account for your MOB to be actually worth anything). Assuming Alice and Bob are contacts on Signal, and Alice wants to send money to Bob, Alice still has to ask for Bob's IBAN. We can safely assume that Bob does not know his IBAN by heart, and has to use his ebanking app (for instance).
You already have some kind of identifier for Bob, Signal would allow you to reuse it. Some ebanking apps already allow you to do that, but I think in most cases both have to be clients at the same bank (?)
The idea is that you have less friction. The chat would be something like:
> B: can you send me 5 USD
> A: sure, here it is
> A sent you N MOB, equivalent to 5 USD.
Of course the UX is still far from being there (volatility is the biggest problem I think).
>"Did it appear to these clowns that if I have to use a wire transfer anyway, I can just use a _____ wire transfer?"
Yeah, it clearly did and they didn't like that you and everyone else doing that now has their transactions tracked. They know X paid Y an amount of $Z. They want you and everyone else to be able to transfer without anyone knowing to who. Just like using cash money in a shop (withdraw, transfer to Y, Y deposits in their bank and your banks know nothing as opposed to a direct deposit from X to Y where your banks know precisely when and who is on either end of the transfer).
Yes, as they note their current solution has issues. Transaction fees are too high. Volatility is a problem for any currency used as a medium of exchange absolutely.
So what is this? A start that can be improved on. If you want your transaction to be secret from your banks and those your banks share info with a wire transfer is probably not an improvement.
Might not work at all. Might have other issues as yet undreamed of. We'll see. Given I don't ever have to use this and Moxie has earned a reputation of not being neither crook nor zuck I'm kinda happy to watch and see what happens.
Immense amount of "Signal is terrible" on this site which doesn't make much sense to me.
> Volatility is a problem for any currency used as a medium of exchange absolutely.
Volatility is not an issue for any major world currency (USD, Euro, Yen, etc). If I pay the bill at a restaurant and ask my friends to repay me on Venmo, the money I receive is worth exactly the same when it hits my bank account a few days later as when the bill was paid. Perhaps you could argue it changed by 0.01% or something due to inflation, but cryptocurrencies can easily change by several percent per day.
The smaller the level of volatility the smaller the problem. Cash in USD is good enough, not so long ago (still? I haven't kept up) cash is not at all good enough in Zimbabwe (unless you use a foreign currency like e.g. USD).
Volatility doesn't have to be an issue with a cryptocurrency tokens either, there are plenty of stablecoins backed by currencies and plenty of algorithmic stablecoins backed by other cryptocurrencies. At the moment the majority of these exist in public blockchains.
There are plenty of models that facilitate the same privacy guarentees for stablecoins.
279 comments
[ 3.5 ms ] story [ 158 ms ] thread(https://www.coindesk.com/signal-founder-may-have-been-more-t...)
- Not be MobileCoin or any small-cap coin - Support Bitcoin/Litecoin/Etherum/other popular and trusted coins - Sync private keys using the same mechanism as messages
Signal has had some questionable choices in the past, but this is over the line for their goal of privacy/security/trust. MobileCoin does not belong in Signal.
Why not?
> - Support Bitcoin/Litecoin/Etherum/other popular and trusted coins
The post explains their requirements which these cryptocurrencies don't fit. Do you take issue with their requirements?
> Sync private keys using the same mechanism as messages
AFAIU it's non-custodial and it stays on the mobile client, meaning that there's no synchronization so far (the desktop client does not support these features). This could come eventually, but it's part of their requirements to stay out of the way and let the user handle their coins without trusting Signal.
> this is over the line for their goal of privacy/security
How so?
Because the price of small cap coins is insanely volatile, and even more subject to manipulation than cryptocurrencies in general. Mobilecoin's price changed by 1000% over the course of a couple weeks last month.
The future volatility of MobileCoin is to be seen. Past performance is not indicative of future performance and whatnot.
Wether they should have used a test net, MobileCoin should have only released a limited portion of the coins or whatnot is another question entirely.
It's not even really used right now, it's hard to tell how much it reflects what will happen later.
With a centralized cryptocurrency there's a lot they could do to make it less volatile, and it's still to be seen what will happen in practice. It's a hard problem, but I don't think we can easily conclude that they will fail, or that a better solution already exists.
The goal is to transmit money through a mobile messaging app. If the MobileCoin wants to take donations to support the platform, or even wants to take a tiny cut of each transaction, that seems fine. But I see no justification for their platform to be based around a volatile speculative asset which generally serves no purpose but to create a new gambling market and enrich the founders.
A mobile-friendly alternative to Monero seems like a really cool, valuable idea. But I don't think it's acceptable that it's both a volatile security to speculate on and the payment system for a supposedly non-profit privacy-and-freedom-oriented messaging app.
The problem isn't cryptocurrency; it's penny stocks and all the zero-sum bullshit that comes with them. You don't have to make your new cryptocurrency a penny stock if you don't want to. Here, it seems they probably want to.
Stablecoin mechanisms have tradeoffs whether that's being on a public blockchain, a centralised party, collateral risk or lack of privacy. Monero is the current gold standard when it comes to privacy but trades off speed (confirmation blocks), mobile friendliness and a volatile price. On the other end of the spectrum Tether is very stable but is produced by a centralised entity and is on a public blockchain.
From Moxie's 2017 interview (https://www.wired.com/story/mobilecoin-cryptocurrency/) we can safely assume that their list of requirements existed from the start (MobileCoin didn't have much to show at this point). Since then it's been public knowledge and since the market cap of MobileCoin is dictated by the market so I'm not sure about your penny stock comment, it seems more sensible to direct criticism at their lack of distribution transparency.
As for the conflict of interest, Moxie appears to (currently) have a "name your price" reputation so he could have chosen any cryptocurrency and they'd probably pay him the same advisor fee. When he says that he chose/founded MobileCoin because in his opinion it's the best (in his value system), I actually believe him.
Do you have any source for this?
That’s kind of interesting, cheap fast transactions, not proof of work, and only the validators have the SGX burden (Secret network does something like this with SGX for private-ish smart contract execution)
So we dont like the premine and the forced integration and pump, which is meh to me, everything is premined these days I cant care much about that.
I’m actually surprised it has some cool technology involved, most “privacy” coins dont pass the smell test and with a name like MobileCoin I just assumed the worst, but I still have to laugh that the purchasers had to do KYC then.
Oh crypto.
Its pretty clear that they omit some information to give people less to disagree with. They pump it and sell, thats going to happen. I don’t care much about that either, speculators are going to get sold into, that’s not even controversial.
The Signal forced integration is grimy.
I still wish there was a stable privacy coin. USDC and DAI on Tornado.cash is okay, but too few inputs to mix with. Mobilecoin doesnt solve that, just another volatile asset.
"SGX is a pile of hacks in a trenchcoat pretending to be a secure enclave" --- paraphrasing the only correct summary of this technology.
Partisia[2] (currently in beta) and Tari[3] could provide something similar.
[0] https://scrt.network/blog/secret-network-ecosystem-update-ja...
[1] https://github.com/SecretFoundation/SNIPs/blob/master/SNIP-2...
[2] https://partisiablockchain.com/#/
[3] https://www.tari.com/
I think by being SNIP-20 they would hide the amounts by nature of the private smart contract execution but would still show the sending address, perhaps the receiving address would be hidden as well due to the private smart contract execution.
I haven't used it yet because I havent acquired any SCRT for the transaction fees on that blockchain, but any variable should be hidden for a smart contract (of which tokens are), while the initiating address writing to the blockchain would by visible for consensus purposes and state management.
I’ll give it a whirl.
I'd rather them have done _nothing_ at all.
Oh well.. further proof you really need federation.
more like: open protocols for certain interactions, irrespective of the app that implements it.
Plus, an open protocol changes the risk calculus for the group that manages the client implementation, in a way that would prevent situations like this one.
However, open protocols beget federation, so I don't think you're at odds with the above poster. Email, DNS, etc are all open protocols with federation built-in, but we trade away some centralization of servers (GMail, Cloudflare, etc) in exchange for nice things (DoS protection, spam filtering, etc).
In the worst case, where a server starts acting scammy (like embedding ads in your email) or tries to diverge from the protocol, you can always go back to hosting it yourself, or paying a small and trusted shop to host it for you.
In the arena where Signal is competing, Matrix [1] is probably our best bet. (Assuming irc is too barebones for your needs, in 2021). It has also supported end-to-end encryption for some time now [2].
[1]: https://matrix.org/docs/spec/
[2]: https://matrix.org/faq/#which-matrix-clients-support-e2e
For example, Let's Encrypt reliably, like clockwork, distributes certificates and maintains related PKI infrastructure. That is what Signal was supposed to be (at least, my interpretation based on their PR) with regards to secure messaging, and they have utterly failed to maintain the focus you'd expect of a non profit with their mission.
If I want payments (unregulated payments at that), I would use and donate to a payment app, not a messaging app. But heh, report it to regulators and let them be the bullwhip to Signal and their poor choices if they ignore the community (who are their stakeholders as a non profit entity). Of all the ways to kill your project, this doesn't seem like the "hill to die on." Don't drag secure messaging into your fight against nation state currency regulations, and have some common sense about compartmentalizing around regulatory risk.
This is exactly what Signal had, until the leadership changed their focus onto more lucrative prizes.
I'm not sure if I understood it correctly, but isn't a major selling point of cryptocurrencies is the anonymity/untraceability?
Let's Encrypt doesn't have a reason to try to blockchain their certs because their bills are being paid. Signal clearly wants more money (they openly state that the coin will pay $1m/yr to Signal).
And will remain so forever. Which is not realistic.
the PIN & cloud features are explicitly designed to facilitate breaking the phone number requirement.
Signal, your bias is showing, and it makes me wonder what other vendors will get your ear and be integrated in the future.
The "vendor" in this case is the creator of Signal. The rabbit hole runs very deep on this situation.
https://www.coindesk.com/signal-founder-may-have-been-more-t...
This explains the issues fairly well. tl;dr most blockchains require a CPU and/or network expensive sync which is prohibitive on mobile. As a fix/hack many web and mobile apps have a SPOF gateway which the client must trust absolutely.
In the context of a cryptocurrency like bitcoin you also have to trust the server you’re talking to, if you’re a light client (a client that doesn’t want to download the whole history). So Bitcoin is not a great choice for mobile clients that don’t want to have to trust another third party. Which in general is the threat model of Signal.
Now fast transactions (finality) is an upside for any type of currency really.
In addition to the conflict of interest Moxie has (and, honestly, I can see that side -- of course he'd want to be involved in the cryptographic design of a privacy-preserving payment system -- but he still needs to come clean about his relationship with MobileCoin), the most disturbing thing to me remains that the source to the server wasn't publicly updated for nearly a year while they added this feature, the timing of when the source went dark clearly indicates that specific intent, and Moxie's statement as recently as January that they didn't have specific plans to add payment/cryptocurrency when it's clear from the server source that they had been working on it for many, many months at that time.
As usual, it's not the crime, it's the coverup.
What lack of transparency do people feel is missing (beyond the server source not being updated - I agree that's a big miss)?
"Marlinspike played down the potential of crypto payments in Signal, saying only that the company had done some “design explorations” around the idea. But significant engineering resources have been devoted to developing MobileCoin integrations in recent quarters, former employees said."
January 25th, 2021
https://www.theverge.com/22249391/signal-app-abuse-messaging...
For any other company, if they were downplaying a product launch for timing/perception/etc reasons, nobody would bat an eye.
May have been more than an advisor.
It would be an enormous conflict of interest if Moxie had a financial stake in MobileCoin, and then drove signal to adopt this random crap coin.
These guys keep on claiming just to be technical advisors with no financial interest or benefit from mobilecoin. BS.
Let's get some auditors into Moxies / Signal Foundation stuff, figure out how this decision was made, if signal foundation received fair value for pushing their users this way etc etc.
I got voted down before for saying this, but will keep on saying it. You can't use a charity and then leverage that charitys assets to enrich yourself outside of the charity.
What's interesting is despite all the claims of "trust" and "security" vs using google etc these guys turn out to be what appears to be scammers.
I've uninstalled signal - you should too.
Signal Messenger LLC isn't.
"Signal Messenger LLC. was founded simultaneously with the Signal Technology Foundation and operates as its subsidiary. Its CEO is Moxie Marlinspike and it is responsible for the development of the Signal messaging app and the Signal Protocol."
https://en.wikipedia.org/wiki/Signal_Foundation
These single member LLC's are considered disregarded entities in most cases. Many nonprofits use LLC's to own property, do app development etc for liability reasons. That doesn't obviate their need to act in a manner consistent with their parent entities objectives and public purpose.
This is the one thing putting me off, I want my chats on my device not on machine I don't own or have access to.
- Moxie's involvement with MobileCoin (could be as simple as saying: "for the same reasons Signal's interested in MobileCoin, moxie is as well").
- The concerns about regulatory risks/attention involved with a cryptocurrency integration.
- Why it involved hiding the server source code.
The idea of privacy-friendly transactions easily available within an app I'm already using is attractive, but I very much hope the obvious concerns won't play out in practice (which time will tell), and it would be good if they'd also addressed the above.
My guess: to reduce the noise and speculation. Much better to deal with it now that there's something to be gained (feedback from beta testers and actual deployment). There was little to gain before, since the server accepts very few contributions anyway.
I wander enough on GH to see how much time big open-source project maintainers spend addressing toxic comments. Open-source is nice when you get relevant contributions and constructive feedback, but it's really not free, you have to deal with all the rest as well.
Is there some law that states a project must publish X code changes in Y timespan?
For the vast majority of people, OSS in 2021 means having a public repo hosted somewhere that all commits are pushed to, or PRs are made to. Periodically updating a public repo with changes made to a private repo is not really what people have in mind.
That's like requiring a developer to push their local changes hourly/daily for a task that's been committed to but not completed.
When you're using a product for which you can't get the source code, the product is not open source.
Commits: https://github.com/signalapp/Signal-Server/commits/master No push between: April 20, 2020 and April 6, 2021.
You can't say affirmatively that yes they deployed but then say it's an assumption.
Either they did or they didn't.
If they didn't deploy the code to production prior to the commit then I see no problem with what they did.
There's no good option here.
The readme.md on the repo doesn't really clarify one way or another on the matter.
Why?
> I can't say affirmatively that anyone is running anything exactly
Signal provides a means for reproducing Android builds so you can affirmatively determine what you're running.
https://signal.org/blog/reproducible-android/
> but they now claim they did.
Signal claims they shipped server updates without releasing code? Do you have a link to that?
When others were complaining about the lack of an update to server, they're complaining about the client and server APIs being out of sync. Reading through these comments, I don't get the impression that the server code published is what's actually running. In fact the following comment even refers to it as a reference implementation:
https://github.com/signalapp/Signal-Server/commit/3432529f9c...
At the end of the day, it doesn't really matter much what server code is running since the Clients manage encryption and the Server has no insight into the messages being exchanged.
You can't sue the copyright holder for infringing their own copyright.
To be open source, you need to publish the source of applications you run. It's as simple as that: "we developed this app, and it's running on our servers, and the source can be found here".
They kept updating their server app for a year, without publishing their source. This is not open source. Signal server code was not open source for a year.
If so, then the code quite simply is not open source by any possible definition. I agree with you that a project that is dormant, or even receiving internal development that is still under review, can defensibly be called "open source" even if the development isn't happening in the open. (For instance, your favorite begrudgingly-GPL-compliant hardware vendor who releases .zip files every time they release a new product is releasing "open source" code.) But if the source code to the Signal server isn't even published, it can't be open.
- the open-source argument was mostly meant for everyone to look at the sources and draw their conclusions regarding privacy and security
- these guarantees are mostly client-side (and you can't check what's running on the server anyway, even with the code)
It's fair to say that the server code was proprietary for one year. Most of their code was still open-source during that time, and most of it (now that they push to the server repo as well) is now.
I feel they would have taken less flak over this if their server code had never been open-source to begin with, or if they just released it now.
Why do you think more transparency would lead to noise and speculation? Exactly the opposite is the case. They could have gone the open route and maybe even gotten help from the community at implementing their payment feature.
But the way they did it they left everyone wondering whether their server is now spyware or what other reasons there could be for them to not update the public repo.
Because of the current situation: people argue about whether Moxie lost it, if Signal is still the right solution, etc.
If the feature had been implemented in the open, this debate would have taken place since the beginning, again with little benefit.
> maybe even gotten help from the community at implementing their payment feature.
Signal does not have an open development model. They're a small team, and most things beyond bug fixes are done by them. You can debate whether that's the most efficient approach, I'll just say it's an open question, and that's the model right now. So contributions to this brand new feature by the community would not have been possible.
> But the way they did it they left everyone wondering whether their server is now spyware
If people misunderstand that most of the security guarantees come from the clients, there's little an up-to-date repository on GitHub can do. I think the noise and complaining that has been happening for one year about the closed-source server is still negligible to what's happening now.
I would have preferred if they had kept it open, but I can definitely understand why they thought it was a better course of action.
It isn't known how much of it was premined, and from an early version of their whitepaper, the founders might have as much as 80% of the total supply of the coin. This isn't fine for a cryptocurrency which aims to be "an alternative payments infrastructure", and it isn't fine for Signal to try to promote them as such.
The details of the distribution are lacking but as a beta it meets the experience they're going for - it's not as if they'd choose something that doesn't meet their requirements for the beta.
At least AFAIK. There's a ton of alt coins so I might have missed something.
Their "privacy" is strongly based on the confidentiality of SGX. If you're willing to trust SGX for your confidentiality and security, as they have, they could use any cryptocurrency in a highly private and instant manner.
E.g. via an implementation of the moneypot server in SGX: https://bitcointalk.org/index.php?topic=5302025.0
MOB is transparently a scheme to generate a windfall from shoving a pre-mined coin into a mass-market application. One could debate the ethics of that with a straight face, I suppose, but to argue that it is anything but is just dishonest.
The client fully identifies itself and its keys to the server, the wallet is entirely implemented server side. Without SGX there is no privacy what-so-ever.
Usage of ringct is incidental. It's like claiming that your documents are private when your operating system submits them all to the NSA because the NSA encrypts them after receiving them. :) (and, of course, we trust the NSA to behave honestly...)
This is a very limited threat model and worthy of serious scrutiny.
Lightning transactions are ephemeral: once the transaction happens, _no_ data about the transaction actually needs to be kept by anyone, let alone on a public blockchain. And only the peers directly involved in the route ever learn about the transaction directly.
Whereas with SGX, if SGX is broken in the future - and it will be - the statistical analysis on the underlying blockchain data is still possible. And unlike MobileCoin, this design wouldn't put SGX in any kind of trust or custodial position at all: if SGX failed, you'd just close the Lightning channels the same way any other Lightning implementation would, and open new channels with non-SGX peers.
I'm trusting their whitepaper but it looks to me that fog provides similar security guarentees between MyMonero (shared view key) and other light wallets (computation on device).
I don't see how the privacy could be any worse than MyMonero even if SGX was compromised.
https://www.coindesk.com/signal-founder-may-have-been-more-t...
The thing that gets me the most though is not what they are doing, it's the way they are going about it.
The leader of a privacy focused app is now hiding secrets from everyone about the technology he convinced people was safe.
I've had to write off signal for this reason alone. I mean the only reason I ever used the app was trust.
At best we know that he (claims to) have no coins. But that he was an advisor for them and focused on what he saw as a problem with crypto payments: speed. But yeah, there are still a lot of open questions here.
> The concerns about regulatory risks/attention involved with a cryptocurrency integration.
They addressed this before and the code reflects it. They whitelist country codes that allow it.
> Why it involved hiding the server source code.
This was weird and I'd like it addressed but probably not relevant to this particular topic/post.
> The idea of privacy-friendly transactions easily available within an app I'm already using is attractive,
Same. I mean it is a core element of the cyperpunk manifesto[0]. But I don't want to use a payment system that is volatile. If I have to choose to be beholden to services that collect my data or use a currency that is volatile, I'm going with the former every time. This is the question that I would have liked to be further addressed.
[0]https://www.activism.net/cypherpunk/manifesto.html
Additional bonus, no electron based client, native apps for ios, Android, Web, Mac and even Linux.
If they can make the verification process for a new device smoother, I can recommend to folks. My worry is the amount of influence I used to get people to switch over to Signal only to ask them to switch again
The "Element" branded desktop apps are actually based on Electron, but since the underlying Matrix protocol is open, there are a plethora of fully native third party clients in varying stages of development.
If you don't like Electron, you're free to choose an alternative desktop client like Fractal (https://wiki.gnome.org/Apps/Fractal) or NeoChat (https://invent.kde.org/network/neochat) or Nheko (https://github.com/Nheko-Reborn/nheko).
Or on the mobile side, FluffyChat (https://fluffychat.im/) and Nio (https://nio.chat/) are both solid alternatives.
If you're coming from IRC, there's a WeeChat plugin (https://github.com/poljar/weechat-matrix) or a standalone terminal client called Gomuks (https://github.com/tulir/gomuks).
It's still early days, but Element is genuinely committed to Matrix's success as an open protocol, and I find the community enthusiasm to be very encouraging.
And, are Nheko or Neochat mature enough for a daily driver? Lasy I saw they were very alpha.
Nheko is certainly usable as a daily driver. Haven't tried NeoChat yet, but it looks good. However, everyone's thresholds are different.
I have found instructions to reverse-proxy matrix service, which satisfies my need for a minimal cloud presence and private (behind enforced NAT) homeserver. Combined with p2p via SQLite dendrite, that might solve my whole problem. (Is Dendrite considered ready for personal use, e.g. p2p, even if not a replacement for Synapse? What should I watch out for?)
I have not found details about identity portability vs. Synapse version. Can identity be ported out of a Synapse 1.29 homeserver?
We always wish software was ready before it is.
And self-hosting Matrix is hard and requires pretty hefty hardware. If performance improves, it will certainly be a great option. For basic chats though, XMPP+OMEMO is still a really great lightweight option.
This is, however, something I also see with Signal. Texts can often take 5-6 seconds to deliver.
With that said, it's been disappointing to see how slow development has been on it. Hopefully it picks up and they can get it out of beta this year.
I think it would address some concerns, but personally, mixing concerns of secure messaging and cryptocurrency payments would still make me too uncomfortable.
[0]: https://news.ycombinator.com/item?id=19913496
It costs 1 SAT to send money over the Lightning Network, but you can't run a pump and dump on that so "MobileCoin" it is
If I understand correctly, Intel could (if compromised or untrustworthy):
* revoke any node's SGX keys - knocking any number of consensus nodes out at zero cost * create false attestations of what code was run (which would presumably be detectd eventually) * dominate the consensus mechanism with its hand-picked SGX nodes
Among other things, this means Intel could turn off the MobileCoin chain, if commanded to do so.
(I could be somewhat off on some of this – if so, corrections with explanations very welcome.)
So, if your threat model is "Intel Inc is always trustworthy & secure", Signal & MobileCoin are wonderful. If you have doubts about Intel's trustworthiness/security, the designed privacy properties start to degrade.
Nobody relies on it. But if we can make an attack 10 times more expensive (because we can't prevent it completely), why not do it?
Secure remote computation is better than nothing. I'd start having problem with it when people rely on it when there are better solutions, but that hasn't been the case so far, AFAICT.
WhatsApp management must be really happy with this sudden move from Signal. Signal has lots of detractors who would like to discredit it, and Moxie and co. just handed it on a platter to them.
That too was so mysterious and moxie never gave a proper explanation why it took them so long to recover the service.
100% this. I'm not a beta tester, but I am a signal user. I reeeally don't want to have to hedge my recommendation of signal because it's involved with some cryptocurrency BS. Please, just be a chat app.
Let the chat app be a chat app. Let the payment app be a payment app.
Or, to put it another way, do you recognize that a chat app and a payment app have different incentives? Combining them means now your chat app has payment app related incentives. Do you see this as a good thing? If so, why?
When was the last time you saw an mobile app taking advantage of another one apart from tre camera? The only and most common time Android apps communicate is with Google Play Services.
Context switching on mobile or GUIs in general also don't follow this principle. Modern GUIs integrate plenty of things (file explorer, image editor, basic camera, etc) becuase mobile package management doesn't resolve dependancies automatically or allow for a great deal of UI customisation. Especially in a messaging client imagine not being able to send photos, videos, audio, or files!c
GUIs are here to stay so until we figure out a composable and we'll adopted GUI solution "doing one thing well" is not really an option.
I do this all the time when I use mobile payment apps. Website has a link that opens the app, I do my payment, back to the safari afterwards. It also works from within other apps.
> We’ve only been testing this in beta in one country, so lots of people haven’t seen this yet and are imagining the worst. Don’t worry, it’s an opt-in feature, so if you don’t ever want to use payments in Signal, you never have to.
https://xkcd.com/641/
I fail to see how, care to explain?
It's opt-in as any other feature which is not the core of the app. You don't have to send stickers or GIFs. If you don't want to receive messages at all, you shouldn't install Signal because it will be hard to avoid, it's a core feature, it's not really opt-in.
b) opt-in features that are very profitable have a funny habit of transmorphing in to opt-out
"Bad guys" will use the anonymity of Signal to do the usual stuff: Phishing, collecting ransom etc. etc.
Signal will get a bad image, no matter whether it's opt-in or not.
Whether you should be able to transfer money in a private manner is a political choice. Signal is mostly showing that it's technically feasible. I don't see braving regulations to provide this feature to everyone, but time will tell.
Signals now integrates all of this right into the app.
That's much easier than before!
So... Big win... But for whom?
Users would either have to already have the attacker in their contacts list or enable sealed sender. Enabling and funding a cryptocurrency wallet is going to be difficult. Even for WeChat who's payment service is popular it only captures 40% market share and as a result generally people are more educated about the risks.
Even my non technical relatives know not to install another app that some stranger tells them they need. Trying to explain what cryptocurrency is and how not to fall into that trap if using signal sounds like a nightmare.
This sounds pretty unlikely, as long as signal does not integrate a payment processor (and they've made no indication they will) the majority of users will not have enabled or funded their cryptocurrency wallet(s) (whichever cryptocurrency they settle on).
Funding MobileCoin requires steps of non insignificant difficulty, not to mention Signal's trust model of using your contacts by default.
This seems like a natural next step to me.
If you're using a privacy focused app, it should guide you towards defaults that maintain that level of privacy. Explicitly choosing a medium that has different privacy profile should be non-default behavior.
Letting people who don't want to think about it say "good-enough-for-signal-is-good-enough-for-me" and use the built in wallet is totally in line with Signal's mission.
It's like providing an option to send links which will by default open in a tor browser.
I don't know the specifics of the cryptocurrency being used, but adding the ability to send money is welcome
and those would be? The top chat apps are: https://www.statista.com/statistics/258749/most-popular-glob...
FB Messenger (#1): looks like it does
Snapchat (#2): did, but killed it in 2018. Don't think it ever had significant traction
WhatsApp (#3), Instagram (not listed, probably because it isn't primarily a messenger, but from personal experience it is commonly used as one): nope, but might be getting it soon[1]
Messenger by Google (#4): looks like it does from their website, but I don't use Android
Discord (#5): nope
iMessage (not listed, but hard to believe that's correct): does, via Apple Cash
So yes, messengers with send-money features are fairly common in the US. That being said, at least in my experience (college age, PNW) nobody uses them—we use use dedicated apps like Cash and Venmo.
[0]: https://www.statista.com/statistics/350461/mobile-messenger-...
[1]: https://www.cnet.com/news/facebook-pay-will-let-you-send-pay...
As a European I have the opposite impression. Pretty much all online sellers I know that don't offer Paypal are in the US.
And sending money is one thing, having yet another weird cryptocurrency is not the right solution though.
Maybe we disagree on the problem. From the US one of the most convenient solutions is Xoom; in my experience the turnaround is around 24-48 hours depending on the country and institution that's receiving funds. First there is a transaction fee, I usually pay $3 - this seems to be flat so 3% if I'm sending $100 and 1% if I'm sending $300 (I've sent $300 maybe once, more commonly I need to send <$100). Then they double dip by using a favorable exchange rate. I would be surprised if we can't do this better with crypto (note I am not a huge crypto supporter in its current state)
Chat apps used to be just: send text.
Over time the standard expectation for a chat app has become send text + online status + image + gifs + video + link previews + typing indicators + @ mentions + emoji reactions + stickers
Fundamentally I don't see why adding "send money" violates it being just a chat app.
When I'm trying to convince people to switch, privacy isn't the main draw, but if the features they care about are there, then privacy can push them over the edge to switch. I view this foray into payments as a sign that Signal feels its already "good enough" in the chat app department and will be spending its effort elsewhere.
Learn from SnapChat: if you're going to shoot the king, don't miss.
Engineers are running the show, and poisoning the UX so that only other engineers know what the hell is going on.
Explaining federation (it's just like email, but we put the @ at the front and a : between uncertain nods) and key management, especially with multiple devices is the hard part.
The people are NEVER the problem.
If we really need a payment system, why not use GNU Taler? It's not a coin but just a distributed way to move real currencies around. Also, it does not run afoul or taxing and does not allow pump and dump or price speculation. (maybe this question just became rhetoric)
The whole need for cryptocurrencies is a dark area of tax evasion and illegality hiding (which it isn't even good at).
Oh, something it does very well is to waste energy [edit: actually it seems like MobileCoin is not that hungry, see children comments].
That's not the case for MobileCoin though. Energy waste does not seem to be direct a requirement by Signal to integrate a cryptocurrency, but the user friendliness and the fast transaction validation make it hard for a good candidate to be wasteful (there's only so much energy you can waste if your transaction is validated within 5s).
This way it seems like they can follow a better path (regarding energy) than the mainline coins like btc, that's a very good thing.
More details on that implementation here:
https://www.bfh.ch/de/aktuell/news/2020/gnu-taler-bfh/ https://archive.ph/3YxkK
Not really. Unfortunately GNU Taler has distinct customer/merchant accounts so it is more alternative to specialized service-payment systems like visa/mastercard, than to general peer-to-peer payment systems like bank accounts.
What is the problem then?
It would all be nicely wrapped in a fun and convenient app.
Having separate accounts allows you to immediately know how much tax you need to pay, it'll be just a fraction of your Rx account.
A large part of the reason why Bitcoin was created was to ensure that there was a digital solution for avoiding trusting the banking system
I can see the reason why, but if everybody does the same then the whole economy goes "informal" and you deprive the state from any income.
That what is happening in most West African countries (95% of the economy is in the "informal") and for exactly the same reasons (No trust in the state and want to avoid taxes. And note that money devaluation because of money printing is another form of taxation, with delaying time effects.)
And the net effect in those African countries is that you cannot even enforce the law, there isn't at all any budget for anything. If you're robbed then you will have to pay the police yourself in order to have them do the work to catch the culprit and find your stolen goods.
If everybody using cryptocurrencies is like you and is still paying taxes, then that's effectively one problem solved.
This is just a Big Brother smear against privacy, with a socialist twist emanating from those with a financial stake in empowering the state and its dependent industries over the private citizen.
Exactly your arguments are made in the campaign to criminalize the use of cash:
https://aeon.co/essays/if-plastic-replaces-cash-much-that-is...
Credit card company representative's statement on it in 2014:
>There's huge interest in cryptocurrencies and what perhaps they can create in the market place. Now we at MasterCard are not completely comfortable with the idea of cryptocurrencies largely because they go against the whole principle that we've established our business on which is really moving to a world beyond cash and ensuring greater transparency.. If you think about it, cash is a problem for a number of countries. Cash really facilitates anonymity, it facilitates illegal activity, it facilitates tax avoidance and a range of other things that aren't going to drive efficiency in an economy
-https://youtu.be/bO4jHXjCXw8?t=2m57s
>If it's an anonymous transaction, that sounds like a suspicious transaction. Why does somebody need to be anonymous?
- https://youtu.be/bO4jHXjCXw8#t=4m12s
I presume the real unstated requirement boils down to "Moxie is associated with the cryptocurrency." Not disclosed is whether he or Signal have financial interests in its adoption (they have said they don't "hold" any of these pre-mined coins, but that's all they'll say).
https://zk.money/
Of course, a lot of the friction with Keybase & Stellar was due to the magic ‘airdrop’ of coins, and all the craziness & flood out outsiders not interested in the Keybase mission itself.
But, the part that stands out to be, is many of the long time users or ‘die hards’ being very vocal about their distaste for the move. They say it doesn’t fit here, or ‘we don’t need this’, or whatever.
But the way I see it, who really cares? Some people will use it, some will ignore it. But if you’re a dedicated Signal user, and you don’t need or want this, why can’t you just keep using Signal the way you are now and not let it affect you?
Why does everything have to be some big philosophical nightmare when a feature you don’t care about gets added?
What are you suggesting? Are you afraid they will give a back-door to the VC backed crypto vendor? Because my point is, unless you think somehow adding a crypto wallet to some obscure coin is going to jeopardize the security of you messages, I just don’t get it.
Just pretend like it’s not there, and keep using it the way you use it. That’s what I did with Keybase. Yeah there is stellar wallet sitting there that I never click on, but I’m still a happy user.
I’m just not interested in sitting around and fuming about business practices I have no idea about. They are a big company, and in this world all companies have to ’grow’ year in and year out. Yeah maybe it’s misguided, but I think it’s wasted energy to sit around and be outraged over how some company decides to run their business.
And if it is so outrageous, then find an alternative. It’s just so exhausting to read comment after comment of people who think they know better than the people who created the thing. It’s there business they can do what they want with it.
If you don't audit and re-audit every bit of code in the whole stack for only alternative, as flawed as it is, is doing calculus based upon the reputation and character of the people producing the code. We differ in that I stopped using keybase when the stellar airdrop occurred. That company is now an appendage of Zoom, another company I've watched closely from a security point of view. I imagine you are also a happy user of that, whereas I'm a begruding/throw-away-laptop-under-duress user. I haven't seen the code from either product but have made a judgement based upon their behaviour.
This is the topic of this debate. If you find it exhausting reading comments from people trying to explain why they might be losing trust in a piece of trusted software, you are free to not read the comments and spend more time auditing code.
ps. There are literally thousands of encrypted messaging apps. That Signal claims to be another is a small differentiator. How does it back up the claim? These lines of reasoning always lead back to the people running the show and how they behave. Short of a State actor using gagging orders to insert back-doors, which is way outside at least my thread model, I moved to Signal because of its claims plus its aggregate reputation.
I don’t use Keybase much anymore but for some fun stuff. I still find the the file system useful.
Sounds like you will be quitting Signal soon too. Time to spend more time & energy researching which company to jump to next, splitting hairs, agonizing over business practices. Reading blogs & Twitter feeds of company officers and forcing opinions of them. Until 6 months later they do something egregious, and you have to start all over.
My main avenue for anything secure now is self hosted Matrix Synapse server. I’m in full control, and I don’t have to waste energy and mental cycles on getting mad about how other people run their business and stirring up outrage in forums.
It’s fantastic, low effort and low stress :) I’ve gone down the rabbit hole you describe before, I don’t need a lecture on it. But I decided it’s not worth it.
I believe I am happier by skipping all the stuff you’re taking about. Which was really my main point, I didn’t really say it very well though.
Don't tell me anyone involved in doing this felt like this was 'the right way to go'. Which makes exact motivation behind it all the more questionable.
If this feature is to stay relevant, it has to be integrated within Signal. Otherwise competitors (who do integrate a payment feature) will just have a better UX.
The choice was basically:
1. have the feature within Signal
2. have no user
They chose 1.
I think we need a reality check here. When I check the Playstore, Signal has 50M downloads. WhatsApp has 2B. Signal is still largely the underdog.
I could definitely imagine a few people using a "Signal Payments" app instead of whatever WA offers. But to actually compete with WhatsApp (which won't create a separate app), you can't afford to split the app in two. The aim is not that HN users are able to transfer money in a privacy-preserving way, it's that everybody can.
Signal's (meaning the app) goal should be to be a long-term, secure, honest alternative for more privacy minded users, no matter their technical expertise? At least that's what I'm thinking.
I see it more like setting the baseline for the whole ecosystem. If Signal allows me to do X privately, why can't WhatsApp? To have this clout, they need to keep a non negligible market share and remain a threat to other messengers, which you can't do if you miss features your competitors have and that users value.
Did it appear to these clowns that if I have to use a wire transfer anyway, I can just use a fucking wire transfer?
The best part about this is that besides all the obvious criticism for hooking up your chat app to a pump&dump cryptocurrency scam, the cryptocurrency is also just a legitimately terrible way to implement this feature. Manual wire transfers? 50p per transaction? Fucking price volatility?
You may have misunderstood what they're saying. The full sentence from which you quoted:
> It currently requires a wire transfer for people in the UK to get funds in and out of cryptocurrency exchanges that support MobileCoin, which costs money.
They're saying that you need a wire transfer to buy and sell MobileCoin using the currently-available exchanges. Once you possess MobileCoin, you can then send or receive it using the app without further wire transfers unless you choose to cash out. A wire transfer isn't necessary for a transaction in Signal.
(Hint: you can just give people contingents of your make-believe currency. But it's a better scam if they wire transfer money for it!)
If MOB becomes less volatile over time, you could imagine people having USD 100 in MOB that they would trade for small debts, and they could be fine leaving this sum in MOB. In this case, you'd have several MOB transfers for just a few bank transfers, and it'd be an improvement.
How stable they'll manage to make it, frankly I can't say, I believe it's still an open problem for them.
It'd be less inconvenient that a worse cryptocurrency, but more inconvenient than hitting a button in your bank app (the uk has instant transfers already).
Sure, assuming:
1. you have the app
2. you have the IBAN (or equivalent)
I'd say 1. is a good assumption for younger generations (?), but 2. is still more friction than what Signal could offer.
What I meant is that you need the IBAN of the person you want to send money to (of course you need to have an IBAN, as in, you need a bank account for your MOB to be actually worth anything). Assuming Alice and Bob are contacts on Signal, and Alice wants to send money to Bob, Alice still has to ask for Bob's IBAN. We can safely assume that Bob does not know his IBAN by heart, and has to use his ebanking app (for instance).
You already have some kind of identifier for Bob, Signal would allow you to reuse it. Some ebanking apps already allow you to do that, but I think in most cases both have to be clients at the same bank (?)
The idea is that you have less friction. The chat would be something like:
> B: can you send me 5 USD
> A: sure, here it is
> A sent you N MOB, equivalent to 5 USD.
Of course the UX is still far from being there (volatility is the biggest problem I think).
Yeah, it clearly did and they didn't like that you and everyone else doing that now has their transactions tracked. They know X paid Y an amount of $Z. They want you and everyone else to be able to transfer without anyone knowing to who. Just like using cash money in a shop (withdraw, transfer to Y, Y deposits in their bank and your banks know nothing as opposed to a direct deposit from X to Y where your banks know precisely when and who is on either end of the transfer).
Yes, as they note their current solution has issues. Transaction fees are too high. Volatility is a problem for any currency used as a medium of exchange absolutely.
So what is this? A start that can be improved on. If you want your transaction to be secret from your banks and those your banks share info with a wire transfer is probably not an improvement.
Might not work at all. Might have other issues as yet undreamed of. We'll see. Given I don't ever have to use this and Moxie has earned a reputation of not being neither crook nor zuck I'm kinda happy to watch and see what happens.
Immense amount of "Signal is terrible" on this site which doesn't make much sense to me.
edit: Immense amount.
Volatility is not an issue for any major world currency (USD, Euro, Yen, etc). If I pay the bill at a restaurant and ask my friends to repay me on Venmo, the money I receive is worth exactly the same when it hits my bank account a few days later as when the bill was paid. Perhaps you could argue it changed by 0.01% or something due to inflation, but cryptocurrencies can easily change by several percent per day.
There are plenty of models that facilitate the same privacy guarentees for stablecoins.