Avatar
Guga Figueiredo
e07e6c1351e07c837b1feb6c3624173c6b3f13e40d75f8e4ebd69fff0739c1c7
Super user philosophy

YES!!! This is awesome! My dream stack is almost a reality!! Lets go Nostr!!!

Thanks for bringing this to my attention!

I'm adding nostr:npub1swrmxnc67rs3gp392gcrc0mme2mupt9ux53jy5lzyurtpt3tyd8s5d73v6 to my watchlist!!

I do think the zap culture is a positive thing though. it shifts the incentive forces from ad-revenue and private funding to consumer centric incentives. I feel like that's why it's so talked about and why people get excited about it.

Let me hear from you guys. What are the most exciting things happening in nostr for you? Whos is building the future you want to see on nostr?

#asknostr #pollstr

nostr:note1fysth6ludaunzpnqxe6ndm6xqvv72w6wh2n6m2z657tul4hzeyws26w8e4

I might be on the conservative side regarding this. PRs are not first class citizens in git. so an integration of nostr+git doesn't need to have PRs.

I want to be able to work with git and nostr side by side. I see clear benefits in decentralization just by reducing friction for handling git server/service migration. And don't want to see nostr native repos become incompatible with regular git ones.

most of all, I like the idea that there are layers in the solutions we are exploring, and I'm hesitant to have protocol definitions across many layers. I don't think every good idea about how to do things in nostr need to be a protocol spec. it incentivizes gatekeeping and hinders flexibility. taking us closer to how centralized solutions work.

I am working on some ideas to improve the remote-helper I've made. Should have an update soon.

That is mixing git workflows and git service functionalities with core git commands, is that right? if I understand correctly, I don't know how I feel about that. my instinctive response is that pulling/pushing code should be all that the transport protocol should care about.

And I think there are more things we can do with nostr to improve UX working with git remotes hosted over nostr on that front, before thinking about adding overhead with what I consider is more a UI concern.

So what are we gaining by adding nostr to that flow beyond the ability to find the server?

My thinking has been going towards doing that server side, for the purpose of providing frontend functionalities, notifications, but that would have no bearing on the remote-helper transport for pushing/fetching.

I understand the concern over centralized servers, but all these refs flying around notes make me concerned about eventual consistency. isn't it enough to setup mirrored servers, that can be tapped into if one of them is compromised? Shouldn't the code owner be the one responsible for that?

if we are going to duplicate refs on nostr events, we are bringing git concerns to nostr events.. once a connection is established with a git remote-helper, git is the one listing refs in the server, and we are going to have to keep the server we are connecting to consistent with the notes we are serving on nostr

what prevents malicious notes from creating false refs, in that communication?

oh, hi! yes. that would be awesome!

I had already started working on this when I first became aware of git workshop.dev and your other projects a little while ago.

I would really appreciate the opportunity. I mostly want people to try it out, see what it feels like and what is missing/desired from such a tool, if at all.

Powerfull speech. But I trully believe the days of central government and elected representatives as we know it are numbered. Even if I believed nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m or even yourself would push all the right ideas into that system, I don't think that is the future we are moving towards.

Anybody else got a dream nostr stack on their mind? Which nostr native apps are you guys most excited about?

my dream stack is GitHubstr, KickStartstr, and StackOverflowstr.

nostr:npub1s3ht77dq4zqnya8vjun5jp3p44pr794ru36d0ltxu65chljw8xjqd975wz is working towards git, and so am I.

nostr:npub1kmwdmhuxvafg05dyap3qmy42jpwztrv9p0uvey3a8803ahlwtmnsnhxqk9 has the lead in making that a reality with crowdfunding.

are there any contenders for StackOverflowstr?

#asknostr #grownostr #buildnostr

Replying to Avatar Melvin Carvalho

A few people are but there is a better way:

Use gitea which almost has feature parity : https://about.gitea.com/

Or gogs if you want something more lightweight.

Then use nostr for updates.

You can host it at git.blowater.app its quite easy.

A good thing to work on is login to gitea with nostr, a couple of people are working on this too, single sign on

An alternative is radicle, but many are put off by their token sale, from the past

Git over nostr is neat, and there are some heroic efforts, but it'll never be feature parity, and also relays are not guaranteed to store data, only to relay notes, and other stuff.

I'm of the mind that nostr and git can complement each other. GitHub is not git. we can build multiple git host services that have a variety of functionalities and focused on different use cases and user profiles.

that way, parity is not even a desirable outcome. I'd argue for superiority.

So sorry for your country.. I'm hoping Denmark take them out

🇩🇪7x1🇧🇷 never forget

Replying to Avatar Laeserin

It's been so weird working on nostr:npub1s3ht77dq4zqnya8vjun5jp3p44pr794ru36d0ltxu65chljw8xjqd975wz because we're now 10 people and it took forever to collect the group and get the infrastructure setup and write the scripts and figure out where to put the docs, and figure out naming schemes, and decide which products to build, and draw icons, and rent relays, and learn how to make repo events, and select frameworks and tools, decide on languages and network with people making similar products, and and...

But, now that's all there and we can just... work.

It's getting interesting.

Feels like we've hiked to the top of some sort of mountain and we can just glide down from here.

Git oriented people on Nostr!!!! We need to talk!! I did a thing: https://github.com/gugabfigueiredo/git-remote-nostr