How much money do you need to develop and maintain a Firefox version? Can I donate? I don't want to help to enforce this idea that Chrom* is the only browser that can run certain things, is against my believes.
Signal Desktop
191–200 of 288 posts
Re: Signal Desktop
#192Earlier quoted context omitted.
If we ever meet I'll buy you a beer for the year of the Linux desktop line. But honestly: I understand mobile support for iOS/Android only. I don't understand Chrome as a platform (FF isn't dead. And the biggest reason for that is that I fail to understand why that client needs to be 'web based' and then again not. A web app in a silo) Mobile numbers.. Why? I mean, if 90% of the population WANT mum to see that they u…
Perhaps Signal just isn't for you. No one who I've introduced signal to has ever had a problem with it. Now if you add a randomly generated 128 bit account identifier, then people WILL have problems with it. Not with you, but with your mum/grandma. I really think Signal might not be for you. Signal is not about building the most secure or private system, it's about building the first mass-market encrypted that that's…
If Signal's not good enough for us, what is?! I want to know...
Re: Signal Desktop
#193This isn't working for me, the code I'm supposed to scan won't show up, just Connecting.... (I installed from github)
EDIT: I apologise, I'm wrong. It appears github has been updated to remove this warning. and as it pretty says on github, the github repo is confiugred to connect to the development server. So yea, trying to jump the queue by installing the dev blob from github won't work.
I made it working:
1. Clone the Signal-Desktop Repo
2. Edit the File: "js/background.js" Line 56 SERVER_URL to 'https://textsecure-service.whispersystems.org' and Line 57 ATTACHMENT_SERVER_URL to 'https://whispersystems-textsecure-attachments.s3.amazonaws.c... and save it
3. Open chrome://extensions/
4. Activate Developer mode
5. Click "Load unpacked extension..." and select the Signal-Desktop directory
6. Open https://textsecure-service.whispersystems.org/ and accept the cert (otherwise you won't see the qr code)
7. Scan the qr code and have fun!
Re: Signal Desktop
#194Earlier quoted context omitted.
Telegram is closed source so we can't verify that they implemented encryption properly, and only Secret Chats have the messages encrypted. https://telegram.org/faq#q-so-how-do-you-encrypt-data
I thought the Telegram client is open-source, it's even on F-droid. The server side being open or closed source is meaningless: 1. In Telegram's threat model the servers are not trusted. 2. You can't verify server side code anyway.
The Telegram client can just barely be considered Open Source, see the discussion at https://github.com/DrKLO/Telegram/pull/76
Re: Signal Desktop
#195I'm feeling dirty, because I don't like to be that negative, especially if we're talking open-source software. And I feel that I kinda hold this project to higher standards: If I compare this to WhatsApp/Telegram/Threema/Whatever, I inheritently, somewhat subconciously expect more from Signal. And I'm disappointed. I tend to repeat the 'central server' and 'a phone number is not an address and not public information,…
They don't like to admit it, but Signal has a metadata problem. It's fine if that's not their threat model, but I wish they would be more clear about it, especially when other chat systems get criticism more often for precisely that aspect. Edit: "As far as we can determine, practical privacy preserving contact discovery remains an unsolved problem." -03 Jan 2014 [0] https://whispersystems.org/blog/contact-discovery/…
> "As far as we can determine, practical privacy preserving contact discovery remains an unsolved problem."
This reminds me of an idea I had which I would love for people to tear apart (I know that the obvious bandwidth problem makes it completely impractical, but I wonder if there are theoretical flaws):
Have a central server which everybody connects to. All clients send a constant stream of data, 24/7 - if they don't have anything useful to send, they send /dev/random. When they do have something to send, they send a GPG public-key-encrypted message. Every client then receives the entire stream of data, handles the data which it can decrypt using its private key, and discards the rest.
- Your contacts list is a GPG keyring - The server knows nothing - Anyone intercepting your internet traffic can't tell where your packets are destined for - You can't even look at two people's traffic patterns and say "these two people were active at the same time, they must be talking to each other"
Re: Signal Desktop
#196Earlier quoted context omitted.
I thought the Telegram client is open-source, it's even on F-droid. The server side being open or closed source is meaningless: 1. In Telegram's threat model the servers are not trusted. 2. You can't verify server side code anyway.
The Telegram client can just barely be considered Open Source, see the discussion at https://github.com/DrKLO/Telegram/pull/76
F-droid builds those parts separately from source.
> The official source code of the app contains binary blobs, so this tracks a fork which builds those from source. Hence, versions might become available with a certain lag.
https://f-droid.org/repository/browse/?fdid=org.telegram.mes...
Re: Signal Desktop
#197Earlier quoted context omitted.
I really wish this was an Electron / nw.js app instead of a Chrome plugin.
I've experimented with this and with a little tweaking it works fine under NW.js's alpha support for running Chrome Apps.
I mention it because downloading one file (a nw.js / electron build) is a lot less friction filled than (in some cases) downloading an entire browser just to use one app. There's still people out there who still use Firefox or whatever default browser their OS comes with. Instead of downloading one file, you're now forced to download two.
Re: Signal Desktop
#198Loving moxie's namedropping of oldschool revolutionaries: Maria (Masha) Alexandrovna Kolenkina was a Russian socialist revolutionary from a merchant family in Temzhuk, a small town on the Sea of Azov. (1850-1926) Vera Ivanovna Zasulich was a Russian Menshevik writer and revolutionary. (1849-1919) Nestor Ivanovych Makhno or Bat'ko Makhno was a Ukrainian anarcho-communist revolutionary and the commander of an independe…
Oldschool Communist revolutionaries, to be exact. Yeah, it's no mystery where Moxie's politics lie given those allusions and the not-a-company company, eat together, do push ups together, open salary policies.
Re: Signal Desktop
#199Earlier quoted context omitted.
Thank you for your reply. I really appreciate it. As I stated earlier, I feel bad about 'expecting more' here - I certainly see the appeal of a popular ~decent~ option. Without trying to derail this further, let me look at those points: If I use throwaway numbers: What happens if I lose access? Do I _need_ the number for anything in the future (say, device died)? Can someone else mess with me if they get access to th…
That's a pretty big holiday wishlist. =) This is the world we live in: people do most of their communication on mobile devices running iOS or Android, use Chrome on the desktop, and expect contact discovery to be automatic in their social apps. The browser has won the desktop, iOS and Android have won mobile, and the velocity of the ecosystem is unlikely to make "distributed" communication mechanisms possible for som…
The main thing I have against webapps is that from a technological point of view they aren't meant for the use we go today.
Obviously the privacy thing is another big issue, but this leads me to point 2;
I can protect my privacy: I just need to switch off my router, throw away my phone and say good bye to the grid, but that is the 2015 way of being an heremit and honestly, is something I don't want.
So I came up with this solution: carefully try to not divulge sensible data and, if I need to, split that over many possible unrelated services.
We're not going to win, but at least I try to defend myself
Re: Signal Desktop
#200Earlier quoted context omitted.
EDIT: I apologise, I'm wrong. It appears github has been updated to remove this warning. and as it pretty says on github, the github repo is confiugred to connect to the development server. So yea, trying to jump the queue by installing the dev blob from github won't work.
I made it working: 1. Clone the Signal-Desktop Repo 2. Edit the File: "js/background.js" Line 56 SERVER_URL to ' https://textsecure-service.whispersystems.org' and Line 57 ATTACHMENT_SERVER_URL to ' https://whispersystems-textsecure-attachments.s3.amazonaws.c... and save it 3. Open chrome://extensions/ 4. Activate Developer mode 5. Click "Load unpacked extension..." and select the Signal-Desktop directory 6. Open htt…
Fantastic, thanks, it's working great!