[–] [S] 2 points 2 weeks ago (1 child)

Every time I use github or gitlab it's broken in a brand new way. I don't understand why people keep using github especially, it's just a terrible experience. The downtime alone, but now the bugs are just out of control. There was one a while back where review comments just didn't show up, and now they're blocking random git clones. That's the whole thing github is for! Code hosting and reviews!

  • source
  • parent
  • context
  • [–] [S] 1 point 1 month ago

    That's really cool! Unfortunately I have ethical issues with systemd, so I'd rather not support it as a first-class option in documentation or out of the box configs. Thankfully something taking over port 79 isn't a concern on any of my threat models for the software. I still require root for low ports on all my systems (to stop takeovers of 80, 443, 22, etc) but something listening on the finger port is going to be pretty harmless. Just don't try to finger hunter2@example.com :p

  • source
  • parent
  • context
  • [–] [S] 1 point 1 month ago (3 children)

    sourcehut is almost everything I want from a git forge! the ability for people to contribute or file bug reports without an account is great, and it's not tied to a horrible corporation. it's right up my alley, when I'm not making silly things like fingies, I'm working on stuff like doink and gah to make it easier for people to leave corporate git forges :)

  • source
  • parent
  • context
  • [–] [S] 4 points 1 month ago

    I mean, you can if you want. But the finger spec doesn’t actually specify a format for the returned data, so anything can be in there. Fingies just reads data from a text file and returns that. So finger foo@server would just have fingies read the file named <data_dir>/foo and respond with whatever is in that file. It could be a real name, address, and phone number, or just a silly greeting.

  • source
  • parent
  • context
  •  

    cross-posted from: https://programming.dev/post/55600767

    Partying like it's 1977!

    I recently stumbled on the finger protocol through happynetbox and thought it was pretty cool, so I wrote a finger server that reads user data from text files. It's a pretty simple protocol, but I think it's a fun way to enable a simple smolnet-style status page :)

     

    cross-posted from: https://programming.dev/post/55600767

    Partying like it's 1977!

    I recently stumbled on the finger protocol through happynetbox and thought it was pretty cool, so I wrote a finger server that reads user data from text files. It's a pretty simple protocol, but I think it's a fun way to enable a simple smolnet-style status page :)

    [–] [S] 3 points 5 months ago

    Great question! I considered that, it's what lead me to the idea to use DNS in the first place. The problem I had with that is that the ultimate URL path might change, not just the hostname. What happens if a repo has to move from github.com/org/repo to mycoolforge.net/repo?

    But there's also another reason that I realized as I was working out the details of git-remote-helpers: What happens if your remote needs to change protocols? With doink you can swap from http(s) to ftp with an ip address instead of a hostname, or perhaps even some (future) git-over-whatever-p2p-network.

    So yeah if you're swapping from a github-style forge to another github-style forge and you don't need the flexibility, you definitely could just CNAME it! And that would probably be more robust, but it would also give you less future flexibility :P

  • source
  • parent
  • context
  •  

    cross-posted from: https://programming.dev/post/49019468

    Hey, I made a thing! It's called doink. Doink gives you dynamic git remotes by using DNS TXT records as pointers.

    I wrote a bit about how it works and what it's useful for.

    Anyway, do you ever thing about how DNS is a basically a decentralized key-value database? I think about it a lot :)

    [–] [S] 5 points 9 months ago

    Yeah, microsoft has owned github since 2018. I made this to help people and organizations move off of github, onto something like forgejo or sourcehut. But even after moving, all of those old issues, pull requests, comments, those need to live somewhere. A lot of people seem to use a script to recreate all their issues on their new code host, but that loses a lot of metadata and can only work if there's a script for your new chosen host. Everyone else just archives the repo and leaves all that info there, which is great until people forget its there, or microsoft decides to start charging for issue hosting.

    So now, with GAH!, people can more easily move away from github, they don't need to worry about what happens to their issues and PRs. It's one less barrier to leaving github :)

  • source
  • parent
  • context
  •  

    cross-posted from: https://programming.dev/post/42508495

    Issue and PR threads are invaluable documentation for a project, it's difficult to migrate to another code host when years of knowledge are locked into your old hosting service. So I built a couple of scripts to archive issues, pull requests, comments, and source code from github repositories, and to turn them into static sites! With the accelerating exodus away from github, I've heard from a lot of people that there aren't any good tools for archiving that knowledge in a human-readable format, so I thought this would be a useful tool to make. The initial release is ready, and just in time for github to start charging for self-hosted runners!

    If you try it out, let me know what you think. There's definitely areas that can be improved on :)

     

    cross-posted from: https://programming.dev/post/42508495

    Issue and PR threads are invaluable documentation for a project, it's difficult to migrate to another code host when years of knowledge are locked into your old hosting service. So I built a couple of scripts to archive issues, pull requests, comments, and source code from github repositories, and to turn them into static sites! With the accelerating exodus away from github, I've heard from a lot of people that there aren't any good tools for archiving that knowledge in a human-readable format, so I thought this would be a useful tool to make. The initial release is ready, and just in time for github to start charging for self-hosted runners!

    If you try it out, let me know what you think. There's definitely areas that can be improved on :)

     

    Issue and PR threads are invaluable documentation for a project, it's difficult to migrate to another code host when years of knowledge are locked into your old hosting service. So I built a couple of scripts to archive issues, pull requests, comments, and source code from github repositories, and to turn them into static sites! With the accelerating exodus away from github, I've heard from a lot of people that there aren't any good tools for archiving that knowledge in a human-readable format, so I thought this would be a useful tool to make. The initial release is ready, and just in time for github to start charging for self-hosted runners!

    If you try it out, let me know what you think. There's definitely areas that can be improved on :)