Replying to Avatar sommerfeld

My thoughts are to iust enable the bridge on repos that already voluntarily signaled a nip34 repo annoucement.

There should be an easy clear way for them to opt out of the bridge (weird decision, if they already enabled nip34 but ok, won't blame them).

After that, we can think of how to do better spam prevention (only mirror "qualityx npubs, etc).
Avatar
DanConwayDev 1y ago

I originally thought projects should have to opt-in to being bridged to github.

I'm not keen for gitworkshop.dev or ngit to be bridged to github.

perhaps maybe it could be opt-out for projects which list github first in the the 'clone' attribute of their repo event?

Reply to this note

Please Login to reply.

Discussion

No replies yet.