Skip to content
This repository has been archived by the owner on Aug 11, 2024. It is now read-only.

New, preferred petname is "aka" when renaming a peer #866

Closed
cdata opened this issue Aug 10, 2023 · 0 comments · Fixed by #869
Closed

New, preferred petname is "aka" when renaming a peer #866

cdata opened this issue Aug 10, 2023 · 0 comments · Fixed by #869

Comments

@cdata
Copy link
Collaborator

cdata commented Aug 10, 2023

I renamed some peers (“justin” -> “justin-mobile” and “justin-alt” -> “justin-desktop”) using orb, and when it sync’d over to Subconscious the UI presented the old names as the primary display name and presented the new ones as “aka …”, which violated my expectation that the new name would be the ones I use henceforth.

image

Related history from orb:

Version: bafyr4ibakhdnv5emnt33kqryjkccfgp734ynmt4dkhj4ysohhgwcuelvui (Latest)
Author: did:key:z6MkomJ522T3mpCndV57uQ4GYMZka4AEeG3ybF7LYdpMY6Fe
Changes:

     Updated  justin-mobile -> bafkr4iextxtremdznjin6m4copubb62x7m2ze4i732j45v4qmtv6kc7sie

Version: bafyr4idlkzsimfjfwf74tiwvw2a7hkt7msf6ncos2ng3dypopjmowgiqnm
Author: did:key:z6MkomJ522T3mpCndV57uQ4GYMZka4AEeG3ybF7LYdpMY6Fe
Changes:

    Followed  justin-mobile -> did:key:z6MkkHxPkcm6oQRHN5s9gaQTE2kCpix8YZudJhPsU2EYWm5D

  Unfollowed  justin

Version: bafyr4idw4mgw7ujn2fijzddf3uqxvrp57xnaajyr2jrlbt43sut3gmew2u
Author: did:key:z6MkomJ522T3mpCndV57uQ4GYMZka4AEeG3ybF7LYdpMY6Fe
Changes:

     Updated  justin-desktop -> bafkr4ifyb7arlj5xp24nl4whd3nmukmncyr4556hbbxzu3ow73fbzvf2da

Version: bafyr4ihfq4atfrluiatmh7bbqhpd2vueyegmejs4q7y7u6slkhzqq73kzu
Author: did:key:z6MkomJ522T3mpCndV57uQ4GYMZka4AEeG3ybF7LYdpMY6Fe
Changes:

    Followed  justin-desktop -> did:key:z6MkpNG41cX5cYXtRXrGSzG6dt6c4SXAHQsK17DSUxo68x3G

  Unfollowed  justin-alt
@bfollington bfollington moved this to 🧑‍🌾 In Progress in Subconscious + Noosphere Aug 10, 2023
@bfollington bfollington mentioned this issue Aug 11, 2023
Merged
bfollington added a commit that referenced this issue Aug 18, 2023
@bfollington
Manage cache validation by comparing version CID (#869)
ee981d7 
Fixes #866

Instead of trying to manually invalidate the cache we can simply store
the version (`Cid`) as a cache key. Assuming my Noosphere fundamentals
are correct, we should never observe a change in address books or user
profiles without out own sphere version changing - incredibly
convenient.

I removed any references to manual cache invalidation since we're using
this method in the only two in-memory caches that exist so far.
@github-project-automation github-project-automation bot moved this from 🧑‍🌾 In Progress to 🌱 Done in Subconscious + Noosphere Aug 18, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
Subconscious + Noosphere
Status: 🌱 Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Manage cache validation by comparing version CID subconsciousnetwork/subconscious
1 participant
@cdata