[HN Gopher] Gitstr: Send and receive Git patches over Nostr
       ___________________________________________________________________
        
       Gitstr: Send and receive Git patches over Nostr
        
       Author : jgilias
       Score  : 36 points
       Date   : 2024-01-30 19:34 UTC (3 hours ago)
        
 (HTM) web link (github.com)
 (TXT) w3m dump (github.com)
        
       | jgilias wrote:
       | This is not a ShowHN, as I'm not the author. I just find the
       | concept really cool!
        
       | Karellen wrote:
       | > Nostr is a decentralized network protocol for a distributed
       | social networking system. [...] It was designed with goals of
       | censorship-resistance in mind.
       | 
       | https://en.wikipedia.org/wiki/Nostr
       | 
       | (Because the linked page doesn't describe/link to a description
       | either, AFAICT)
        
       | kevinak wrote:
       | This is dope! Very cool to see more Nostr applications that
       | aren't just Twitter clones.
        
       | RIMR wrote:
       | Nostr really feels to me like the blockchain: An incredible novel
       | solution desperately in search of a problem to solve.
       | 
       | The engineering behind this is neat, but I have no idea why this
       | is useful.
        
         | pjfin123 wrote:
         | Nostr is the only payment network I've ever used that lets you
         | send payments of less than $0.10.
        
           | gkbrk wrote:
           | Nostr is not a payment network. You probably used Lightning
           | instead.
        
             | RIMR wrote:
             | Bitcoiner "understand what you advocate for" challenge
             | (impossible).
        
           | RIMR wrote:
           | Nostr really feels to me like the blockchain: Nobody that
           | advocates for it understands what it is or how it works.
        
             | evbogue wrote:
             | Bitcoin uses secp256k1, Nostr uses secp256k1. I was
             | surprised as anyone to learn that when you exchange money
             | using Nostr clients it is not directed at the private key
             | that you use to sign Nostr messages.
        
               | RIMR wrote:
               | I cannot say that I am surprised at all to learn that you
               | were sending and receiving Sats over the LN with zero
               | understanding of what keys were actually associated with
               | your funds. This is exactly the level literacy I expect
               | to see of anyone dealing in cryptocurrency.
               | 
               | Is there a reason to think that two different keys for
               | two different protocols are actually the same key just
               | because they use the same ECDSA? Not if you possess even
               | a modicum of understanding of cryptography, but I
               | digress, we are talking about Bitcoiners after all.
        
               | seanw444 wrote:
               | Your condescending bone-to-pick attitude about people
               | using cryptocurrency is kind of cringe.
        
               | crotchfire wrote:
               | I'm surprised by this too.
               | 
               | Bitcoin was developed just barely before ed25519 was
               | finalized, which is probably why it uses secp256k1.
               | Unless intended mainly for government users (FIPS),
               | almost every new cryptographic system uses ed25519 --
               | _except Nostr_.
               | 
               | I always assumed Nostr chose secp256k1 so you could send
               | bitcoin to another Nostr user without some extra "payment
               | address request protocol" bolted on the side. Very
               | surprising that this was not the motivation!
        
         | ecf wrote:
         | Nostr is everything that fediverse social networks claim to be,
         | but aren't.
         | 
         | I was shocked to find out that the Lemmy instance I signed up
         | on was blocking dozens upon dozens of other instances, which
         | defeats the entire purpose of a federated network.
        
           | AlphaCerium wrote:
           | Then switch to a different one, the point of a federated
           | network is that anyone is able to talk to anyone, not that
           | they have to.
        
             | ecf wrote:
             | You must realize that the moment you say "just switch to
             | another" you've lost 99% of your potential user base.
             | 
             | It took me signing up for Lemmy to realize why Lemmy is
             | still a completely dead network.
        
           | RIMR wrote:
           | This is a strawman argument. The biggest advocateds of
           | federated social media are not promising a fully
           | decentralized and censorship-proof network. Federation is
           | built on trust, and blocking untrustworthy instances is a
           | critical function of any open federated system.
           | 
           | There is another side of the Fediverse that operates on the
           | principles you are talking about (eg. Poast, Baest, Spinster,
           | Gleasonator, NoAgendaSocial, NicecrewDigital, et al). That
           | part of the Fediverse, like Nostr, is covered in Lolicon,
           | gore, and Nazi memes because that's the userbase you get when
           | you promise that nobody can stop you from posting whatever
           | you want.
           | 
           | More and more I am learning that the people who desire
           | censorship-free social spaces are the kind of people that
           | others rightfully exclude from polite social spaces, because
           | these are people who lack respect and want to say and do
           | horrible things without opposition.
        
         | poulpy123 wrote:
         | I tried nostr and I was impressed by how fast it is compared to
         | the alternatives and by how seamless it is to connect to
         | everyone. Unfortunately I'm not interested by the current
         | content and I'm not sure a social media without censorship is
         | viable on large scale
        
         | Nzen wrote:
         | I found Ryabitsev's 2019 meditation [0] about maybe using git
         | with secure scuttlebutt interesting (though not terribly
         | compelling). Ryabitsev's fantasy scenario involves a developer
         | exchanging git patches for a particular project via phones, to
         | a laptop. Because that person uses secure scuttlebutt, the bug
         | tracking thread is part of the enabling software, rather than
         | out of band. I am of the impression that Ryabitsev's history as
         | mailing list manager and software patch attestation more likely
         | informed this dalliance than typical web3 inroads.
         | 
         | [0] https://people.kernel.org/monsieuricon/patches-carved-
         | into-d...
        
       ___________________________________________________________________
       (page generated 2024-01-30 23:00 UTC)