Avatar
average_bitcoiner
d3d74124ddfb5bdc61b8f18d17c3335bbb4f8c71182a35ee27314a49a4eb7b1d
sum divided by count sp1qqvj5uth3ruspj8marnkr2eyvufsfu2ssggwyl4ma3ad3cxta86y6wqje6h6astqvrx5m9qpc34hahfavq90hwcdl3umnls9e9mef6nyaj5dcz0ev

https://alblue.bandlem.com/2011/12/git-tip-of-week-patches-by-email.html

How git patches are sent over email in the era before GitHub etc.

"""

Once the bundle file has been generated, it can be sent over any transport to the remote host for reconstitution. This might involve burning to a CD, via a USB stick or some other network protocol.

"""

Unsure what your definition of cheap was.

https://www.3riversarchery.com/

I use these guys.

Narrowly scoped feature with lots of self-custody reactive security possibilities.

Bitcoin currently lacks any reactive security models for self-custody. Because users cannot be vigilant 24/7, security will trend toward offloading to counterparties that can remain 24/7 vigilant. OP_VAULT enabled the sovereign individual to have reactivity for their most secure stacks.

How did Hal install the original

Bitcoin core on his computer?

How did you install it on your computer?

Writing complex software and then creating a seamless install method are both laborious. I think there’s over-trivialization of creating an installer/bundle/whatever in this thread.

No offense taken🫂, I appreciate the perspectives and understand your points. I just think we’re talking about two separate tools. Hammer vs screwdriver type of thing.

I don’t install many things from source due to the friction you describe. I use package managers or app stores because those are purposely designed with that flow in mind.

Got itself is a nightmare to understand. Just go search “git porcelain vs plumbing”. It’s a complex system in its own right. Any time you add layers of abstraction, it gets a little less clunky.

When you’re frustrated with the process of using GitHub for a task (install or otherwise), ask yourself “how would I do this using CLI/non-GUI?” I guarantee whatever your doing requires much more wizardry and knowledge on the CLI than in the GUI.

That being said, UI/UX abstractions on top of git should improve over time as most abstractions do. (Compare computer management/use from the 90s/00s to now)

Love you’re content 🧡🧡and perspectives and if you ever have concrete ideas for an improved flow related to git, please share!

Until then, I’m going to just copy the GitHub design because my brain isn’t creative enough to think of new ways. 🫠

This seems to want to replace git by managing the actual source code. While it may work, I would think that problem is already solved by git very very well.

Followed for ideas though.

That’s what the mentioned NIP proposal is trying to do. Define the contract/protocol for sharing git context.

It’s the seamless experience that is capturing. Why do so many people use GitHub? I would argue it’s because of the friction it removes from the many git related tasks. Emailing patches is fine but not something everyone is comfortable with due to the “extra” steps needed to compare/diff, and discuss the patch. There’s user friction involved. GitHub and other git context providers have greatly reduced the friction for these processes as well as consolidated them into one place with other tooling. This value add cannot be understated. I can email you a patch, but that does not provide visibility into any CI/CD I’m running. Nor does it connect the patch to an outstanding issue.

Yup yup. Pretty cool. Just want to rally the devs around the NIP discussion. For acceptance we’ll need a few implementations.

Was just looking at the source code. It’s in an unfamiliar language. 😞

But still going to check it out!