ahalam

In January itself. One of the devs said

Google has a reputation of extinguishing its own projects. So who knows how long their fascination w/ Fuchsia will last.

FastMail had some of the cleverest ideas for plus addressing. [email protected] could be given away as [email protected]

If only my corp allowed me to upgrade the macOS on my laptop, I would be using the latest Safari too instead of messing with Chrome / Brave.

Micropayments.

Why did you give up on Brave? I find Brave a good option on Android with all the privacy options built in. What am I missing?

It is possible to embed posts from public channels in web pages. In fact, if your group is public, you can even embed conversations in your web page. Try the announcement link here https://t.me/telegram/83

Last week, someone on a Android podcast referred to it as "Alto"! No one remembers / knows what it is.

Wire (wire.com) is now fully open sourced. You can build your own client from https://github.com/wireapp and use it to talk to other user using the official clients.

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

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.

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

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

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.

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.

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

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

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

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.

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.

Buzz is/was the same. If they hadn't forced Buzz down every one's throat, it might have been successful.

Buzz + suggest who to follow!

The problem with FB groups is that both you and the friends that you want to share the link/photo/message with have to agree to be part of that group. I usually put my friends in multiple groups/circles, i.e. they could be a work colleague but also a eating out enthusiast. This multiple categorization can easily get messy and definitely doesn't scale to hundreds of friends.

Hopefully, with Google+ Circles my private categorization of my friends is not shared with them. They should only see what I share.

The teams maybe autonomous in Google but I'm sure that they are aware that they are duplicating functionality and thus really harming the company. What the heck the are product managers and their managers doing at Google? Building their own little empires?

Agreed. It shouldn't be counted as revenue. It is such misleading reporting that leads to over valuation and bubbles.

Man-in-the-middle attack are made less likely because the 3DSecure page where the user is asked to enter a password also contains challenge question that was originally added by the user at the time of setting up 3DSecure for his/her account. The user should be able to recognize that this is not the bank's website when the challenge question is not his/her own.