Content
@
https://warpcast.com/~/channel/walletconnect
0 reply
0 recast
0 reaction
polymutex
@polymutex.eth
Imagine the HTTPS protocol spec requiring browsers to route all HTTPS traffic through G∗∗gle, and any browser routing traffic through G∗∗gle must pay for the privilege. And then describe this as a "Open protocol for connecting browsers to websites" on the first line of the README.
5 replies
8 recasts
21 reactions
accountless.eth
@accountless.eth
@ardaddy.eth @hennadios
0 reply
0 recast
2 reactions
Señor Doggo
@fubuloubu
Wonder if they got approval from their 156 contributors to make this license change
0 reply
0 recast
1 reaction
Degengineering | $DGNGX
@degengineering.eth
Agree with your analysis. Sadly, people do not care about such "detail" same goes for "Ethereum L2" and other Blockchains that are still at stage 0 or 1. Wallet connect has a great potential and solves a real problem: it can become some kind of decentralized ngrok for wallets. They need to not give up on the decentralization of the walletconnect infrastructure although it is hard because they have to balance legal risks, independant node runners and the overall quality of the service. And that's especially hard since they haven't given up on websocket connectivity...
0 reply
0 recast
1 reaction
markus - ethOS - e/acc-d
@markus
🤣
0 reply
0 recast
1 reaction
Lucas | POAP Studio @ Devconnect
@gabo
@worthalter !
0 reply
0 recast
1 reaction