Anthony Accioly @Anthony Accioly - 6mo
Big rant against GitHub of the day. I finally managed to get "Accibot"'s account reinstated: https://github.com/accibot. It's now merrily updating my Golang repos. It was flagged about 3 hours after creation for, and I quote, "because you appear to have registered more than a single free user account. The GitHub Terms of Service Account Requirements state that an individual may not maintain more than one account." Meanwhile, here's what GitHub's ToS actually says: > - A machine account is an Account set up by an individual human who accepts the Terms on behalf of the Account, provides a valid email address, and is responsible for its actions. A machine account is used exclusively for performing automated tasks. Multiple users may direct the actions of a machine account, but the owner of the Account is ultimately responsible for the machine's actions. You may maintain no more than one free machine account in addition to your free Personal Account. > - One person or legal entity may maintain no more than one free Account (if you choose to control a machine account as well, that's fine, but it can only be used for running a machine). By the way, before anyone asks: Renovate can update Golang’s version (Dependabot can only update dependencies). You don’t need to use a bot to do this manually: https://github.com/renovatebot/renovate. This is all part of an experiment. I want a machine account to be able to generate and sign HAVEN releases, and handle all sorts of CI/CD shenanigans in a portable way, in case we ever decide to move off GitHub. At the moment, GitHub is a necessary pain in the neck for maintainers. For example, I’m happy to migrate to NIP-34, run my own instance of ngit-relay (can’t thank you enough nostr:nprofile1qyt8wumn8ghj7un9d3shjtnwdaehgu3wvfskueqpp4mhxue69uhkummn9ekx7mqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq32amnwvaz7tm9v3jkutnwdaehgu3wd3skueqpzpmhxue69uhkummnw3ezuamfdejszgnhwden5te0dpshvetw9ejxzmnrdah8wctev3jhvtnrdakj76twvfhhsqguwaehxw309a5xzan9dchxgctwvdhkuamp09jx2a3wvdhk6qpq5qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exskxljkd ), or use non-Nostr tech like Forgejo. Still, this basically means we'll get little to no contributions from the community, even from a tech-savvy crowd like we have here on Nostr. So yeahp, I keep having to jump through hoops to push my code to GitHub so that Microsoft and OpenAI can use it to train LLMs and build more vibe-based coding tools for you folks. Suggested Hashtags: #devstr #GitHub #Rant #MachineAccounts #FOSS #SelfHosting #NIP34
nostr:nprofile1qydhwumn8ghj7un9d3shjtnzd96xxmmfdecxzunt9e3k7mgpzfmhxue69uhhwmm59e6hg7r09ehkuegpz3mhxue69uhhyetvv9ujuat50phjummwv5q35amnwvaz7tmjv4kxz7fww468smewdahx2tmfde3x77qqyr3vea70ypqr70e2ff2mx28smca78p2c5l2lxd3jlk4wl3exc8ywk6y4j80, what do you think? Should we use NIP-34 for HAVEN? We can keep GitHub for issue tracking, CI/CD stuff, releases and eventual PRs. But I would love to have an alternative (even if it means extra work to keep everything in sync).
03653 - 6mo
This is the problem nostr:npub1s3ht77dq4zqnya8vjun5jp3p44pr794ru36d0ltxu65chljw8xjqd975wz is aiming for in our GitRepublic branded applications and services. We're not there yet so this is just noise, but git servers will be available eventually so teams don't have to rely on Github for their contributions.
Looking forward to it. Between your efforts, nostr:nprofile1qqs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7hycrvd’s work, Fiatjaf’s contributions, and others, the alternatives are starting to take shape. The hard part is getting users to report issues and send PRs via NIP-34, even with user-friendly clients like https://gitworkshop.dev/. Honestly, I’d even be happy to go back in time and use CircleCI and TravisCI if it means breaking free from Microsoft’s chains. Forgejo is also doing quite well in that regard for folks looking for something akin to GitHub Actions. So, self-hosting Forgejo as the "main repo" along with an Ngit relay for NIP-34 might already be enough for early adopters.
Myself and nostr:npub1s3ht77dq4zqnya8vjun5jp3p44pr794ru36d0ltxu65chljw8xjqd975wz have been enjoying OneDev for git and CI/CD running on our own servers which is fun. As you've heard me mention I use the heck of my hardware. Eventually we're planning CI but I personally want to push that down the roadmap for a bit, I don't want to just offer a hosted version of Jenkins, it's not that difficult for teams to deploy their own cloud jenkins or whatever CI and point it to their hosted repo.
