Live data from Hacker News

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

drewdevault.com

151–160 of 221 posts

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

#151

Earlier quoted context omitted.

Can you elaborate on your reasoning for that?

not speaking for OP, but the significant changes between GPL v2 and GPL v3 would make me absolutely paranoid, and represent a good example. A "v2-and-later" would have subjected people to licensing changes they absolutely don't want.

And that is why GrafX2 devs switched[0] to GPLv2 only

> GPL v2, without the "any later version" clause (sorry FSF, I don't want to accept licences you didn't even write yet).

[0] https://gitlab.com/GrafX2/grafX2/commit/26c6d12d0987f4467036...

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

#152
post #77

> builds.sr.ht, which is easily the most capable continuous integration system available today Azure DevOps pipelines are really capable, with a great UI - I'd love to see a side-by-side comparison?

That is a bold claim. More capable than Team City?

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

#153
This looks fantastic! One feature I would like to see in a service like this would be support for custom domains. Personally, I would be willing to pay extra for such a feature. It’s nice to have control of the domain for personal work, but self hosting for a handful of personal projects is a big ask - I would rather pay for someone to do it the right way.

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

#154

This looks fantastic! One feature I would like to see in a service like this would be support for custom domains. Personally, I would be willing to pay extra for such a feature. It’s nice to have control of the domain for personal work, but self hosting for a handful of personal projects is a big ask - I would rather pay for someone to do it the right way.

Thanks for your feedback! This is definitely something I'm interested in adding in the future. I don't think I can prioritize it right now, because I have limited time to spend on sr.ht (I still have a day job), but I want to tackle it post-alpha.

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

#155

I noticed that there's no link from, for example, https://todo.sr.ht/~sircmpwn/man.sr.ht to https://git.sr.ht/~sircmpwn/man.sr.ht - is there any way to link a project's pages together across multiple sr.ht services? Otherwise the navigation isn't so friendly for someone just discovering a project.

Yeah, improving this is a pre-alpha todo item.

It would be nice to be able to add custom links to whatever form this navigation takes, also (for example, if a project uses a different solution for code review/patch submission).

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

#156

Earlier quoted context omitted.

Yeah, improving this is a pre-alpha todo item.

It would be nice to be able to add custom links to whatever form this navigation takes, also (for example, if a project uses a different solution for code review/patch submission).

Aye, this is planned. Thanks for the feedback!

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

#157

I like everything. Well, almost everything: The "View raw message" feature exposes way too much information about your contributors - including their email, smtp client, ip, and a bunch of other things. I understand and appreciate the usefulness, but as a contributor I don't usually expect my details to become that public.

The IP is the IP of your mail server, which is a lot less private (you can derive that just by doing a DNS lookup on your hostname). The email address is explicitly exposed, your email is not private in git repos either, and it's important that people are able to get in touch with you. It's a mailing list! I'm glad that you like everything else :)

Many email servers report the IP of the incoming SMTP connection when you use a client (e.g. mutt, Thunderbird, Apple Mail, or Outlook) as an "X-Client-IP" or similar raw header; often also the envelope "from", which may be different than the message "from" which is the only one usually shown.

It's not that IPs are very private - sending an email to someone often tells a lot about you. But having all that info publicly scrapable seems unexpected to me.

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

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

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

#159

Earlier quoted context omitted.

not speaking for OP, but the significant changes between GPL v2 and GPL v3 would make me absolutely paranoid, and represent a good example. A "v2-and-later" would have subjected people to licensing changes they absolutely don't want.

From GPL 2: > either version 2 of the License, or (at your option) any later version. "At your option" means that no one is 'subjected' to changes they don't want. They just have the option to upgrade.

Sure, but this thread is about licensing the software as "version $x or later", which pushes the choice to the user of the license.

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

#160

Earlier quoted context omitted.

The IP is the IP of your mail server, which is a lot less private (you can derive that just by doing a DNS lookup on your hostname). The email address is explicitly exposed, your email is not private in git repos either, and it's important that people are able to get in touch with you. It's a mailing list! I'm glad that you like everything else :)

Many email servers report the IP of the incoming SMTP connection when you use a client (e.g. mutt, Thunderbird, Apple Mail, or Outlook) as an "X-Client-IP" or similar raw header; often also the envelope "from", which may be different than the message "from" which is the only one usually shown. It's not that IPs are very private - sending an email to someone often tells a lot about you. But having all that info public…

That seems fair. I can probably strip unnecessary headers from incoming emails.

https://todo.sr.ht/~sircmpwn/lists.sr.ht/60

Post reply on HN