It's simple to implement: sarcastic notes SHOULD always be rendered in Comic Sans regardless of system configured fonts.

No takes me seriously whenever I propose it, they just think I'm being sarcastic. Which just showcases the problem

You didn't use the '/s' tag signaling a sarcastic note. 10 points penalty

Complyoors also get rekt sooner or later, difference being without any honor.

nostr:nevent1qqsd6lvhdtmxnpn4ytxvx48mglzdr43uryh3lqapznl56hxdm4d9uvspgdmhxw309ahhsarjv3jhvctkxc685d35093rw7pkwf4xwdrww3a8z6ngv4jx6dtzx4ax5ut4d36kw6mwdpa8ydpkdeunyutzv9jzummwd9hkuq3qhxjnw53mhghumt590kgd3fmqme8jzwwflyxesmm50nnapmqdzu7sxpqqqqqqzq7md0l

You're right, PRs are much more complex to mirror, although I still think it should be possible.

If someobe creates a PR on nostr, it could be mirror by a PR created by the bot (which would have permissions to push to its fork). It's hard, but doable.

Let's start with Issues only...

Web of Trust

I don't even understand the incentive of sucking his dick so hard. Do his simps just think that if they do it for long enough, he will notice them and give them free money?

If true, I can't think of a saddest existence.

My repo uses my personal git server as primary, github as a mirror: https://gitworkshop.dev/repo/sentrum

If people mainly use GH for the social aspect and we can steal that with nip34, I believe people will naturally use other git servers since they won't depend on GH so much anymore.

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).

I have heard about nostrocket on your pod. Great idea albeit ambitious.

I just checked the spec for NIP-1971 and it looks more like a replacement for complex issue tracked used internally within companies (like Youtrack, altassian, jira, zendesk, redmine) more than GH issues (which are rather simple).

Would love to see it to fruition! For now I will focus on bridging NIP34 events, gotta start small.

Looks interesting but is it bridging github with nip34 events?

I have nothing yet, this is just something that has been brewing on the back of my mind while I take a shower.

I just think repo maintainers have no incentive to manage 99% of issues on GH and the rest on nostr. That won't work, even if they like nostr, managing 2 separate issue trackers is a big no.

I want to create a nostr-github bridge bot: if you open an issue/PR on nostr, it should be seen on GH and viceversa.

Bridges are essential to foment smooth adoption. Why pick one or the other when you can have both...

For people using clients that can't display the above event: https://gitworkshop.dev/repo/ngit/issue/826a6a8b5cd202072d7a652c0ae21577618ee167d2dc2f45b112f943cf9ce49b/

Just opened my first git issue on nostr

nostr:nevent1qqsgy6n23dwdyqs894ax2tq2ug2hwcvwu9na9hp0gkc3972re7wwfxcpzamhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuegzyrgda0ulkyk7lq05847xjs5mk7zgz2kpunfd2w3q9km243l2fdrxcqcyqqqqv4g4xn7v6

> Kill your heroes

If Saylor was ever your hero, you seriously need to reevaluate all your life decisions.

True, didn't even think of that!

Europeans don't know what a "mile" is

Who's stopping you?

Forget about the red , orange or purple pill. The dark pill will never disappoint you...