Is this possible to have multiple accounts with the same email address?
Technical Support
1
Posts
1
Posters
0
Views
-
@zielony-xd@community.nodebb.org the email confirmation logic will probably unset any other users with that email.
You can set the email with setUserField, but it would not be confirmed.
It is likely just to prevent users sharing emails.
Perhaps you can try
username+differentiator @example.com?
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@zielony-xd@community.nodebb.org the email confirmation logic will probably unset any other users with that email.
You can set the email with setUserField, but it would not be confirmed.
It is likely just to prevent users sharing emails.
Perhaps you can try username+differentiator @example.com?
-
The setting itself pre-dates AP integration so that's why I am unsure.
How it works is, on the NodeBB side, when the picture is requested, you need to be logged in to be able to load it. This isn't restricted by category, but rather is site-wide.
This likely applies to federated content too. If the setting is enabled then the images will not be visible when federated out.
All bets are off with S3 plugin. Most likely it ignores this option, as the media has been uploaded to S3 it is outside of NodeBB's control and we cannot gate access.
-
@panos@community.nodebb.org my best guess is you wouldn't be able to guarantee restricted access to the files if you use the S3 bucket.
As far as I know that setting doesn't influence anything when using a third party file store.
-
Can you try once more?
-
Unfortunately, I think you have to turn off the bot challenge completely. CF puts up a javascript challenge that wget and curl cannot bypass.
-
@djensen47@community.nodebb.org could it be maybe Claude Code has cached the site? I'm not exactly sure what else to turn off 😛
-
I have the same problem with Claude Code on my site but my site isn't for developers. 😉
-
It works from the web/desktop client.
It fails with Claude Code:
Unfortunately, the NodeBB docs site (docs.nodebb.org) is behind Cloudflare challenge protection, which blocks automated fetching. The pages return only Cloudflare's JavaScript challenge script instead of the actual content.
