Content pfp
Content
@
0 reply
0 recast
0 reaction

vrypan |--o--| pfp
vrypan |--o--|
@vrypan.eth
Signers (rebranded as app keys) are extremely powerful, but I think they are becoming a disaster waiting to happen. Users are not aware how to manage them, and even if they were, there are no reliable tools to do so. Does anyone else share the same concerns? If so, what can we do to improve them?
2 replies
0 recast
8 reactions

Varun Srinivasan pfp
Varun Srinivasan
@v
Is it any different from OAuth tokens to your X account?
1 reply
0 recast
0 reaction

vrypan |--o--| pfp
vrypan |--o--|
@vrypan.eth
Invalidation of content created by the key. I see a list of signers I have approved in WC, some of them are for apps that no longer exist, but I can't remove them, because I don't know what will be removed. And even if I did, what choice do I have?
1 reply
0 recast
1 reaction

Varun Srinivasan pfp
Varun Srinivasan
@v
It should be pretty easy to write a script that resigns your messages before removing your app key. We haven't prioritized this feature in Warpcast because it's not that important. Most users app keys don't have a lot of messages, and even if they do they are mostly old, so users dont care too much if they get revoekd.
1 reply
0 recast
1 reaction

vrypan |--o--| pfp
vrypan |--o--|
@vrypan.eth
@stephancill has put together something like this. But I don't feel it's stable enough to trust it with my data, and it's definitely not a simple solution anyone can use. Otoh, this is a cool solution, that would let me remove old signers without worrying what happens to my content. https://warpcast.com/stephancill/0x71cf91d8
1 reply
0 recast
2 reactions