4 ms·

Just signed up. I like the old fashioned user URL, reminds me the age of public_html https://lists.sr.ht/~ontouchstart https://lists.sr.ht/~ontouchstart BTW,

Just signed up. I like the old fashioned user URL, reminds me the age of public_html https://lists.sr.ht/~ontouchstart 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 https://sr.ht/~ontouchstart

Sir_Cmpwn 8y ago
Thanks for the feedback! https://todo.sr.ht/~sircmpwn/sr.ht/113 https://todo.sr.ht/~sircmpwn/sr.ht/113
- ontouchstart 8y ago
  Following link listed on the man page https://man.sr.ht https://man.sr.ht https://man.sr.ht/root https://man.sr.ht/root also gives a 404, but in a little better format. :)
  - Sir_Cmpwn 8y ago
    That's a git clone URL, not a web-facing URL :)
    - ontouchstart 8y ago
      I have not tried to clone it myself. But if it is not a web-facing URL, you should list it in clear CLI command and remove the <a> tag. People will click if you make it clickable.
andrewfromx 8y ago
Hmm i made a golang project to test https://git.sr.ht/~ata/demo/tree/master/main.go 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?
- andrewfromx 8y ago
  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
  - andrewfromx 8y ago
    I mean, you can do it, it’ll work but looks weird.
  - aaronmdjones 8y ago
    The only characters not allowed in a filename on Linux are 0x00 (the null byte) and '/'. It's perfectly valid to have '~' in it. You may be confused because your shell expands it to the value of $HOME -- which you can prevent by putting it inside single quotes. aaron@aspire5742:~$ echo hi > 'foo~bar.txt' aaron@aspire5742:~$ ls -l *.txt -rw-r--r-- 1 aaron aaron 3 Nov 16 03:20 foo~bar.txt aaron@aspire5742:~$ cat 'foo~bar.txt' hi aaron@aspire5742:~$
napsterbr 8y ago
> BTW, please add a nice 404 so people won't see that you're running nginx/1.14.0 :-) Actually simply adding a custom 404 page won't hide the webserver/version, as it is also sent along the HTTP response headers. For nginx specifically, one can use the `server_tokens off;` directive, which hides the version (but not the webserver). Brings back memories of when I used to recompile the webserver to remove this header :) Of course for UX a custom 404 page is great. Congratulations, Sir_Cmpwn, this is just awesome and I'll soon be subscribing.

Sir_Cmpwn 8y ago

Thanks for the feedback! https://todo.sr.ht/~sircmpwn/sr.ht/113 https://todo.sr.ht/~sircmpwn/sr.ht/113

ontouchstart 8y ago
Following link listed on the man page https://man.sr.ht https://man.sr.ht https://man.sr.ht/root https://man.sr.ht/root also gives a 404, but in a little better format. :)
- Sir_Cmpwn 8y ago
  That's a git clone URL, not a web-facing URL :)
  - ontouchstart 8y ago
    I have not tried to clone it myself. But if it is not a web-facing URL, you should list it in clear CLI command and remove the <a> tag. People will click if you make it clickable.

andrewfromx 8y ago

Hmm i made a golang project to test https://git.sr.ht/~ata/demo/tree/master/main.go 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?

andrewfromx 8y ago
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
- andrewfromx 8y ago
  I mean, you can do it, it’ll work but looks weird.
- aaronmdjones 8y ago
  The only characters not allowed in a filename on Linux are 0x00 (the null byte) and '/'. It's perfectly valid to have '~' in it. You may be confused because your shell expands it to the value of $HOME -- which you can prevent by putting it inside single quotes. aaron@aspire5742:~$ echo hi > 'foo~bar.txt' aaron@aspire5742:~$ ls -l *.txt -rw-r--r-- 1 aaron aaron 3 Nov 16 03:20 foo~bar.txt aaron@aspire5742:~$ cat 'foo~bar.txt' hi aaron@aspire5742:~$

napsterbr 8y ago

> BTW, please add a nice 404 so people won't see that you're running nginx/1.14.0 :-) Actually simply adding a custom 404 page won't hide the webserver/version, as it is also sent along the HTTP response headers. For nginx specifically, one can use the `server_tokens off;` directive, which hides the version (but not the webserver). Brings back memories of when I used to recompile the webserver to remove this header :) Of course for UX a custom 404 page is great. Congratulations, Sir_Cmpwn, this is just awesome and I'll soon be subscribing.