I would not want to implement all these ideas, more i was having a mini brain dump to get some discussion on the topic.
Ultimately, having the experience as embedded as possible is important here and everywhere and that is what i am aiming for.
The challenge of site hosted wallets for tipping, vs using the users own wallet is going to be a trade off between security and accessibility
However you raise an interesting point that i hadnt thought of where tipping could be “contained” within a site
My view was a little broader.
e.g I run a blog and someone tips me on a particular post (funds go to my defined browser wallet address)
I come here and participate in a discussion and feel that someone deserves some crypto love
I can call on my funds directly from my browser wallet, and not have to think about transferring to the local storage.
The funds are transferred directly from my wallet to yours
So, my little bucket of crypto love can be used everywhere without thinking on localising.
With the way the wallets works, you could have as many wallet addresses as site you participate in and send/receive funds as required (ie, you register an address of your own wallet, rather than a tipbot address).
Again, there is no right or wrong way, but i was taking a lead from the current implementation here on this forum and trying to improve on some ideas.
The Browser Wallet does make most of the above easy,
But, i would like to see BIP21 improved to handle desktop (QT) wallets if possible (call QT, if browser wallet not installed)
But i digress, as it is not important for functionality, rather future improvements
I am after more feedback on the front end as this is what needs to work seemlessly