Forums Bug Reports - PLEASE PLEASE PLEASE INCLUDE DETAILS

[Mogri]

I just tried in incognito. You can't actually see anything more meaningful than post count aside from what's in the left pane of each post.

 

[Phantoon]

Ok, that's cool. Just thought I should ask

 

[lincolnic]

I'm not getting notified when I get mentioned in posts - Violentvixen @'d me in this post, but I didn't get a separate notification for the mention. I did get the usual "[Person] replied to [thread]. There may be more posts after this." notification. I do have alerts turned on to be notified when I'm mentioned, is there any other info I can provide that's helpful?

 

[Kirin]

I wonder if it fails to notify you about the tag if you were already notified about the same post for a different reason...

 

[Bongo]

I think that's what it is; it won't notify you twice about the same post.

 

[lincolnic]

I'd swear that I've gotten notified twice if someone quoted one of my posts in a thread other people had responded to, but maybe not. Either way, I'd expect a separate notification if you were specifically mentioned by name, though I can see how others might not prefer it.

 

[Kirin]

Huh, so for some reason *one* of my computers is saying it can't connect to Talking Time right now, although two other computers in the same room are having no problem. On the problem one, a rather old version of Safari just says it can't open the page because it can't establish a secure connection. On the same machine, a theoretically up-to-date version of Chrome (which may still be kinda old because it's "up to date" for MacOS 10.9) is also complaining about the secure connection and reports NET::ERR_CERT_DATE_INVALID, and when prompted for details it reports that the site's certificate expires on Jan 26, 2022. One may note that this date is in the future, albeit not by a lot. The laptop in question does admit the current date is in fact January 14. So I'm not sure why it's complaining about this when other computers/browsers aren't. Though it does look like our certificate needs updating in less than a couple weeks.


Update: looks like said laptop is throwing the same errors for some other websites with certificates expiring later in the year (including gamefaqs for example), so it's not anything to do with our certificate specifically. I probably just need to ruthlessly clear some caches or something. So, hopefully we're just on top of getting ours renewed soon. TIA to the TT support crew!

 

[Lady]

we use Let's Encrypt, which became a thing because it allowed you to generate ssl certs for free because they found a CA that would let them issue short term certs, initially 1 month I think, and maybe now up to 3 or 6 months. Incidentally, the cert I see for https://talking-time.net says it expires on Mar 27 '22. Also, this process is largely automated since it has to be repeated so often.

Have you used this particular computer to connect to any sites using Let's Encrypt since say September? You may wish to add the root CA referred to in this article to your key chain https://eclecticlight.co/2021/09/21...about-to-have-a-security-certificate-problem/

 

[Kirin]

Ooh, I bet that's my issue. Thanks Lady!

 

[LBD_Nytetrayn]

Anyone else find that embedded tweets are REALLY slow to load now?

 

[Bongo]

I'm seeing that on other sites as well, not just here. I think it's Twitter's fault.

 

[lincolnic]

I've had slow-loading tweets here on Talking Time for a while now, but they're fine for me on other sites.

 

[LBD_Nytetrayn]

Yeah, it's been this way for me for a bit... I thought it would clear up, but apparently hasn't.

I don't think I've noticed it elsewhere, but I can't say with 100% certainty, though if I have, I don't think it's as slow as it's been here.