Earlier quoted context omitted.
No, it’s not the same with stocks. With stocks, as a majority holder, you can make the minority an offer that everyone is forced to accept if a majority of the minority accepts it. This is why market cap is relevant to the stock market, but not e.g. the forex or commodity market.
What I was saying was if everyone wants to sell and nobody wants to buy, the value is zero. This is true of all markets. The market cap is always determined by the last matched order, not the total that you can sell the whole market for.
Signal adds a payments feature with a privacy-focused cryptocurrency
621–630 of 665 posts
Re: Signal adds a payments feature with a privacy-focused cryptocurrency
#622Earlier quoted context omitted.
No, this is just what happens when you try to hit the page from a US IP address.
Why are you blocking the US?
Re: Signal adds a payments feature with a privacy-focused cryptocurrency
#623Earlier quoted context omitted.
Monero is clearly the most practical secure coin as evidenced by it's popularity on the darknet. But I think what MobileCoin offers is speed.
And way less energy consumption, according to their website.
Re: Signal adds a payments feature with a privacy-focused cryptocurrency
#624Earlier quoted context omitted.
> 3. Moxie directs his non-profit to integrate MobileCoin in secret The fact that Moxie is collaborating with MobileCoin has been known for years . EDIT: See links in https://news.ycombinator.com/item?id=26718488
But not the fact that it's going to be directly integrated into Signal. The CEO of MobileCoin is in here saying that he started it as a way to fund Signal, which from what I can tell, wasn't public knowledge until today. So he gets to monopolize a currency that was mostly worthless, knowing that it would be directly integrated into a popular application, greatly increasing its value. If that's not a scam, I don't kno…
To be honest, that was exactly the impression that I got back then. So to me, yesterday's announcement was no surprise at all. Whether I like it, is a different matter.
Re: Signal adds a payments feature with a privacy-focused cryptocurrency
#625Earlier quoted context omitted.
> A hard fork in a decentralized cryptocurrency is democratic Yup, and I don't want public votes to decide the amount of money I have.
> public votes to decide the amount of money I have. Unfortunately, there is no alternative. The value of what you have is decided by what people are willing to pay for it in markets. If people decide that they value the forked ETH that doesn't provide the money to the people who stole from the DAO more than the version where those people have all of the money, then it is going to be more valuable. You don't escape t…
Re: Signal adds a payments feature with a privacy-focused cryptocurrency
#626Earlier quoted context omitted.
> public votes to decide the amount of money I have. Unfortunately, there is no alternative. The value of what you have is decided by what people are willing to pay for it in markets. If people decide that they value the forked ETH that doesn't provide the money to the people who stole from the DAO more than the version where those people have all of the money, then it is going to be more valuable. You don't escape t…
Gold or other physical scarce assets come pretty close to allowing you to escape this.
As I said, there is no escaping market mechanisms, as value is market contextual. Certainly, there are assets with more or less stable value, but that is still due to the whims of what people (ie. the "public") are willing to pay.
Re: Signal adds a payments feature with a privacy-focused cryptocurrency
#627Earlier quoted context omitted.
You're making very strong claims here. Signal regularly goes the extra mile to protect their users from 3rd-party tracking (by Giphy[0, 1] etc.) and, as they noted on GitHub at some point, they also consciously decided against UI/UX tracking and error reporting because they did not want to give off the impression that they themselves are surveilling their users. And now you're telling us that they deliberately includ…
> AFAIK the Signal app doesn't connect to the Google servers directly, so even if it exists, the cookie doesn't get transferred anywhere. The Firebase Cloud Messaging library / Google Play Services on your phone do connect to Google but they carry unique identifiers, anyway. It does connect to google's servers for pretty much everything [1] - you can look for these constants in the codebase and you'll find lots of th…
I remember reading all those threads (the one on GitHub and those on Twitter) back in the day and, honestly, I didn't come away impressed by the way some people treated Moxie. I've been in his shoes a few times now (trying to build a product that works – technically and economically – with team of anarchistic techies) and can empathize with the path he's taken. Not understanding his POV is no excuse for being rude, though. Now, since you posted the link, I went through that GitHub thread again and my impression has stayed the same. A few quotes:
> Wow, moxie0 just sounds sounds like a giant cunt. Anyone who uses a binary compiled release of Signal from the Google Play Store for security is a fucking idiot. (https://github.com/LibreSignal/LibreSignal/issues/37#issueco...)
> FUCK YOU OWS!!! (https://github.com/LibreSignal/LibreSignal/issues/37#issueco...)
> I must say, you [moxie] really are the worst anarchist I've ever encountered in my life; but I'm no authority on the matter. Writing good software doesn't give you a license to bully other projects around unless they give you a WhatsApp-level payout. How about you keep your narcissism tucked in so that secure messaging in general doesn't have to suffer from it? (https://github.com/LibreSignal/LibreSignal/issues/37#issueco...)
> That post [by moxie] is pure politics. It's a bunch of feel-good phrasing, cringe-worthy in its superficial slickness, that obfuscates what is really a giant policy-level middle finger from in terms of Open Whisper Systems shifting away from free software and into a centralized, All Rights Reserved commercial outfit. (https://github.com/LibreSignal/LibreSignal/issues/37#issueco...)
Here's what the people in the thread had to say who didn't get all personal:
> [Directed to someone else on the thread:] Whatever your take on what "the right thing" is, there is no need to get personal. And as previously said, Signal is free software - that entitles you to the source code, and no more. Noone is in the right to demand that OWS do anything else, and that includes most of what is being said in this thread. (https://github.com/LibreSignal/LibreSignal/issues/37#issueco...)
> I thank @moxie0 for replying when asked by @mimi89999, providing his (OWS) point of view in a polite and useful way, bringing up some truly interesting aspects of the issue. I can understand @cjeanneret's frustration, feeling just one step away from a truly free and secure messaging system, but this is no excuse for being rude. (https://github.com/LibreSignal/LibreSignal/issues/37#issueco...)
Re: Signal adds a payments feature with a privacy-focused cryptocurrency
#628Feels like a gut punch, I feel horrible asking people to switch to signal after buying into signl marketing, all of that now seems to be a ruse for their ecoin business.
Deleted the app. Also left a note in status so others can see the msg and delete the app also.
Re: Signal adds a payments feature with a privacy-focused cryptocurrency
#629Earlier quoted context omitted.
You're making very strong claims here. Signal regularly goes the extra mile to protect their users from 3rd-party tracking (by Giphy[0, 1] etc.) and, as they noted on GitHub at some point, they also consciously decided against UI/UX tracking and error reporting because they did not want to give off the impression that they themselves are surveilling their users. And now you're telling us that they deliberately includ…
> AFAIK the Signal app doesn't connect to the Google servers directly, so even if it exists, the cookie doesn't get transferred anywhere. The Firebase Cloud Messaging library / Google Play Services on your phone do connect to Google but they carry unique identifiers, anyway. It does connect to google's servers for pretty much everything [1] - you can look for these constants in the codebase and you'll find lots of th…
Have you actually looked at that code? It's for domain fronting[0], so nothing shady, and it's only used when you're in Egypt, UAE, Oman, Qatar, or Iran. Have a look at
https://github.com/signalapp/Signal-Android/blob/d74e9f74103...
vs
https://github.com/signalapp/Signal-Android/blob/d74e9f74103...
and, finally,
https://github.com/signalapp/Signal-Android/blob/d74e9f74103...
> you can look for these constants in the codebase and you'll find lots of things that would worry any netsec person, including the key backup related stuff
I just ran a recursive grep on the entire repository and the file you referred to is effectively the only place where a google.com URL shows up in the code (apart from two or three more instances which are not suspicious, either).
Maybe I'm missing something, so feel free to prove me wrong, but right now my impression is that you're spreading FUD for no good reason.
Re: Signal adds a payments feature with a privacy-focused cryptocurrency
#630The comment from the article echos my own sentiments: > Speaking solely as a person who is really into encrypted messaging, it terrifies me that they're going to take this really clean story of an encrypted messenger and mix it up with the nightmare of laws and regulations and vulnerability that is cryptocurrency. Moreover, there are three other points I'd add: 1. I don't like "do everything" apps like WeChat or Line…
What about using Wickr as an alternative to Signal. What all these "tech" companies tend to do is to exploit a captured audience. They are generally not focused on doing one thing well (producing a product or providing a service), they are more focused on building a following and then doing with those users whatever they like. One of the most blatent examples of this line of thinking is Microsoft's acquisitions. They…
## Linux
### Linux Requirements
- CMake 3.1 or higher
- Clang
- OpenSSL => 1.0.2 (Optional)
### Linux CMake Configuration
The linux build can be configured using the standard CMake flow with a few options
```
mkdir build
cd build
cmake -DBUILD_OPENSSL=true \
-DCMAKE_BUILD_TYPE=Release \
-DCMAKE_INSTALL_PREFIX=USER_INSTALL_LOCATION ../