Earlier quoted context omitted.
Agree. Simple and not over-engineered.
>not over-engineered Always keep in mind that many people have an interest in ensuring their own job remains relevant and necessary. How else can you explain e.g. google's constant UI changes? Designer's keeping themselves busy (even though there are no real reasons for the changes)!
Sr.ht, the hacker's forge, now open for public alpha
81–90 of 221 posts
Re: Sr.ht, the hacker's forge, now open for public alpha
#82Re: Sr.ht, the hacker's forge, now open for public alpha
#83Looks like the CI builds are tied to a user/group account rather than being tied to a particular repo or branch. Bravo on that— it works much better for projects whose build is composed of assets from many small repos than the approach of Travis (and GitLab, who cloned it) of tightly coupling those things.
Re: Sr.ht, the hacker's forge, now open for public alpha
#84You are my hero Sir! I've recently switched from i3 to sway beta, and now this, do you ever sleep?
Re: Sr.ht, the hacker's forge, now open for public alpha
#85Some thoughts:
* Thanks for adding support for 2FA via OTPs, this is a requirement for me
* Access control is a little weird. I start without any users having access, but I can push to the repository. I can then add myself as "ro", and still push. I know this is an edge case but wanted to raise it
* I keep getting logged out while navigating through pages, though I'm guessing this is related to the 502's I'm getting occasionally (HN Effect)
Re: Sr.ht, the hacker's forge, now open for public alpha
#86Looks fantastic, I just signed up to try it out. Small ux thing; the nav bar on top are different for every subdomain. Probably easier to navigate if the elements are in fixed positions.
Thanks for signing up! They're ordered by the time you accessed each last. I agree that this is, in retrospect, unintuitive and poorly designed. Will be reverting it soon enough.
Was very confused by the changing order.
Re: Sr.ht, the hacker's forge, now open for public alpha
#87>On top of that, sr.ht is one of the most lightweight websites on the internet, with the average page weighing less than 10 KiB, with no tracking and no JavaScript. You have my attention!
Re: Sr.ht, the hacker's forge, now open for public alpha
#88Congrats on the milestone. This is a huge boon to the open source community. I love the pricing model. Are there any plans or ideas for a migration path from GitHub to sir.ht? I would imagine that if there was a way to transfer issues and discussions it would encourage more users to make the switch. Here's one data point for you: zig programming language. Influencing factors: * If we had syntax highlighting in the fi…
>* If we had syntax highlighting in the file browser, that would be a win over GitHub, which insists that there be "hundreds of GitHub repositories" before accepting a syntax highlighting pull request for a new language. I could imagine it would be reasonable to support "repository-local" highlighting configuration. We use pygments, so patches to pygments would make it to sr.ht's syntax highlighting. >* Transferring…
- Sophisticated cross-referencing tools like Kythe and SourceGraph
- Linking stdlib functions and imports to public documentation, like cppreference.com, python.org, etc.
- Linking ticket/user names to my non-srht bug tracking tool (especially JIRA, but there are lots of possibilities).
- Linking to public or self-hosted generated API docs (doxygen, swagger, sphinx, etc).
- Linking to info pages generated from metadata-type files such a PKG-INFO (for example containing dependency tree information).
- Propagating back information gathered from build or test runs, for example highlighting areas missing test coverage, or which are "hot" from a perf point of view.
Only some of these would be appropriate to go into the mainline version of the tool, which is why it's important to support plugging in these capabilities for the users which need/want them.
Re: Sr.ht, the hacker's forge, now open for public alpha
#89This is a very cool project, and I'm interested in using it for some of my private repos. Some thoughts: * Thanks for adding support for 2FA via OTPs, this is a requirement for me * Access control is a little weird. I start without any users having access, but I can push to the repository. I can then add myself as "ro", and still push. I know this is an edge case but wanted to raise it * I keep getting logged out whi…
Thanks: https://todo.sr.ht/~sircmpwn/git.sr.ht/128
>I keep getting logged out while navigating through pages, though I'm guessing this is related to the 502's I'm getting occasionally (HN Effect)
The 502's are a bug, rather than a scaling issue. git.sr.ht seems to have a memory leak, which I'm investigating. Are you logged out as you browse between different subdomains? There's a ticket for logging you into everything at once, but for now you have to click "login" on every sub-site.
Re: Sr.ht, the hacker's forge, now open for public alpha
#90One of the things that I do like about GitHub is actually the community/social aspect. For example, I follow projects I am interested in, and I can see notifications from all of them on one page--without filling up my email inbox. I also follow users who have similar interests, and I often discover new projects when I see in my feed (which I read via RSS) that they've starred a project that sounds interesting.
I think it's great that you're supporting email as a first-class way to interact with the services, but will there also be anything like GitHub's "Notifications" page?
Another feature I enjoy on GitHub is the ability to view issues and PRs across all of my repos from a single search page (e.g. search for "user:repo-owner-username is:issue"). Will sr.ht have anything like this?
Thanks for your work and for sharing it freely.