I will do that, but imo it makes some pretty bad UX if the relay loses livekit support. Either we silently convert voice or voice + text rooms to text only on edit, which may not be what the user…
Ah, ok. I think you mentioned including the tag on the update event in a comment on the proposed NIP too. I was very confused but now I see that you always try to publish a kind 9007 room create…
Ok cool. Can you explain why you prefer Maybe over typescripts built-in optional type? Is that a pretty universal preference for you?
@hodlbod I'm ready for a review of the code/direction here and for some input on how you want to ship this. It's not done but I think enough is done for it to be useful so we could merge and ship…
Ok this cascaded into more changes than I wanted but I think I fixed a pre-existing bug with the logo download too. I have been shipping shipwreck.scuttle.works using this Dockerfile for a few…
This fixes an issue I had with setting the logo. You could configure the other vars in .env because npx reads that automatically but the logo was being read here and wasn't respecting .env.
The old curl command was failing silently for me so this one will fail the build if the logo URL exists but the logo cannot be fetched.
I changed this to a two-stage docker build mostly because include .env in an image seems dangerous even if none of the env values are secrets at this time.