Can someone provide me with an #Alby invite?
I’ve seen so many people say they won’t use Nostr because we don’t support delete. This is really frustrating, because Nostr DOES support delete, it’s right there in the NIP’s! We’ve got delete in nostr:npub1pu3vqm4vzqpxsnhuc684dp2qaq6z69sf65yte4p39spcucv5lzmqswtfch, but most apps don’t expose the functionality to users because they either don’t like the idea of delete or can’t be sure that something is 100% deleted. That misses the point, delete is as much about social signaling as it is about getting rid of the content.
Here’s my argument for how we should think about and support delete in nostr. In case your client doesn’t support long form content, here’s the njump link: https://njump.me/naddr1qq2ksje3g9trxujpxymyxjjlg5ckjmmrtguyxq3qpu3vqm4vzqpxsnhuc684dp2qaq6z69sf65yte4p39spcucv5lzmqxpqqqp65wk06e7u nostr:note1hldm4z430w76dn2ywzwjnafytnvyt7gsg6nhk3l8a3x8utzl88asl06u8m
It‘s rather an update of the content, right? Replaceable with an excuse.
I’ve seen so many people say they won’t use Nostr because we don’t support delete. This is really frustrating, because Nostr DOES support delete, it’s right there in the NIP’s! We’ve got delete in nostr:npub1pu3vqm4vzqpxsnhuc684dp2qaq6z69sf65yte4p39spcucv5lzmqswtfch, but most apps don’t expose the functionality to users because they either don’t like the idea of delete or can’t be sure that something is 100% deleted. That misses the point, delete is as much about social signaling as it is about getting rid of the content.
Here’s my argument for how we should think about and support delete in nostr. In case your client doesn’t support long form content, here’s the njump link: https://njump.me/naddr1qq2ksje3g9trxujpxymyxjjlg5ckjmmrtguyxq3qpu3vqm4vzqpxsnhuc684dp2qaq6z69sf65yte4p39spcucv5lzmqxpqqqp65wk06e7u nostr:note1hldm4z430w76dn2ywzwjnafytnvyt7gsg6nhk3l8a3x8utzl88asl06u8m
Maybe there should be a „regret“ button instead 😝
Please elaborate. What‘s inherently bad about FTP? That it‘s an active protocol?
You should talk to Scott Chacon. He‘s rethinking Git based on CRDT (https://en.m.wikipedia.org/wiki/Conflict-free_replicated_data_type). The idea would be that you could merge Git and GDocs editing processes. He just open sourced his main project today: https://github.com/gitbutlerapp/gitbutler
I suggest, we use nostr instead of alert.swiss? #Switzerland 
Then how do you learn what it takes to bring something upstream? We for example encourage our interns to propose changes to open source projects. There is a lot to learn there about how to do things properly. All assuming you don‘t treat GitHub as if it was a GDoc or CMS.
I understand that this might be a controversial opinion, but I believe that new developers should not contribute to established open source projects. It only makes the lives of open source project managers more difficult.
If a developer cannot understand the basics of full code base, they should not contribute. This practice is essentially turning into spam and is akin to a DDoS attack on the open source community.
Many open source projects are considering going closed source due to this exact reason. People with little to no coding knowledge are literally practicing on main ExpressJS repo. What a nightmare for these project managers.
https://video.nostr.build/84049a473935a18ab66e30c582f7ea7adb1dfb23ff461d1504dac7194a9f0a2f.mp4
I like if there are automated tagging and assignment policies, which for example depend on linters and tests. So newbies can still open a PR, but maintainers can actively choose whether to look at it.
Oh yes, and we deployed in milliseconds using Ctrl+S in the Notepad++ FTP plugin!
You’re right, that’s wishful thinking. Seriously now, the JS build system is horrible. I hate my node_modules folder and cryptic webpack configurations with all my guts.
But also it was worse: remember gulp? Today we‘ve got importmaps, JS gets more TS features built-in, TailwindCSS brings us alternatives to hunky CSS files and much more. I hope,
