Author Topic: NASASpaceflight.com and NSF Forum Bug Reports (Read 138086 times)

Spider1 · « **Reply #60 on:** 02/05/2021 09:50 am »

Thank you for your help, Chris, on behalf of myself and my dad. Optus are not being helpful, it is definitely the source of the issue.
Thanks again.

russianhalo117 · « **Reply #61 on:** 02/06/2021 06:32 pm »

Someone resurrected this old thread and has permanently broken for me on Firefox 85.0.1 on MacOS 11.1
https://forum.nasaspaceflight.com/index.php?topic=27791.msg2189133#new

gongora · « **Reply #62 on:** 02/06/2021 07:29 pm »

Quote from: russianhalo117 on 02/06/2021 06:32 pm

Someone resurrected this old thread and has permanently broken for me on Firefox 85.0.1 on MacOS 11.1

There was a broken (list), and it got quoted a couple times, should be fixed now

russianhalo117 · « **Reply #63 on:** 02/06/2021 07:42 pm »

Quote from: gongora on 02/06/2021 07:29 pm

Quote from: russianhalo117 on 02/06/2021 06:32 pm
Someone resurrected this old thread and has permanently broken for me on Firefox 85.0.1 on MacOS 11.1

There was a broken (list), and it got quoted a couple times, should be fixed now

yep fixed.

Spider1 · « **Reply #64 on:** 02/08/2021 06:29 am »

Hi Chris,
I received this from my Dad today following contact with Optus, this is their response. Neither of us understand phishing, any ideas? I’m thinking he may just have to change internet providers?
Hopefully this photo loads.
Thanks for trying to help.

Chris Bergin · « **Reply #65 on:** 02/09/2021 12:23 am »

Sounds like nonsense. The forum is hosted by Digital Ocean. Cloudflare is the DNS. Passed it on to the webmaster

bstrong · « **Reply #66 on:** 02/09/2021 01:16 am »

Hmm, this actually looks like a legitimate issue:

https://cxsecurity.com/issue/WLB-2019030006

I tried, and it does in fact work on this site, which is a problem for reasons explained here:

https://www.netsparker.com/blog/web-security/open-redirection-vulnerability-information-prevention/

It is not impossible that Optus has found someone exploiting it for phishing attacks.

NSF Webmaster · « **Reply #67 on:** 02/09/2021 07:21 pm »

Quote from: bstrong on 02/09/2021 01:16 am

Hmm, this actually looks like a legitimate issue:

https://cxsecurity.com/issue/WLB-2019030006

I tried, and it does in fact work on this site, which is a problem for reasons explained here:

https://www.netsparker.com/blog/web-security/open-redirection-vulnerability-information-prevention/

It is not impossible that Optus has found someone exploiting it for phishing attacks.

Thanks for pointing this out! A fix was implemented minutes ago and the "exploit" (redirect) doesn't work anymore to sites other than NSF itself.

widow18 · « **Reply #68 on:** 02/10/2021 06:54 pm »

I am back on. Thanks to Bstrong and webmaster.

Peter

Hog · « **Reply #69 on:** 02/10/2021 07:23 pm »

Quote from: widow18 on 02/10/2021 06:54 pm

I am back on. Thanks to Bstrong and webmaster.

Peter

Welcome (back) to NASA Spaceflight.com!

Spider1 · « **Reply #70 on:** 02/10/2021 08:22 pm »

So I can stand down?
Thank you everyone involved.

Chris Bergin · « **Reply #71 on:** 02/10/2021 08:37 pm »

Quote from: Spider1 on 02/10/2021 08:22 pm

So I can stand down?
Thank you everyone involved.

Yep! Thanks for the information and check your messages (PMs - the thing at the top of the forum) as we've got a thank you for your Dad when he gets back in one way or the other.

endlesslimitation · « **Reply #72 on:** 02/12/2021 05:49 pm »

It looks like the 'Carbon capture x prize' thread previously in the 'advanced concepts' section has disappeared. I think it happened in the last ten minutes or so after I made a comment - did I brake it?

gongora · « **Reply #73 on:** 02/12/2021 05:53 pm »

Quote from: endlesslimitation on 02/12/2021 05:49 pm

It looks like the 'Carbon capture x prize' thread previously in the 'advanced concepts' section has disappeared. I think it happened in the last ten minutes or so after I made a comment - did I brake it?

The thread is really not on-topic for this forum.

endlesslimitation · « **Reply #74 on:** 02/12/2021 05:55 pm »

fair enough - but it inspired some interesting discussion nonetheless. Did it get moved to another section? Or simply deleted?

the_other_Doug · « **Reply #75 on:** 03/26/2021 09:53 am »

New odd bug:

I opened the SpaceX Missions topic and, as I normally do, clicked on the NEW icons next to threads which have new posts since the last time I looked at them. The last thread I clicked on in this manner was the Crew 1 discussion thread, which did have two new posts about the alarms that were spuriously sounded from Resilience overnight last night.

However, when I clicked the NEW icon, instead of being brought to the new post from today (the first new post in that thread since December of 2020), I was brought to Reply #548, posted on 11/15/20 I believe. Literally hundreds of posts prior to the new post. And before y'all ask, yes, I had already displayed and read the hundreds of posts between the post displayed and the actual newest, unread posts. Put it this way, I have my forum settings set to show 100 posts per page. The NEW icon opened me up to page 11, while the latest posts are on page 15. That is be definition hundreds of posts...

This happened at about 5:40am CDT. I'm awful at remembering what the offset is in both standard and daylight savings times, but I think that's about 10:40 UTC.

That's the first misdirect I've seen using the NEW icons in, like, forever. Figured it caught my attention, so I'd report it.

xor · « **Reply #76 on:** 03/26/2021 03:41 pm »

Quote from: the_other_Doug on 03/26/2021 09:53 am

New odd bug:

I opened the SpaceX Missions topic and, as I normally do, clicked on the NEW icons next to threads which have new posts since the last time I looked at them. The last thread I clicked on in this manner was the Crew 1 discussion thread, which did have two new posts about the alarms that were spuriously sounded from Resilience overnight last night.

However, when I clicked the NEW icon, instead of being brought to the new post from today (the first new post in that thread since December of 2020), I was brought to Reply #548, posted on 11/15/20 I believe. Literally hundreds of posts prior to the new post. And before y'all ask, yes, I had already displayed and read the hundreds of posts between the post displayed and the actual newest, unread posts. Put it this way, I have my forum settings set to show 100 posts per page. The NEW icon opened me up to page 11, while the latest posts are on page 15. That is be definition hundreds of posts...

This happened at about 5:40am CDT. I'm awful at remembering what the offset is in both standard and daylight savings times, but I think that's about 10:40 UTC.

That's the first misdirect I've seen using the NEW icons in, like, forever. Figured it caught my attention, so I'd report it.

I can confirm the same odd behavior on the same Crew-1 thread at 1:50am EDT, and whatever caused it happened in the previous hour or few.

This is the "New" link I was given:

https://forum.nasaspaceflight.com/index.php?topic=50525.msg2154284#new

It was so far back, I checked it a couple of times and couldn't make sense of how it happened this time.

Normally it's either edited, or more usually deleted and the link does its best job to land at whatever post follows that.

The odd thing here is this is the first post in a while that still existed as a valid target (i.e. wasn't deleted), and wasn't obviously edited.

AFAICT, Crew-1 thread metadata had its own SEU.

Arb · « **Reply #77 on:** 03/26/2021 08:26 pm »

Quote from: xor on 03/26/2021 03:41 pm

Quote from: the_other_Doug on 03/26/2021 09:53 am
New odd bug:

I opened the SpaceX Missions topic and, as I normally do, clicked on the NEW icons next to threads which have new posts since the last time I looked at them. The last thread I clicked on in this manner was the Crew 1 discussion thread, which did have two new posts about the alarms that were spuriously sounded from Resilience overnight last night.

However, when I clicked the NEW icon, instead of being brought to the new post from today (the first new post in that thread since December of 2020), I was brought to Reply #548, posted on 11/15/20 I believe. Literally hundreds of posts prior to the new post. And before y'all ask, yes, I had already displayed and read the hundreds of posts between the post displayed and the actual newest, unread posts. Put it this way, I have my forum settings set to show 100 posts per page. The NEW icon opened me up to page 11, while the latest posts are on page 15. That is be definition hundreds of posts...

This happened at about 5:40am CDT. I'm awful at remembering what the offset is in both standard and daylight savings times, but I think that's about 10:40 UTC.

That's the first misdirect I've seen using the NEW icons in, like, forever. Figured it caught my attention, so I'd report it.

I can confirm...

Likewise

gemmy0I · « **Reply #78 on:** 03/26/2021 09:41 pm »

Quote from: the_other_Doug on 03/26/2021 09:53 am

The last thread I clicked on in this manner was the Crew 1 discussion thread, which did have two new posts about the alarms that were spuriously sounded from Resilience overnight last night.

...

However, when I clicked the NEW icon, instead of being brought to the new post from today (the first new post in that thread since December of 2020), I was brought to Reply #548, posted on 11/15/20 I believe.

I encountered something similar, with that exact thread IIRC.

I've noticed that this frequently happens when the mods have merged two threads together, particularly if the "side thread" being merged in is itself substantial and/or spread out in time. It seems to confuse the forum software's ability to remember "where have you left off in this thread".

I've noticed it always happens after merges because I'm subscribed to email notifications for most threads I'm interested in, and (by default) notifications go out for splits and merges as well as for new replies.

When it works "right", it takes you to the oldest newly-merged-in post in the resultant thread. If that's older than the last post you'd previously read in the pre-merge thread, it will have the effect of "rewinding" you to the merge point. So, for instance, if a side thread was merged in which had some posts going back a month that you hadn't read (perhaps because you weren't following that thread when it was freestanding), it'll drop you into the merged thread starting a month ago.

Sometimes, though, the forum software seems to just get confused and give up, in which case it'll drop you at the first post and leave you to figure out what the heck happened. Other times it "rewinds" to a post somewhere in the middle whose connection to the merge is non-obvious (but presumably makes sense somehow in the database's internal representation).

Given that this is connected to merges, I suspect this erratic behavior is due to deeper limitations in how the forum software tracks thread reading progress across merges. As any programmers who've worked with revision control systems like Git or Subversion are no doubt painfully aware, merging is actually a very complex topic, algorithmically speaking, and it's not always obvious (or easy to compute) what the "best" resolution is.

gemmy0I · « **Reply #79 on:** 04/02/2021 08:42 pm »

(Posting this here because I can't find a specific thread for discussion of the relevant article. Mods, feel free to move this to somewhere more appropriate.)

Just wanted to make the site admins aware that many of the inline images in this recent article on the NSF main site are broken:

https://www.nasaspaceflight.com/2021/04/blue-origin-complex-progress-new-glenn/

Specifically, this seems to affect all the images that are captioned as "via L2". Closer inspection reveals that these images were hotlinked directly from attachments on the forum side of NSF rather than actually uploaded to the WordPress side in connection with the article. Presumably these images are attached to posts in the L2 section, which is why they are failing to load in the article for those who aren't L2 members. (I can see how this mistake might've been missed when the article was posted, because the authors are presumably L2 members themselves and thus their browsers would've had the appropriate login cookies to give them access to the images.

)

I've attached a screenshot showing what the problem looks like from a non-L2-member's perspective. In the screenshot I've opened Chrome's developer console to inspect the broken image and highlight the problematic hotlink URL.

FYI, I've also noticed similar "broken image" issues on several recent main-site articles. I haven't checked those in detail but I would guess they are broken for the same reason.