case: (Default)
Case ([personal profile] case) wrote in [community profile] fandomsecrets2025-07-01 05:04 pm

[ SECRET POST #6752 ]


⌈ Secret Post #6752 ⌋

Warning: Some secrets are NOT worksafe and may contain SPOILERS.


01.



__________________________________________________



02.



__________________________________________________



03.



__________________________________________________



04.



__________________________________________________



05.



__________________________________________________



06.



__________________________________________________



07.




















Notes:

Secrets Left to Post: 01 pages, 20 secrets from Secret Submission Post #965.
Secrets Not Posted: [ 0 - broken links ], [ 0 - not!secrets ], [ 0 - not!fandom ], [ 0 - too big ], [ 0 - repeat ].
Current Secret Submissions Post: here.
Suggestions, comments, and concerns should go here.

Re: Anyone in the loop with DW news?

(Anonymous) 2025-07-01 11:10 pm (UTC)(link)
What's wrong with the captcha?

Re: Anyone in the loop with DW news?

(Anonymous) 2025-07-01 11:13 pm (UTC)(link)
More often than not it will not let me post and go to an antispam page where you have to enter the capatcha to prove you're a human, but the captcha is broken so in the end you can't post at all.

Re: Anyone in the loop with DW news?

(Anonymous) 2025-07-02 01:11 am (UTC)(link)
This has happened to me, as well. I wound up filing a bug report on June 9th, and the person at support was nice, but most of what they said was just:

"Sorry about the captcha issue - we're not sure what's going on with the server that issues those challenges. We're waiting for additional information. In the meantime, you won't be able to comment anywhere that a captcha is required unless the journal owner switches to using one of our other available captcha provider options."

I haven't had comments rejected in a while, and I would've felt like I was imposing if I asked Case to change how FandomSecrets does things. Especially because I could not tell if anyone else was encountering the bug.

If anyone else knows more, though, I'd be interested in hearing about it, too.