TIL: In GitHub, the creator of a PR can block the owner of the target repository from commenting. WTH?

https://github.com/isaacs/github/issues/1570

A fidelity bond is some locked-up funds that you lose if you do bad stuff.

nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 the supporter subscriptions come supposedly with a badge. Two issues there:

* Where is my badge?

* How can I upgrade to the other tier? When I now go to the subscriptions page, it only shows me that I have 28 days left with my current subscription but no hint at how to upgrade.

Given it was taken (I was told) and nobody replied thanking for it, I assume there is bots now that collect free stuff on nostr. It was taken instantly actually.

Who wants some cashu sats? It's 100 I was told ...

cashuAeyJ0b2tlbiI6W3sicHJvb2ZzIjpbeyJpZCI6IkkyeU4raVJZZmt6VCIsImFtb3VudCI6OCwiQyI6IjAyYmY4ZGFkZjA5MDVjYjZlNzIzNmNmOTFhNmY0NDZiMjU3OGYwMWIyOGEwMGU0MzcwNmI4ZWRiNmRiODUwMDM1ZCIsInNlY3JldCI6Ii9sejlDUkVkbC9MSXVTVEFpNDV1L1F0SSttNStTbC9JZ1RHc1Zpc0NjNEU9In0seyJpZCI6IkkyeU4raVJZZmt6VCIsImFtb3VudCI6NjQsIkMiOiIwMjMwMDU5N2NlMWRmYjU1MTNkNmI5MGJjYTY2MzQ4NjhkMWM0YjA4NDViOTkwOTMzNzEyMjE3NmMyMmRiNmI1NjUiLCJzZWNyZXQiOiJSR3cyRFMyNjlUL3BoVk9HZEhmcmphK1lEQVVQTzk5U0I4ME9VSnF4bERZPSJ9LHsiaWQiOiJJMnlOK2lSWWZrelQiLCJhbW91bnQiOjEyOCwiQyI6IjAyYTY3Yjc1M2JiZjAzNWQ5ZDQ0ZTkwNzIzYWExNTdjMDcwMmM1NzBiYmJiMjlkNzA0ZWEwZjBiZmRhMDRlYWRhOCIsInNlY3JldCI6IlFBVUZ5R21nazBEVmFDRGYwNGJjNG4rbm5FckdxQlcyRzZhOGtGdU1Ka2c9In1dLCJtaW50IjoiaHR0cHM6Ly84MzMzLnNwYWNlOjMzMzgifV19

The rule for acceptance currently is that it needs to be implemented in two clients and a relay (if relevant to relays). There are libraries, so of course many aspects are quickly adopted in the libraries, too.

Currently clients support all different sets of features and do things differently. But I would say that's acceptable. Let them experiment and eventually they will converge doing things more similarly.

How to aggregate a bunch of 👍 and 👎 into a verdict?

I would love to open up to multiple reviewers suggesting a verdict but currently I'm even behind myself in terms of validating builds and have little hope to get more people to build wallets. But even if people did, what would I make of it? The provider might have some sock puppet accounts that just claim whatever. I have little hope to get the most trusted users to review products that are not their own.

Instructions usually are not very specific, so they might just assume your OS and version and installed apps. "Hit compile in your IDE".

For WS verdicts I think it's no big deal to give them a "ftbfs" verdict meanwhile they make their instructions more specific.

How can I find this plugin? Link please!

If only more people would care to try to build. Sadly most blame themselves when they fail and don't even dare to open an issue to resolve what they couldn't figure out.

I was in charge of an Android Bitcoin wallet for several years. My stance is:

* The bar is "reasonably technical person"

* I'm above that bar

* If I fail, a negative verdict is warranted

Probably should spawn a sock puppet to say this but that chart looks not exciting at all. It looks linear in the zaps and constant in the zappers/zappees.

#[1] good luck with this one! May many plebs give you the resources to build an even more awesome product!

Any plans on hiring people if you achieve amount X? Any commitments to keeping stuff open source? Any plans to push for a multi-account nip-7 extension?

For me, it's "Coming soon". Slow rollout?

https://void.cat/d/VybUiAiUCBFWyt1oKLSVLQ.webp

I have a question about the multi-account support: nip-07?

Noob friend sent his sats to his Binance app on iPhone to sell them for CLP. He didn't understand anything and sold them for USDt instead of figuring out the "Binance P2P" market where he could sell to Chilean bank accounts. Now he has no idea how to buy back BTC to sell them to me or how to withdraw his USDt in case I can find him a buyer.

He sent me his credentials but the website wants me to authenticate using a registered security key which he has no idea about.

🤦‍♂️

https://twitter.com/LeoWandersleb/status/1646727949079523333

you win! 😃

I was alluding to the possibility to write a bot that gives you a new follower every hour.

I could see notifications for people that follow you back but randos following you is just noise.

Not sure why he's singling out notifications as a problem on decentralized apps though ...

Yeah? I'll have a bot notify you once per hour. Any preferences for the usernames and avatars?

* reference: Some clients and by far not all do understand nip-21 urls referencing nip-19 bech32 encoded public keys such as `nostr : npub...` (without the spaces).

* mention: All social clients understand `# [0]` as a mention of that pubkey in the first tag (index 0).

Currently, clients wildly differ in how they show mentions/references during editing. Most assist in finding your follows when you hit the @ key and start typing and show you some `@ npub...` but once you send, they replace it with some `# [index]` and add the actual pub key in the tags. Producing references is currently not well supported in any client I know of but you can always find the `npub` and prepend it with a `nostr:`