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 →

No, people will not run large, public relays for free, forever. These relay are already gigantic and they're quickly growing. They eat up serious resources, and they are only performant if they are tightly managed and cleverly architected. Much (most?) of the traffic they receive is bots, spam, scammers, attackers, and scrapers. Not to mention having to deal with the material people store on the relay and the possible personal or legal consequences of having that on your computer. People don't run Bitcoin nodes for free, either. They run them to manage _their own money_. The way Bitcoin is designed, you automatically help other people manage their money, when you manage your own, as it is all on the same chain. And storing something on Bitcoin costs you Bitcoin. It isn't free storage. Relays are not a chain. Almost everyone can and will only store and manage the notes they are personally interested in, and maybe those of their friends and contacts. That is enough, for basic communication (if your clients have AUTH and outboxes implemented), but larger relays facilitate wider reach. They aren't all going to go away... so long as they bring the person running it higher benefit and reward, than cost and bother.

Software engineering is now a performance art.

Highlights on git patches and PRs.

I've spent most of my "career" struggling to improve data quality, so I think I probably appreciate the simple standard of the event construct, more than most people. Nostr events are really useful for all sorts of data sets in all sorts of environments. They aren't just a relay-thing or a social-thing. They're great for signing documents, parsing data, structuring data archives, machine2machine coms, etc.