ALIAS doesn’t actually exist in DNS and must be simulated with A records. My guess is that Heroku changed things and PointDNS didn’t handle that correctly in its simulation. See here for details (from a different DNS provider but talking about the same issue).
But when I try connecting to each of the returned addresses over non-secure HTTP, each one seems to be the right site (they each had an X-Clacks-Overhead header and they each tried to set _glowfic_session). That’s not what I’d expect if it were a DNS error.
DanielH wrote:But when I try connecting to each of the returned addresses over non-secure HTTP, each one seems to be the right site (they each had an X-Clacks-Overhead header and they each tried to set _glowfic_session). That’s not what I’d expect if it were a DNS error.
I think I'm not understanding this. Did you see lexile or bluefin returned when connecting to the http version of glowfic.com? I've only seen it mentioned for https so far.
I don’t connect to the http version, so I haven’t seen that happen but that’s not evidence. Not seeing anybody report it is some evidence, but I don’t know how many people use http so it was worth checking.
Marri wrote:Also, I'm going through a really miserable cold. I've cycled through fever and chills, headache and sore throat, miserable cough, and am now onto the "horribly congested to the point where it makes me tear up constantly and my eyes hurt and I can't look at screens". I'm presently drugged enough to have managed responding, since I didn't want to get too behind on it, but I could do a response at a time then take a break; actually doing things that require uninterrupted screen staring (like coding) is so extremely on hold till I'm functional. Apologies to everyone and in particular Throne, who is wonderful and very helpfully sent me many pull requests I'm in no shape to review.
Hugs.
Also, can I just say: what the hell, certificate errors? I mean, I haven't experienced any yet, but, this sounds like An Issue. (And I'm likewise pretty sure it's not our fault.)
Heroku got back to me and blamed PointDNS, PointDNS got back to me with a list of questions. I was correct that they wanted to know if was www or root or both, yay past!me asking; sent them a longer response and we'll see what they say.
Apparently if I mark unread from the first page, the thread becomes not “opened”. It seems to me that having it be “opened” but fully unread would make “opened” a better fit to “thread I want to follow/finish reading”.
OTOH, if we did that I'd want some way to mark a thread unopened (in case I opened one by accident, or to check something, or tried it and decided I didn't want to follow it).
Personally, I use "favorites" for "thread I want to follow/finish reading."
Unbitwise, clicking the eye on the first reply does what you want. Marking the thread unread from the menu of thread options does what Moriwen said in her first paragraph.
Follow ups from PointDNS and Heroku make it sounds like Heroku rotates our IP address and then PointDNS doesn't update fast enough. PointDNS lowered our TTL so this should be happening less; still waiting on Heroku to explain why, when they rotate our IPs (normal) the old one points to someone else's website rather than being unrecognized (not normal).
If I standardize people on something, I'll probably standardize on www to avoid this nonsense.
