Monorepo for Tangled tangled.org

Manually editing an existing sh.tangled.publicKey creates a duplicate key #439

open opened by blooym.dev

Whenever you manually edit an existing Tangled Public Key record (for example, to rename it like I did) the AppView will actually just make a second key with that new name and not remove the last one even though it was an edit event with the same rkey.

Screenshot

sign up or login to add to the discussion
Labels

None yet.

area

None yet.

assignee

None yet.

Participants 1
AT URI
at://did:plc:p5yjdr64h7mk5l3kh6oszryk/sh.tangled.repo.issue/3mgsvsuiojj22