Im intrigued by the choice to enforce all lowercase usernames, why is it like this?
Usernames must be valid Unix usernames. This is a forward-looking design decision for some interesting features down the road...
Thanks for sr.ht!
141–150 of 221 posts
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.
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.
I'm glad that you like everything else :)
Just signed up. I like the old fashioned user URL, reminds me the age of public_html https://lists.sr.ht/~ontouchstart BTW, please add a nice 404 so people won't see that you're running nginx/1.14.0 :-) https://sr.ht/~ontouchstart
You mention: > lists.sr.ht finally modernizes mailing lists What's new that lists.sr.ht brings to the table? I only had a quick browse of https://lists.sr.ht/~sircmpwn/sr.ht-dev , but as far as I could tell it looked like a pretty normal list of topic lines (like a typical web forum), and the e-mail conversations themselves are just the messages concatenated into one long page (e.g. https://lists.sr.ht/~emersion/mrsh…
"Looking like a typical web forum" is a huge improvement compared to what e.g. GNU Mailman offers.
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.
One of the coolest projects I've seen in a while! Really excited to see where this goes. Some quick feedback: viewing messages on lists.sr.ht on mobile gives the " block experience" of moving a horizontal a scroller for every line. This might be intentional (wrapping can wreck formatting/alignment) but it might be worth wrapping for it to be less painful to read from a mobile browser.
Yeah, this is deliberate. I don't want to wreck the formatting of anyone's emails. That being said, there are solutions to this... but they're a bit obscure and will require some effort.
Just signed up. I like the old fashioned user URL, reminds me the age of public_html https://lists.sr.ht/~ontouchstart BTW, please add a nice 404 so people won't see that you're running nginx/1.14.0 :-) https://sr.ht/~ontouchstart
Hmm i made a golang project to test https://git.sr.ht/~ata/demo/tree/master/main.go and first thing I noticed was that ~ in my package name. I wonder if that’s valid golang?
Earlier quoted context omitted.
Hmm i made a golang project to test https://git.sr.ht/~ata/demo/tree/master/main.go and first thing I noticed was that ~ in my package name. I wonder if that’s valid golang?
Golang doesn’t have a problem with it, but I would have to rename src/git.sr.ht/ata src/git.sr.ht/~ata a ~ in the filename which linux doesn’t like
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.
> 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.