Well I guess the other issues have been assigned, so we can do it individually.
I think it would be simpler to just provide a fake secret for local testing. It would only blow up when receiving a webhook, which would never happen.
Looks pretty good, but I'd like something a little lighter. What about something like the attached, and when you click on the pinned message it scrolls to that message and updates the x/y number…
This exists already in @welshman/lib
This is redundant with deriveSupportedMethods in core/state.
Instead of re-exporting, update imports
Instead of re-exporting, update imports
Instead of re-exporting, update imports
Instead of re-exporting, update imports
This looks very good, nice and organized. Just a few comments.
This follows the old spec which used nip 85 assertions, see this comment for the updated design. Also, I'm happy with the old rendering, keep that as is, just change the score calculation.
