But chat will never go away, as we value direct conversations. Today many people mostly use Skype for chat, which is a bad idea for many reasons:
- It doesn't use an open protocol, so it is very hard, almost impossible, to put Skype to use except through the official Skype client.
- Your messages aren't encrypted between you and your chat partner, so your conversation can (and in some cases probably is) monitored. Remember that Skype offers phone calls to normal phones, and to be allowed to connect with the public phone system, they have to comply with lots of government regulation, of which machinery for wire-tapping by police is one.
- It isn't open source, so it is unclear how things works.
- Also Skype has become bloatware.
Plus it supports OTR, which is an easy to install plugin that offers (quoting directly from the website):
- Encryption - No one else can read your instant messages.
- Authentication - You are assured the correspondent is who you think it is.
- Deniability - The messages you send do not have digital signatures that are checkable by a third party. Anyone can forge messages after a conversation to make them look like they came from you. However, during a conversation, your correspondent is assured the messages he sees are authentic and unmodified.
- Perfect forward secrecy - If you lose control of your private keys, no previous conversation is compromised.
If you are curious about chat in general, EFF has a very good page.
You might want to check out this software, for untraceable digital cash:
ReplyDeleteWHAT IS 'Open Transactions' ?
It's a solid, easy-to-use, FINANCIAL CRYPTO and DIGITAL CASH LIBRARY.
Including an operational API, SERVER and CLIENT.
Diagrams:
Architecture Overview: http://opentransact.nevermeta.com/OT%20Diagram.jpg
Fully-Anonymous (cash only): http://opentransact.nevermeta.com/OT-Anon-CashOnly.jpg
Pseudo-Anonymous (using accounts): http://opentransact.nevermeta.com/OT-Pseudonym-Instruments.jpg
Featuring:
-- Untraceable Digital Cash (real blinded tokens)
-- Anyone An Issuer (Ricardian-style Contracts)
-- Bearer-only, Fully-Anonymous (when used cash-only)
-- Pseudonymous User Accounts (user account == PGP key)
-- No Account History (asset account == the last receipt)
-- Many Financial Instruments (cheques, cash, vouchers, invoices...)
-- Basket Currencies (10 "baskets" == 5 gold, 3 silver)
-- Markets with Trades (stop, fill-or-kill, limit orders...)
-- Payment Plans
-- Native API for Java, Ruby, Python, PHP, Perl, C,
C++, Objective-C, C#, Tcl, and LISP
-- XmlRpc/HTTP transport layer (build option)
-- Soon: Stocks that pay dividends, Bonds that pay interest,
and even Collateralized Debt Obligations.
-- Soon: 2-D Barcodes to make possible 'Any screen a cash
register' and 'Any camera phone a customer.'
Please see the Project page:
http://github.com/FellowTraveler/Open-Transactions/wiki
Use Cases:
http://github.com/FellowTraveler/Open-Transactions/wiki/Use-Cases
FAQ:
http://github.com/FellowTraveler/Open-Transactions/wiki/FAQ
Business Cases:
http://github.com/FellowTraveler/Open-Transactions/wiki/Business-Cases
Release Notes:
http://github.com/FellowTraveler/Open-Transactions/wiki/Release-Notes
"Seeking developers to contribute by writing client software and
doing other integrations! I will support you on the OT API. Let's
make this happen!" -Fellow Traveler
this one is very impressive plus instructive software development group
ReplyDeleteThis is the precise weblog for anybody who needs to seek out out about this topic. You notice so much its almost arduous to argue with you. You positively put a brand new spin on a subject that's been written about for years. Nice stuff, simply nice!
ReplyDeleteHey keep posting such good and meaningful articles.
ReplyDeleteHi, Really great effort. Everyone must read this article. Thanks for sharing.
ReplyDelete