Lol. I don't know how nostr:npub17u5dneh8qjp43ecfxr6u5e9sjamsmxyuekrg2nlxrrk6nj9rsyrqywt4tp marked the images as sensitive. Maybe in the image metadata? 😆

Apparently the nevent is wrong?

Something went wrong

Invalid checksum in

nevent1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgnwaehxw309ahkvenrdpskjm3wwp6kytcpr3mhxue69uhkyatrddjhgtnrdaexzcmvv5h8xmmrd9skctcppemhxue69uhkummn9ekx7mp0qyg8wumn8ghj7cfwdehhxtnvdakz7qgewaehxw309a5x7ervvfhkgtnwdaehgu339e3k7mf0qy08wumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wshszymhwden5te0wp6hyurvv4cxzeewv4ej7qpqm8yx6u92c3gylgz4flv6h8xlxxrwduhy8wgvpmh6ejvtyhwl4: expected "e60ger"

NoStrudel doesn't render OPs embed. :(

nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr these images should probably be blurred ;)

Udi is a lost case since years. nostr:npub1mxrssnzg8y9zjr6a9g6xqwhxfa23xlvmftluakxqatsrp6ez9gjssu0htc though ... I had not realized he was a lost case before the ordinals stuff. 😟

That's what I had tried once, too. The worker would get requests to get further events and store them locally and all the tabs would just watch the indexedDB for new stuff to show.

I can't stand sharing a room with loved ones that have headphones on and I avoid looking at my phone when my daughter is around. I'd sure as hell not be that dad.

If they started wearing such masks, this is the mask I would get:

I'm disturbed by otherwise sane humans working on this crap. The fee spikes will blow over but these people ... are kind of lost cases for anything serious now.

The french know how to protest.

Sadly that nip was rejected but mainly because it's not an implementation possibility but merely a reminder.

It's one thing to not read kind3 relays but to write kind3 destructively ... is evil. https://github.com/Giszmo/nips/blob/protectTheUnknown/24.md

I see a lot of Bitcioners hatching this way.

Twitter is dead, too. They just don't know it yet.

There is clients that "work" the old way, with the dev havin no spare resources for this, so they won't fix it. For the sake of a good standard, clients should not support old standards but users will blame the clients that don't find their relays for being buggy, so client devs will add this interoperability.

Yesterday or so I saw there's a project that documents what client doesn't play well with another client. This kind on project can give the users a perspective on who's at fault here.

Maybe we will have tools to upgrade profiles so clients can just implement the current nips and not care about legacy support across all of them.

I only let two sign events using one extension. That's how early we are :D

As probably having filed more client issues than anybody else, I wonder why people don't file more issues. Client devs tend to be very well receiving.

All of these issues should be filed with one or both of the projects involved. If both close them as "not a bug" because they can't agree on a standard, then yes, making public that A doesn't play well with B might help to find better standards or discuss more publicly who's at fault. If 90% side with client B, maybe A reconsiders but that could happen on nostr social instead of a GitHub issue tracker.

Bounties can discourage those who would have done the work anyway as people work a lot behind closed doors and when it fails to attrackt good mercenaries, it can be a net negative overall. This is why I'm trying to push people into the light and to collaborate instead of just racing towards something nobody knows if it's a valid finish line.

In this case here, a bad outcome would be a "polished" product where the mercenaries themselves couldn't be bothered to dig back into the mess they left on the code side of things. Therefore I think protocols are more important than products and don't quite understand why fiatjaf disregards nip34's importance for the bounty.

Estoy usando GitHub un montón pero dado que el Español no es mi lengua materna, no hago traducciones.

That works when you have your funding secured but with a bounty I feel like several teams might be flying blind.

Wouldn't it be sad to have some 8 projects work behind closed doors for years when one of them decides to release to claim the bounty. Now the other 7 rush to get in line with whatever they have to offer as there is no deadline to the bounty, so as soon as any project looks half promising, any team with a perceived better product will have their hands forced or miss out on the reward for good.

I would prefer to have all teams work transparently and I would trust the bounty to get split fairly if some project with great ideas and devs abandoned their code to work on another project.

Yeah, well, it's been some time. Let's all work in the open and pool our brain power. I hope nobody bullshits Jack into giving the bounty to anything but the most deserving people. I would love to see teams to pool forces and then agree on how to split funds instead of one beating the other.

And for the record, I'm not in the race for this bounty. I'm just enthusiastic about seing GitHub dethroned in a much more cypherpunk future where unstoppable code gets developed by shadowy supercoders.

PSA: If you are on NoStrudel and wonder why you don't see replies to your threads in the notifications, that's because that's only available in the "next" version. Try it out now at https://next.nostrudel.ninja/#/notifications/threads

Unless you are talking about intellectual property ... nip34 or ngit should work using separate npubs via VPNs or TOR. What am I missing?

Yes, all what's proposed is for brutally transparent development, only but you can hide your ID.

I bet whatever works best will take the world by storm. Developers love trying out new things.

Whatever wins, I hope it fixes discoverability so when I next shop around for developers I will not have to check their portfolios exclusively on GitHub. I want some "ngit search npub..." to find all the projects that npub contributed to regardless on which servers and including the patches that were not hosted on forks of projects.