latest 20 messages by nate

+ [2020-10-26T15:57:55Z] nate Someone really needs to do something about stenographer lol
+ [2020-10-25T23:49:26Z] nate I thought the github channel on here actually had the backing of official members? Or was that pre-microsoft?
+ [2020-05-25T07:49:55Z] nate If it does still work it's most likely a -very- limited time token
+ [2020-05-25T07:49:37Z] nate try it in a "new private window", it shouldn't inherit your session cookies then I believe
+ [2020-05-25T07:47:04Z] nate Did that open in a completely disconnected browser profile?
+ [2020-05-25T07:45:10Z] nate eggbean: What you view as the token is -probably- the above commit ID/hash I was talking about lol (which would make randomly guessing at URL's a lot harder)
+ [2020-05-25T07:40:30Z] nate simple solution would be try to view the latest/head raw file and then copy the URL to a browser session you're not logged ino n
+ [2020-05-25T07:40:13Z] nate If at all I'd imagine maybe only if you have a specific commit ID for the URL rather than 'latest'
+ [2020-05-25T07:39:42Z] nate I would highly doubt it, otherwise there would be risks probably for URL brute snooping which would be obviously bad
+ [2020-01-25T17:21:47Z] nate It's not, there's no real way for a git client to default sign like that, the author would need to provide their actual identifier key
+ [2020-01-25T17:12:42Z] nate It could be they're commiting from different systems and don't have a key configured on all of them
+ [2020-01-25T17:10:05Z] nate You mean the PGP verification thing for author commits? I would assume because the author didn't properly verify with their key
+ [2020-01-25T17:09:21Z] nate 'no verification'?
+ [2019-12-11T08:25:41Z] nate But again it might be mostly just an assumption of some technical knowledge. Can always post a request for adjustment on the community boards :P
+ [2019-12-11T08:25:05Z] nate But yeah they used a bad example in the screenshots, as they didn't include the www.*
+ [2019-12-11T08:24:43Z] nate Well it's a bit of sysadmin-ish general knowledge, it's possible they assume most users setting up github pages may have some technical knowledge. It looks mainly like that page you linked implies -only- the existence of a www.* record
+ [2019-12-11T08:16:19Z] nate https://github.community/t5/GitHub-Pages/Does-GitHub-Pages-Support-HTTPS-for-www-and-subdomains/td-p/7116
+ [2019-12-11T08:15:52Z] nate palasso: No, CNAME's are not redirects, they're aliases for a DNS lookup. The thing you need to understand is that a hostname only works on a server if it's configured for it, github pages are only recognizing domains defined in the settings, which is a single domain.
+ [2019-12-11T08:11:05Z] nate Unless the interface implies www.* should be working (which as far as I recall it does't, it's been a bit though), there's no reason to think www.* will work
+ [2019-12-11T08:10:40Z] nate palasso: I'm aware what a subdomain is, the point is if you configured example.com to be your github pages custom domain, that's what your github pages custom domain is, not www.example.com, only example.com.