Subnostr

Item 4 is already in our backlog—we plan to add anonymous publishing.

As to the others, we can create tickets for those.

nostr:npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5 I put them in two tickets

https://gitcitadel.com/r/naddr1qvzqqqrhnypzplfq3m5v3u5r0q9f255fdeyz8nyac6lagssx8zy4wugxjs8ajf7pqy88wumn8ghj7mn0wvhxcmmv9uqq5stvv4uxzmnywf5kz2elajr/issues/note12wkd0whdqgny9j33n64zuxqg4p8rq8qg32wncw4gj5tesjnk9vgqe5dfut

https://gitcitadel.com/r/naddr1qvzqqqrhnypzquqjyy5zww7uq7hehemjt7juf0q0c9rgv6lv8r2yxcxuf0rvcx9eqythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qq9yzmr90pskuerjd9ss38emv9/issues/note1wj6z0n932lem6g40h49qknmlrm8e06jkgj0k8jy8zjcx8qlujeus5prnfc

Reply to this note

Please Login to reply.

Discussion

elsat 10mo ago

💪

Noticed in the comments in links above you mention issue # e.g. 200. Are you tracking in multiple places?

MichaelJ 10mo ago

We have a OneDev instance on which we host our repos and track tickets. Using it requires creating a login, so GitWorkshop is better as a public-facing tracking tool.

Silberengel 10mo ago

Yes, we list the OneDev issue in the Nostr issue and vice-versa. That way we have traceability. And, later, they'll be automatically linked.