Man I love this idea - signed up. But I've been getting 502s consistently, HN "Hug of Death"?
Sr.ht, the hacker's forge, now open for public alpha
91–100 of 221 posts
Re: Sr.ht, the hacker's forge, now open for public alpha
#92Earlier 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)!
That must explain the new GMail design.
Re: Sr.ht, the hacker's forge, now open for public alpha
#93Earlier quoted context omitted.
>* 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…
Nonetheless, it'd be nice to have some way of plugging in more of this kind of functionality at the instance, user, and possibly repo levels. Obviously syntax highlighting is one use case, but some others: - 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…
I think a lot of what you're looking for is going to be possible through generic interfaces I plan on writing. It's not going to take the shape of "you can write code which executes on sr.ht's servers just for your repo in particular", but rather things like "you can POST to an API endpoint on git.sr.ht to annotate the sources in your tree for a specific commit sha with links to pydoc et al". builds.sr.ht would then be the place where you could run arbitrary code to automate this.
Re: Sr.ht, the hacker's forge, now open for public alpha
#94Man I love this idea - signed up. But I've been getting 502s consistently, HN "Hug of Death"?
It's a memory leak in git.sr.ht, rather than an issue of scale, thankfully. I'm working on it. After a few refreshes you should get through, and the problem is isolated to git.sr.ht in particular.
Re: Sr.ht, the hacker's forge, now open for public alpha
#95Earlier quoted context omitted.
Nonetheless, it'd be nice to have some way of plugging in more of this kind of functionality at the instance, user, and possibly repo levels. Obviously syntax highlighting is one use case, but some others: - 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…
I think a lot of what you're looking for is going to be possible through generic interfaces I plan on writing. It's not going to take the shape of "you can write code which executes on sr.ht's servers just for your repo in particular", but rather things like "you can POST to an API endpoint on git.sr.ht to annotate the sources in your tree for a specific commit sha with links to pydoc et al". builds.sr.ht would then…
Sourcegraph CEO here. We would love to help integrate Sourcegraph into sr.ht for code intelligence (hovers, go-to-definition, etc.). We’re kicking this off with GitLab next month.
Re: Sr.ht, the hacker's forge, now open for public alpha
#96Earlier quoted context omitted.
I think a lot of what you're looking for is going to be possible through generic interfaces I plan on writing. It's not going to take the shape of "you can write code which executes on sr.ht's servers just for your repo in particular", but rather things like "you can POST to an API endpoint on git.sr.ht to annotate the sources in your tree for a specific commit sha with links to pydoc et al". builds.sr.ht would then…
Sourcegraph CEO here. We would love to help integrate Sourcegraph into sr.ht for code intelligence (hovers, go-to-definition, etc.). We’re kicking this off with GitLab next month.
Great! My email is sir@cmpwn.com. I can't guarantee a lot of cycles right now, but get in touch and I'll keep it on my radar.
Re: Sr.ht, the hacker's forge, now open for public alpha
#97>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!
Server side html rendering will always be less efficient, but I can see the application of using curl to request and parse pages.
You mean more efficient, right? Because the single page "applications" that download UI and data with javascript take a three-digit number of requests and multiple seconds to render everything and be "done".
Re: Sr.ht, the hacker's forge, now open for public alpha
#98Forgive me if this is covered elsewhere, but I haven't found it yet. One 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 vi…
Thanks for your feedback and questions!
>One 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.
For the moment I've explicitly decided against this. I want sr.ht to be a professional tool more so than a social network. This may change to varying degrees in the future.
>will there also be anything like GitHub's "Notifications" page?
There will be a feed of events, which you can use for a similar reason. At the moment, there are feeds like this, but they aren't global - they're scoped to each sub-site, like lists.sr.ht. Here's what my lists.sr.ht page looks like:
>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?
Maybe!
Re: Sr.ht, the hacker's forge, now open for public alpha
#99This 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…
>I can then add myself as "ro", and still push. I know this is an edge case but wanted to raise it 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 log…
> Are you logged out as you browse between different subdomains?
This is probably it. Clicking "login" logs me right back in. The move between the subdomains is very smooth, so I did not even notice. Thanks!
Re: Sr.ht, the hacker's forge, now open for public alpha
#100Browsing from mobile so not easily able to poke around, hence pardon my ignorance, but what is meant by “software forge”? Is this common terminology? I haven’t heard it before. Initially I assumed this was some sort of web-based IDE, but I guess it’s more of a source control, continuous integration, devops, and deployment system? Is it like Github meets Jenkins meets Jira? It might be valuable to have a more clear overview message on the site.
Edit: The actual project homepage has a much better overview of what this is, sorry for my initial cluelessness. The more I look into it, the more impressive it looks, thanks for the great open source contribution!