Live data from Hacker News

Sr.ht, the hacker's forge, now open for public alpha

drewdevault.com

181–190 of 221 posts

Re: Sr.ht, the hacker's forge, now open for public alpha

#181

Forgive 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…

You can have email notifications without filling up your inbox. Just set up a filter rule to move all emails from an address to a folder. I do that for all spammy things like mailing lists or issue tracker comments.

Re: Sr.ht, the hacker's forge, now open for public alpha

#182

Earlier quoted context omitted.

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".

No, because once you download the js you don't redownload it on every page request. When you want to update contents you get the new data to be displayed. This is how any other gui application does server communication. The traditional page based responses re-send all the html content over again. If the client can cache it then it doesn't have to be, but caching something like a git frontend does not work with page b…

When most of the web looks like this: https://news.ycombinator.com/item?id=17655316

I'm happy about Drew's decision to not include JS.

Re: Sr.ht, the hacker's forge, now open for public alpha

#184
post #95

Earlier quoted context omitted.

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.

Awesome. Just filed https://github.com/sourcegraph/sourcegraph/issues/1027 on our end to track it.

Re: Sr.ht, the hacker's forge, now open for public alpha

#188
This looks really nice and it's working incredibly quick for me.

I have a couple of maybe stupid question.. I'm having trouble understanding the workflow. When I open something like https://todo.sr.ht/~sircmpwn/

This is the issue page for a user, right?

And then when I go to

https://todo.sr.ht/%7Esircmpwn/sr.ht

(oh, the tilde copy-and-pastes weird into the comment window.. not sure what that's about)

This is the "issue page" (in Github speak) for one of a user's repositories. But how do I navigate from there to the actual repository? The 'git' button at the top takes me to generic landing page? I found this link through the announcement page : https://git.sr.ht/~sircmpwn but I dont get how to navigate to there naturally.

Or how to go from the git back to the todo. I get they're decoupled features, but surely there must be a way to go back and forth.

Also when I open up the 'tree' section, each line starts with file permissions in the style of 'ls -la'. Is this b/c the system is fundamentally tied to POSIX? (I've used git with no problem on Windows before - so I don't see why it would be)

Re: Sr.ht, the hacker's forge, now open for public alpha

#189
post #188

This looks really nice and it's working incredibly quick for me. I have a couple of maybe stupid question.. I'm having trouble understanding the workflow. When I open something like https://todo.sr.ht/~sircmpwn/ This is the issue page for a user, right? And then when I go to https://todo.sr.ht/%7Esircmpwn/sr.ht (oh, the tilde copy-and-pastes weird into the comment window.. not sure what that's about) This is the "iss…

Navigating between different pages for the same project is an upcoming feature

Re: Sr.ht, the hacker's forge, now open for public alpha

#190
post #158

All features work without JavaScript I'm not sure why this is a selling point. Yes, there are many upsides to this, particularly from the maintainer's standpoint, but I think it might just be a side-benefit that only certain users really care about. Eventually, there might be advantages to removing that "feature", and you might turn off users who joined largely because of it.

I see it as a reflection of the website's overall design stance: no frills, no stupid material design, no js junk scripts. Just a fast-loading website that loads what it needs to. This kind of website is quite refreshing in 2018. Maybe one day it will have a tiny amount of JS, but let's cross that bridge when it comes. That's still better than the vast majority of modern websites built today.

It does already have some JS. On the builds page, when it is running a build, it refreshes every second to show new output.
Post reply on HN