How does this affect smartphone wallets for Monero?

So, I had previously created these two mobile wallets for Android / Windows 10 respectively:
https://github.com/ShenNoether/MiniNeroUniversal & https://github.com/ShenNoether/MiniNeroDroid

These rely on a server app running with your Monero installation, which is somewhat complicated to set-up (several command line steps). The web-app that this post references will run in conjunction with that server, and will have a web-interface to ease the set-up process). The web app should be able to most of the command line process with simply scanning a qr-code generated in the web-app with your phone app (this is the API-key tab).

Additionally, this version of the server should remove several dependencies which were making installation annoying on certain platforms, and add several alternative server languages (go, ruby, python, perl).

Caveat, that I am writing these in my spare time, and don't have a solid timeline for completion.

TLDR: The MiniNero web will make the setup of the above two phone wallets much easier. Additionally, MiniNero Web can be used as a simple, standalone wallet.

All the notes you list after 805/806 are actually for 794. Wallet refresh speedups in 806 have no downside.

How does this affect smartphone wallets for Monero?

So, I had previously created these two mobile wallets for Android / Windows 10 respectively:
https://github.com/ShenNoether/MiniNeroUniversal & https://github.com/ShenNoether/MiniNeroDroid

These rely on a server app running with your Monero installation, which is somewhat complicated to set-up (several command line steps). The web-app that this post references will run in conjunction with that server, and will have a web-interface to ease the set-up process). The web app should be able to most of the command line process with simply scanning a qr-code generated in the web-app with your phone app (this is the API-key tab).

Additionally, this version of the server should remove several dependencies which were making installation annoying on certain platforms, and add several alternative server languages (go, ruby, python, perl).

Caveat, that I am writing these in my spare time, and don't have a solid timeline for completion.

TLDR: The MiniNero web will make the setup of the above two phone wallets much easier. Additionally, MiniNero Web can be used as a simple, standalone wallet.

All the notes you list after 805/806 are actually for 794. Wallet refresh speedups in 806 have no downside.

correct. The new password is for the new wallet C. This new wallet is unable to spend your money.

Agreed on the underlined. New improvements to simplewallet allow for individual bookkeeping, but not particularly audibility - i.e., you'd have to give someone your wallet files or something.

Though the point has been raised that bookkeeping doesn't need to be a fundamental property of a currency.

There is room for improvement for sure, but it is debatable whether it should be in the protocol or as a layered-on thing.

I said it is a complex game theory discussion. Seems you want to force me to have that discussion when I said I am busy on other more urgent priorities. Because I can't just leave your afaics incorrect assumption there unrefuted.

You can't retain an older version, because soon the new features will become intertwined in everything and soon you won't be able to function in the network. The complexity of failure modes with an older version are beyond the scope of the discussion I want to have now. That will be a technical discussion. Just remember what happened the last time I got into a technical discussion with gmaxwell on Ogg streaming format indexing, a topic that he thought he was more expert on (and he should have been since he was the co-inventor of one of the Ogg codecs).

Thank's for the link, that's an awful lot to read for a simple question, i tried to read it out of there but unfortunately not managed to do so...
Would you be so kind to explain it in a way, as i tried to in the above example, simplified so i can understand this too? (Maybe update that point at moneropedia too)

Thanks in advance  

Correct. However, (i) Trezor will greatly mitigate these issues because it is able to show you a balance whilst remaining safe (i.e. it's impossible for, for instance, malware to steal your funds) and (ii) there are some options to show outgoing transactions and thus a balance too, which were discussed in this thread:

https://np.reddit.com/r/Monero/comments/4dly99/lack_of_feature_to_easily_monitor_current_balance/
I'd also suggest to read this:

http://weuse.cash/2016/03/07/trezor-for-monero-first-impressions/

P.S. The protocol allows the audibility of a company via key images. That is, company A could hand over their key images and their viewkey for a given year and an audit company would perfectly be able to audit all the transactions and balances for that given year.

Frankly I haven't yet studied SegWit in great detail, because I will wait until they have finished it, so I am not losing time studying a moving target. I have no influence on the Bitcoin community's decisions, thus studying it now is of no significant advantage in the holistic priorities.

Conceptually I understand that SegWit enables outsourcing validation and retains hashes of the validated data on the block chain. Afaics, this is centralizing for at least three reasons:

1. Those with preferential access/propagation to validators can earn more with the same hashrate by mining on the correct block slightly sooner. Over time this moves ROI and thus hashrate concentration to those who have these political connections. However, this is not much different than the same effect that can exist now where miners with significant hashrate (even a cooperating set of them) can validate their block announcements sooner than the rest of the network. Afaik, the salient worsening due to SegWit is that validation concentration can now be political, not only by hashrate concentration, so it amplifies the vectors towards centralization.

2. Afaik, SegWit relies on trust enforced by voluntary fraud proofs to insure that the validation is correct for each hash on the block chain. Afaics, the game theory around these voluntary fraud proofs drives more centralization. But this is not something I want to detail now. It is a complex discussion and I am busy on more urgent priorities.

3. Afaik the new versioning capability that will be introduced with SegWit, basically hands the power to Blockstream to drive forks any time they want to. Again this is another game theory discussion which I don't wish to elaborate on at this time. Note Monero's periodic forks as a protocol also seems to a form of centralized control. One can argue that miners can vote, but it is fairly impossible to stop the political clout of the lead developers especially when that control is hardwired into the protocol. Satoshi's design was that it should be nearly impossible to hard fork, because that is the only way you truly have decentralization.

Question #1
Why is it only showing the incomming balance, and not the spended balance also?

Question #2
The usage of the viewkey option is quite, let's say, less good documentated. To clear some things up here a little bit, please advise me in the following schematic description

I have wallet "A" with the corresponding viewkey "B" from wallet "A"

If i want to check the balance of wallet "A" with the viewkey "B" i have to create a wallet "C" and have simplewallet running on wallet "C" with the command?

Am i getting something wrong here? I am sorry, but the documentation is not very expressive...

I heard that the SegWit will be implemented in a few weeks according to the bitcoin core road map. So the price could rise.

If you have an IRC client, just make sure you are on the freenode server and you can subsequently join #monero-dev

If you don't have an IRC client, you can follow the dev meeting using:

http://webchat.freenode.net/

Set the channel to -> #monero-dev

And pick a nickname you like. Everyone is welcome to follow the dev meeting!

If you have an IRC client, just make sure you are on the freenode server and you can subsequently join #monero-dev

If you don't have an IRC client, you can follow the dev meeting using:

http://webchat.freenode.net/

Set the channel to -> #monero-dev

And pick a nickname you like. Everyone is welcome to follow the dev meeting!

Is Monero a fork of a scamcoin?

John Connor (VCASH def)  said that Monero stole his code, is that right?

XMR / Monero broken crypto:

I tested it against 19 transactions, some mixin 4 and some mixin 20 (excluding my own signature, so mixin 5 and 21 according to ChainRadar).

For these transactions none of them were completely compromised by ChainRadar, and ChainRadar got 0 out of 157 guesses correct.

It's bad crypto alright. Monero users were transacting "anonymously" for a year only to discover later that they could be trivially deanonymized because those in charge hadn't fixed a "hole" in the system from the start.

and/or maybe not!

im more concerned about monero's security when quantum computing makes a breakthrough.. 

How do i create a paperwallet?

Found nothing in OP.

Thanks.

Monero is nice but will get hit so hard when Zerocash launches that you will all regret not getting out when you had the chance.

Well here is a test for getmonero.org http://www.websitepulse.com/help/testtools.china-test.html

Website Test Results
Tested From:   Shanghai, China
Tested At:   2016-04-22
00:22:49 (GMT +00:00)
URL Tested:   http://getmonero.org
Resolved As:   104.25.211.22
Status:   OK
Response Time:   14.872 sec
DNS:   0.000 sec
Connect:   0.277 sec
Redirect:   12.382 sec
First Byte:   2.213 sec
Last Byte:   0.001 sec
Size:   2779 bytes
   
Tested From:   New York, NY
Tested At:   2016-04-22
00:22:49 (GMT +00:00)
URL Tested:   http://getmonero.org
Resolved As:   104.25.211.22
Status:   OK
Response Time:   0.507 sec
DNS:   0.000 sec
Connect:   0.009 sec
Redirect:   0.083 sec
First Byte:   0.415 sec
Last Byte:   0.000 sec
Size:   2779 bytes

The overall response time was 14.872 sec vs 0.507 sec. On a 2 min blocktime (Monero) this is very significant. Also how would the Chinese miners communicate with each other if they are using external servers without going four times across the GFWC? If they use Chinese servers they could avoid this; however they would still have to deal with domestic spying that would introduce both latency and bandwidth limitations.