Live data from Hacker News

Gitstr: Send and receive Git patches over Nostr

github.com

41–50 of 63 posts

Re: Gitstr: Send and receive Git patches over Nostr

#41

Earlier quoted context omitted.

> I'm not sure a social media without censorship is viable on large scale Right, it absolutely isn't. Some form of censorship is vital. This claim becomes more agreeable when substituting "censorship" with the almost-synonymous word "moderation".

Nostr's idea of "moderation/censorship" is quite simple: you (or your relay admin) can drop whatever content you don't want to see or promote. It's no different than email servers, and (as a system) it works just fine even if you are surrounded by bad actors.

Wait, this is just ActivityPub with extra steps. Why not just use Mastodon?

Re: Gitstr: Send and receive Git patches over Nostr

#42
post #40
post #5

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.

Nostr can be thought of as an open, decentralized, censorship resistant messaging layer with a built-in micro payments system. Regarding why this might be useful. Remember when youtube-dl got taken down from GitHub? I think it’s now back after all the outcry. But the point stands, if you develop something that someone powerful might not like, a Nostr based git solution for that might make sense.

Or, you know, just email the patches.

Re: Gitstr: Send and receive Git patches over Nostr

#44
post #3

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

And no token. Many token scammers try to sell their token as part of a new social network. This project doesn’t sell a token

Re: Gitstr: Send and receive Git patches over Nostr

#45

Earlier quoted context omitted.

Nostr's idea of "moderation/censorship" is quite simple: you (or your relay admin) can drop whatever content you don't want to see or promote. It's no different than email servers, and (as a system) it works just fine even if you are surrounded by bad actors.

Wait, this is just ActivityPub with extra steps. Why not just use Mastodon?

The main difference with Mastadon is tha with Mastadon you have a single node that you get your federated feed from, and that verifies your identity. Therefore if your node operator doesn't peer with some other node, you wouldn't automatically be able to communicate with users on that node.

With nostr, your identity is just a pubkey, and you can publish to / read from several nodes simultaneously. So if some node refuses to puplish certain content, you can just get it from another node without having to create a whole new identity.

Re: Gitstr: Send and receive Git patches over Nostr

#46
post #40

Earlier quoted context omitted.

Nostr can be thought of as an open, decentralized, censorship resistant messaging layer with a built-in micro payments system. Regarding why this might be useful. Remember when youtube-dl got taken down from GitHub? I think it’s now back after all the outcry. But the point stands, if you develop something that someone powerful might not like, a Nostr based git solution for that might make sense.

Or, you know, just email the patches.

That’s a fair point. In the current iteration there’s not much functional difference.

The vision though would be to build something that feels a lot like one of the centralized git services, just built on top of Nostr. So, it’d be some kind of a frontend that you may be able to run yourself if it’s open source which you could point to a set of relays to get the ‘git notes’ from. Couple this with the integrated payments functionality, and I think it becomes an interesting proposition.

If I recall correctly some time ago Jack Dorsey pledged some amount of BTC to make that a reality.

Re: Gitstr: Send and receive Git patches over Nostr

#47
Why would anyone want to use an inefficient complicated network to send a Git patch rather than sending it over email, using Git integrated workflow?

What I'm actually eagerly waiting for is GitLab instances being able to federate using ActivityPub, allowing remote forks and auto-updates, merge requests, issues opening and commenting, following users and projects… all that without having to open an account per instance.

See https://docs.gitlab.com/ee/architecture/blueprints/activity_...

Re: Gitstr: Send and receive Git patches over Nostr

#48
post #43
post #4

This is dope! Very cool to see more Nostr applications that aren't just Twitter clones.

https://www.nostrapps.com/ has quite a few non-twitter clones to offer.

all of these seem to be Twitter-like social apps. what am I missing?

Re: Gitstr: Send and receive Git patches over Nostr

#49
post #25
post #5

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.

> Nostr really feels to me like the blockchain That’s not strange, given that it’s architecturally similar. However, blockchains are solving global consensus problems. Nostr doesn’t give a shit. To me, that’s good. One piece at a time. Also, what’s so important about consensus? It’s extremely slow and expensive and mostly matters for financial applications. The less financial speculation the better, imo. Time will te…

In what ways is the architecture similar? As far as I can tell, the only similarity to Bitcoin is that it is a "permissionless" protocol. Any relay can participate in Nostr, just like any node can participate in Bitcoin.

Re: Gitstr: Send and receive Git patches over Nostr

#50
post #10

Earlier quoted context omitted.

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.

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.

Except once instances block other instances for not going along with their blocks. Then you really cannot talk to anyone from a single idenity. This makes the whole system not much better than a bunch of independent sites.

Then there is the fact that you once you choose an instance your identity is bound to that instance. Why would anyone invest in such a dead end network.

Post reply on HN