Replying to Avatar DanConwayDev

I completely agree and would like to see this added to gitworkhop.dev and it is on the list of functionality definately to be added. it hasn't reached the top of the list because users receive notifications in other clients are you mention.

I would see these as coming under usecase 3 as you should be tagged in those events.

nostr:nevent1qvzqqqqqqypzpgqgmmc409hm4xsdd74sf68a2uyf9pwel4g9mfdg8l5244t6x4jdqythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qy88wumn8ghj7mn0wvhxcmmv9uqzpwh65jc27eu74euum9wstkqqfmt38pffgkhd57jufhlcw9mslz5dcgtw4m

I have considered either storing read activity locally or publishing them in encrypted events but this would leak metadata (when you are using git over nostr.

Avatar
Silberengel 1y ago

I would just do it locally. It's not really "important" data, that needs to travel between applications. Npubs will be able to use the ⭐ bookmarks, to favorite individual events, which seems like the more critical data.

Reply to this note

Please Login to reply.

Discussion

No replies yet.