Most developers on here don't seem to like simple things. Anytime you come up with something that is extremely elegant, reliable, and easy to implement and use, they come right back at you with something convoluted, messy, and garish, for no good reason. Oh, that sounds great, girly, but those are rooky codes. We need to pump that code up. Let's add some doo-dads, transpose it to the third dimension, add a landing port for Superman, rewrite it in Rust... They just get off on everything being complicated because that is more impressive to other developers. Why write 5 lines of code when you could write 104710 lines, KWIM? Besides, if they just wrote the same 5 lines you did, then they would be _reusing your idea_ which is apparently the absolute horror. I mean, *Obvious girl code cooties are obvious.*

I'll publish the new #gitstuff specs, but I need to get it all running smoothly in the container, first, so that there's a nice web app where people can try them out.

I hate when I bug-fix an algorithm to death and completely befuddle the AI and it just turns into 🍝.

Example of a Nostr-signed commit. 🕹 Instead of verifying only the repo (we also have that), you can verify all of the commits, individually. You can see that in the commit history, including the userbadge of the signer. ✍🏻 View quoted note →

GN. 🌝 GitRepublic Web has already come a long way. 1. Spent two whole days, refactoring, but I still haven't managed to stop it from spawning zombie processes during polling. I'll look at it, again, next time and rehost the repo when I get it fixed. 2. Implemented release events for the tags, that include the zip-download URL. 3. Local cloning to localhost/dev and online editing/adding/saving of all files works. 4. You can add a Markdown or Asciidoc documentation event (30818 default), or just stick to the ReadMe. 5. Branch management for empty repos was very hard and I am now git-traumatized, but it works. I suffer, so that you don't have to. 6. Issues, PRs and patches implemented, including code highlights and comments. 7. Changed access management to be more granular. Now have public, unlisted, restricted, private. (Private saves all events to the repo, rather than publishing them to relays. Share the events with other git repos and stay off the Nostrnet.) 8. Kind 11 discussion thread under very repo. Lots more bug-fixing and testing to go, but all MVP features are implemented and proven. Project management and Kanbanstr not until v.0.2.0 I need to work on other stuff, like the data imports and aitherboard #spells and the mysterious something something from our mysterious boss @MichaelJ, so I will get back to this repo next week.

Gitea: Git with a cup of tea

gitrepublic-web

gitrepublic-web

#GitRepublic #gnostr

I need to stop responding to people who ignore me. Feels like talking to a wall. They all have me muted. 🙄 View quoted note →