I can empathize with that. here’s my opinionated guide to git. this pattern is common in large OSS projects as well as big tech:

- read up on and practice using “conventional commits”. this will help focus commits into isolated units of work

- read up on and practice using “feature branches”. this will allow you to group your tidy commits into an isolated branch. feature branches should introduce one feature/change/fix. eg “add login support” or “fix bug x”.

- submit a pull request for the feature branch

- after review is complete and changes are ready to merge, squash all the commits into a single commit, then merge. this keeps the main branch’s commit log clean and readable

this is the basic workflow I’ve followed and introduced to teams I work on. there are lots of variations at each of these steps, but it’s a good place to start.

Confirmed nostr:note12set2ez0wwh647zxk4fjnscswhgwtd9wu6sxy84z0ptfn6v9r3nqrpfku7

I contribute to this. Unfortunately, there is not an easy way to know that what you are reading or learning is any good, short of having a mentor.

Once I have people I can trust to collect patches into trees I can just merge large subtrees of changes like linus does it. Its very scalable. People just need to learn how to do proper git commits that are logically distinct and can be cherry picked incrementally and independently. Developers don’t have this skill anymore because github doesn’t force you to think about it.

Once people learn how to do this I would feel more comfortable letting maintainers collect many changes into their own forks that I merge all at once. I kind of do this already with #[2]​‘s translation PR but I still find myself formatting the branch and removing duplicate commits, etc.

It would save me a lot of time if contributors learned git and used it effectively so I don’t have to spend all day formatting patches, rebasing, squash merging, and fixing conflicts.

There’s kind of an inherent flaw in the idea of vanity npubs, which is, in a naming system, shorter names are worth more than longer names, but with vanity npubs, its exponentially easier to mine a short one than a long one.

Who’s got the next round?

I’ll pay it forward.

pv

Only rejected the camera permission on the first build, that’s it. I can try deleting the app data and reinstalling in case something corrupted somehow.

Yes, it still crashes, and I submitted the crash report.

Let me know if it works now. This is happening to a handful of people.

Wow this is the first time I’ve seen thread spam. Someone is triggered

I had been running consistently since 2003, but lately I’ve fallen out of my habit. I need to get back into it and want to use nostr to keep me accountable. My plan is to do this half marathon program. Anyone is welcome to join me in this adventure. Should I call this #nostrrunningclub, or should I call it #runstr ???

good morning, mempools may never clear again

ya'll went from making fun of me for my mempools prediction to calling a fee market an attack in less than three months lmfao

Natural wood colors; not stained, not finished, just sanded.

Someone just need to write a markdown doc with some POST/GET endpoints that defines some basic things like auth

Then you would need people to start running storage nodes. This would work fine with nip94 and would be the proper way to do it.

Anything pre-existing that comes to mind? Im interested in spinning something up to play with.