P2P Fallback mode in the android app

The android app now includes to ability to switch between using blockchain.info's servers to retrieve information about transactions and the bitcoin p2p network itself. When P2P mode is enabled the app will switch to using bitcoinj as an SPV client and once it has synced the block headers you can send and receive transactions even is blockchain.info is offline. It can also be used to verify your wallet balance independently of blockchain.

- In P2P mode you cannot generate new addresses (since the wallet can't be saved on the remote server)
- Watch only addresses will not work
- If the app cannot connect to the PIN server the password will need to be re-entered every time the app launches.

Bitmessage v0.3.0 is available. It is an important release with a new change relevant to everyone.
The most significant change is the move from version 2 to version 3 addresses.
With version 3 addresses, users may set the minimum-Proof-of-Work-difficulty that they require of others in order to receive a message. The network-minimum difficulty is 1 but you may, for example, demand that people who send you messages accomplish a proof of work with a difficulty of 1.5.
Before making new addresses, see the 'Demanded difficulty' tab in the settings menu.
The next new feature is encrypted broadcasts. Broadcasts sent from v3 addresses will now all be encrypted. Broadcasts sent from v2 addresses will remain in clear-text until 2013-05-28 at 10:00 UTC at which time all upgraded clients will automatically switch to using encrypted broadcasts for all addresses.
Note that broadcasts are only encrypted with the address of the person sending them.
Anyone who has the address may read the broadcast. Some people may try to decrypt all broadcasts with all addresses ever seen on the network; this is expected.
The purpose of this feature is to encrypt the data sufficiently well such that unencrypted data will not flow through your Internet connection that you are not actually interested in.
Going forward, all new addresses will be v3 addresses thus it would be wise to upgrade soon so that you may receive messages from new Bitmessage users. v2 and v3 addresses will remain mutually-compatible indefinitely.
The next new feature is Daemon mode which allows Bitmessage to run without a graphical user interface. https://bitmessage.org/wiki/Daemon
You may report issues to the Github issue tracker or by replying to this bitmessage. https://github.com/Bitmessage/PyBitmessage/issues
Users who downloaded the source code with git may use 'git pull origin master' to upgrade.
All the best, Atheros
https://bitmessage.org/
https://github.com/Bitmessage/PyBitmessage

Bitmessage v0.3.0 is available. It is an important release with a new change relevant to everyone.
The most significant change is the move from version 2 to version 3 addresses.
With version 3 addresses, users may set the minimum-Proof-of-Work-difficulty that they require of others in order to receive a message. The network-minimum difficulty is 1 but you may, for example, demand that people who send you messages accomplish a proof of work with a difficulty of 1.5.
Before making new addresses, see the 'Demanded difficulty' tab in the settings menu.
The next new feature is encrypted broadcasts. Broadcasts sent from v3 addresses will now all be encrypted. Broadcasts sent from v2 addresses will remain in clear-text until 2013-05-28 at 10:00 UTC at which time all upgraded clients will automatically switch to using encrypted broadcasts for all addresses.
Note that broadcasts are only encrypted with the address of the person sending them.
Anyone who has the address may read the broadcast. Some people may try to decrypt all broadcasts with all addresses ever seen on the network; this is expected.
The purpose of this feature is to encrypt the data sufficiently well such that unencrypted data will not flow through your Internet connection that you are not actually interested in.
Going forward, all new addresses will be v3 addresses thus it would be wise to upgrade soon so that you may receive messages from new Bitmessage users. v2 and v3 addresses will remain mutually-compatible indefinitely.
The next new feature is Daemon mode which allows Bitmessage to run without a graphical user interface. https://bitmessage.org/wiki/Daemon
You may report issues to the Github issue tracker or by replying to this bitmessage. https://github.com/Bitmessage/PyBitmessage/issues
Users who downloaded the source code with git may use 'git pull origin master' to upgrade.
All the best, Atheros
https://bitmessage.org/
https://github.com/Bitmessage/PyBitmessage

If I understand correctly, using a gateway costs you non-negligible amount of money.

Is it possible to use Ripple without using gateways? Like, issue your own IOUs etc.

Is it possible for gateways to ignore transactions which aren't beneficial to gateways?

I see two possibilities:

1. Either people are forced to use gateways so that in the end they pay more.
2. Or these almost-free transactions are not good for gateways and they'll try to curb them.

Well... It might be zero cost if people run servers for free, but I don't see how it can be sustainable. Of course, OpenCoin is interested to keep their servers running to create demand for XRP and sell those XRP for profit.

But how is this decentralized?

Seriously, it sounds like a scam...