mikedilger on Nostr: Conductor (related to Chorus) Every few days somebody posts an "Introducing ___" note ...
Conductor (related to Chorus)
Every few days somebody posts an "Introducing ___" note to nostr, where they tell everybody about their new project that they have been working on for ages and finally have released. These are exciting and very cool.
I'm a little different. I'm gonna tell you want I'm working on before it is ready.
For a couple weeks I've been working on a web application called "conductor" (like that guy who swings a baton at an Orchestra). It is a relay management tool using NIP-86. I know there are a few others in development by other people, but it was time for me to get better at writing web applications and it seemed like I could get one working in just a few days (after the first day I felt like I was halfway there). Also, being the chorus developer I can adjust both sides until it does all the right things, which makes it easier to make progress.
In the process of developing conductor, I ran into issues with chorus and AUTH and have worked to get them resolved.
https://github.com/nostrability/nostrability/issues/163
https://github.com/nostr-protocol/nips/pull/1778
https://github.com/nostrability/nostrability/issues/167
Also, a number of breaking changes had to happen to chorus (such as moving user configuration into the database so it could be dynamic) prompting me to prepare towards releasing a Chorus 2.0 which requires a small amount of migration. This is not ready yet, I'm just telling you what I am in the middle of doing.
Conductor will start out very basic, and while it will work with chorus relays it might not work with other relays as NIP-86 might not have the commands I was interested in. It won't work with 1984 reports yet either (but that is coming). It will just allow approving (or rejecting) events and pubkeys that haven't been approved yet using the same scheme chorus already uses with the `chorus_moderate` command. I will release it when this is all it does. I will release it again once you can manage users with it. And I will release it again once it handles 1984 reports too. One step at a time.
Every few days somebody posts an "Introducing ___" note to nostr, where they tell everybody about their new project that they have been working on for ages and finally have released. These are exciting and very cool.
I'm a little different. I'm gonna tell you want I'm working on before it is ready.
For a couple weeks I've been working on a web application called "conductor" (like that guy who swings a baton at an Orchestra). It is a relay management tool using NIP-86. I know there are a few others in development by other people, but it was time for me to get better at writing web applications and it seemed like I could get one working in just a few days (after the first day I felt like I was halfway there). Also, being the chorus developer I can adjust both sides until it does all the right things, which makes it easier to make progress.
In the process of developing conductor, I ran into issues with chorus and AUTH and have worked to get them resolved.
https://github.com/nostrability/nostrability/issues/163
https://github.com/nostr-protocol/nips/pull/1778
https://github.com/nostrability/nostrability/issues/167
Also, a number of breaking changes had to happen to chorus (such as moving user configuration into the database so it could be dynamic) prompting me to prepare towards releasing a Chorus 2.0 which requires a small amount of migration. This is not ready yet, I'm just telling you what I am in the middle of doing.
Conductor will start out very basic, and while it will work with chorus relays it might not work with other relays as NIP-86 might not have the commands I was interested in. It won't work with 1984 reports yet either (but that is coming). It will just allow approving (or rejecting) events and pubkeys that haven't been approved yet using the same scheme chorus already uses with the `chorus_moderate` command. I will release it when this is all it does. I will release it again once you can manage users with it. And I will release it again once it handles 1984 reports too. One step at a time.