[TTT] Design copy for TTT not available on current network

[yenda]

Problem

Currently TTT is only available on mainnet, the TTT setting should reflect that on other networks by either not showing up or showing a warning

[errorists]

Let's show it disabled with a message like so

https://www.figma.com/file/aS1ct66VQ6V0cio7vSqS8UoG/Chat?node-id=4706%3A0

also @yenda if I'm on testnet and hit a paywall myself, I assume we need to communicate it too right?

[yenda]

What do you mean I don't understand the question

[errorists]

in the instance of a user not being on mainnet, if he would encounter a new contact with TtT enabled, would he be able to interact and pay the tribute?

[yenda]

Ttt is per network, so if let's say I'm on mainnet and you are on ropsten, I have no way to know if you have ttt enabled. That's why swarm feeds will be much better and reliable.

…

On Wed, May 1, 2019, 13:05 Maciej Zadykowicz ***@***.***> wrote: in the instance of a user not being on mainnet, if he would encounter a new contact with TtT enabled, would he be able to interact and pay the tribute? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#8090 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAJAMKJJ5T6VSAQUHWK3QT3PTF2P7ANCNFSM4HJSQ7ZQ> .

[yenda]

#8090 (comment) has been implemented in current ttt-flow draft