I figured that when publishers do that (autoplay) to you, you can respond back by blocking scripts for them.

You will find https:///www.wire.com/ interesting. e2e encrypted, clients for Windows, Mac, Android & iOS. And chats are synched between all your clients. Also .. no phone number required to sign up; use your email.

It's closed source, has no linux client and it's not end-to-end encrypted. https://mobile.twitter.com/thegrugq/status/54017648967774617...

Also have a look at https://wire.com/legal/#privacy

All crypto is open sourced.

https://app.wire.com offers full functionality on Linux.

That tweet you link to is over a year old. Wire is E2EE since March 2016. https://wire.com/privacy has security and privacy whitepapers.

PS. I work at Wire.

Missing Linux native, but that might be too much to ask. Thanks for the link. I'll give it a try.

Do you know if it's open source or at least gone through an audit?

The crypto modules are indeed open source. https://github.com/wireapp

I don't know whether they have been formally audited.

That would be the source of some crypto code, not necessarily the code the app itself uses. Since the app is closed, there's no way to verify.

How is client sync possible with e2e?

Why wouldn't it be possible? The app knows who is sending to who and which devices are linked.

Because if it's end to end encrypted each device would either need the same private key to decode the messages or each message is encrypted with each devices public key.

This would require some kind of key exchange i.e. scanning bar codes.

There are probably a million ways to deal with it.

I haven't looked into it at all, but one way I just thought of right now is to have your own devices p2p the message among themselves with original sender's information after the one used most recently receives it.

I've noticed that a new device added to the account will not see the history. It only sees those messages that are received or sent after it has been added to the account.

There's no technical reason that the synced devices couldn't distribute the missing messages amongst themselves. :)

Signal also syncs its e2e encrypted chats

Client-to-client, simple as that. Pushed in encrypted form like regular messages.

It's possible because chats are not end-to-end encrypted.

Why aren't you using Wire (https://www.wire.com)? It is cross platform, end to end secure w/ open source audited crypto, focuses on app usability, and doesn't need a phone number to sign up.

Trust issues with the founders (Skype hardly had a great privacy record); inability to build own APK (because only the crypto is open source) means you can't be sure the code on GitHub is what you're really running.

I had honestly never heard of it before. It looks good, but the website is completely lacking any information about the company which again makes me feel a little bit uneasy. I might try it, though.

Some one needs to pay attention to Bittorrent Bleep https://www.bleep.pm/ It is closed source but it riding on a big P2P betwork.. the Mainline DHT

Why would a closed source client from a company known to be scummy (looking at what they did to uTorrent) be something anyone should pay any attention to? (FWIW I did check it out, but it wasn't better than Telegram, nor was it better when it was released than Signal is now.)

I'm not filled with confidence when visiting a secure messaging app site that fires off warnings when visiting the https url.

Of course HTTPS is not at all secure due to that central source of authority enabling easy large-organization MITM.

If the problem you're solving is bringing E2E encryption to the masses, then starting with a site that brings up

"Your connection is not private

Attackers might be trying to steal your information"

as the very first thing I see is not really leaping over the first hurdle.

Users can always revoke their public keys. The same public key does not have to be used continually. Allow users to revoke their keys as often as they like. Heck, force the keys to expire in 1 day if you like! We already expect the sender to be online. The sender can check for key revocation before they send the message. Or let the server send back a error response if the sender used an expired or revoked key to encrypt the message.

Torrent here http://burnbit.com/torrent/227565/201211_musk_mp4

Thx

That would be best. Share the magnet link and we will all help.

Ok. I used Burnbit to create a torrent

http://burnbit.com/torrent/227565/201211_musk_mp4

Would love to, but am at a university network and will go home in less than 20 minutes. If the Veoh doesn't work, I'll upload to depositfiles.com, so you could grab it from there and then torrent it? I agree that it's probably is the best solution.

Rs 98 / month is for 2 GB of EDGE data per month. That is the normal charge in India for every mobile customer. This is not a special tariff for this tablet.

Seconded. I currently live in Bangalore and pay just Rs 400 (about $8) per month for blackberry services + unlimited 3G usage. I had this Rs 98 plan a few years ago when I was in college and didn't have a 3G capable phone.

If you send a friend request to some one, and they don't respond (it happens) - you still get to see their public posts in your news stream.

Wouldn't Facebook massively improve usability by just including the Lists in the drop down list in the web interface also? It is actually not too hard if they approach this incrementally.