You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Overview
For troubleshooting purposes it would be helpful to know on which client an update to the contact list occurred. This will help us measure whether Nos is overwriting contact lists or if it's some other app. NIP-89 has a spec for a "Client Tag" that we can use.
AC:
Add the client marker to each content and account flag posted from Nos to say that it came from Nos.
The text was updated successfully, but these errors were encountered:
From our meeting today: closing as a dupe of planetary-social/nos#1455 (even though the title was talking about moderation, this was supposed to be about contact lists)
It occurred to me while implementing this that once we publish a contact list with the Nos tag, other Nostr apps may preserve that tag when they publish new versions of the list.
To mitigate this I added code to fire a new "Published Contact List" analytics event as well. Now if our server-side alert goes off we can check Posthog to verify whether the event that overwrote the contact list was actually published by Nos or not.
Overview
For troubleshooting purposes it would be helpful to know on which client an update to the contact list occurred. This will help us measure whether Nos is overwriting contact lists or if it's some other app. NIP-89 has a spec for a "Client Tag" that we can use.
AC:
The text was updated successfully, but these errors were encountered: