Source: https://faq.remarkbox.com/a8d5cc7c-894c-11ea-93a8-040140774501
Snapshot: 2026-05-01T12:38:29Z
Generator: Remarkbox 763cacb

This is a subthread snapshot. The living document lives at the source URI above — it may have been edited, extended, or replied-to since.

Scan for living source

I'm getting the same problem. I've set up my own account fine, but when I try a test comment with another email, clicking the link (or pasting it) just takes me back to the post with the comment, still unverified.

See here: https://devilgate.org/blog/2020/04/25/repairability-is-good/. The "This is a comment from someone else" is me using another email address.

russell — Apr 28, 2020 09:03 am

Once logged in you should be able to verify unless you accidentally used the wrong email address.

You may need to use a separate browser (or private/incognito mode) since we use cookies to track the authenticated user. A user is able to verify (or deny/disable) all comments attributed to their email address.

Try going to https://my.remarkbox.com/u/<username> to view all comments from a user. Try replacing <username> with the unverified user's display name.

For example, your comments for your main user are here:

devilgate — Apr 29, 2020 10:06 am

Thanks, Russell, that was helpful. I tried a private browsing window, but it still took me back to the blog post without giving me the chance to verify. However, I realised the URL has a parameter forcing the return to the post. I removed that part, and I was able to get to the user page and verify the comment.

This seems like a bug. The URL that was emailed to me was:

https://my.remarkbox.com/join-or-log-in?email=martin%40tinlion.software&raw-otp=qUpv3IjKNr3MF9LiEI5cYohU3H79zEZn&return-to=https://devilgate.org/blog/2020/04/25/repairability-is-good/#516d23dd-8949-11ea-93a8-040140774501

And I edited it to:

https://my.remarkbox.com/join-or-log-in?email=martin%40tinlion.software&raw-otp=qUpv3IjKNr3MF9LiEI5cYohU3H79zEZn

Until I did that, I had no chance to see what username had been allocated for the test email address, so no way I can see of getting to anything useful on this site.

devilgate — Apr 30, 2020 05:02 pm

I posted another reply yesterday, but it doesn't seem to appear here. I can see it on my profile, though, so I'm not quite sure what's happening. Anyway, what I said is this:

Thanks, Russell, that was helpful. I tried a private browsing window, but it still took me back to the blog post without giving me the chance to verify. However, I realised the URL has a parameter forcing the return to the post. I removed that part, and I was able to get to the user page and verify the comment.

This seems like a bug. The URL that was emailed to me was:

https://my.remarkbox.com/join-or-log-in?email=martin%40tinlion.software&raw-otp=qUpv3IjKNr3MF9LiEI5cYohU3H79zEZn&return-to=https://devilgate.org/blog/2020/04/25/repairability-is-good/#516d23dd-8949-11ea-93a8-040140774501

And I edited it to:

https://my.remarkbox.com/join-or-log-in?email=martin%40tinlion.software&raw-otp=qUpv3IjKNr3MF9LiEI5cYohU3H79zEZn

Until I did that, I had no chance to see what username had been allocated for the test email address, so no way I can see of getting to anything useful on this site.

russell — Apr 30, 2020 07:18 pm

Hey Devilgate,

Sorry about that.

Your comments are safe! Currently Remarkbox isn't rendering a "load more" button so, which means all comments past a certain "depth" (I think 4) are hidden from view.

For the moment I have enabled Grouped Conversation mode for the faq.remarkbox.com Namespace so that I can see your comment.

In the meantime, I agree this is a bug, any issue in the sign up flow is a defect of the sign up flow.

If you have any recommendations on how to fix this flow please let me know!

devilgate — May 04, 2020 01:55 pm

No problem, Russell, I thought it might be something like that.

If you could make it send the URL in the form that I got to work, I think that would be a start. That is, remove the part starting &return-to=.

On the other hand, the intent of that parameter is no doubt so that the user can get back to the comment after verifying, so removing it might be a problem. Keeping that parameter in, but presenting the verification option before acting on it would be the ideal, I suppose.

SirShanksalot — Jul 12, 2020 10:20 pm

Just noting this is still an ongoing issue. Thanks to devilgate's tip, the workaround of truncating the variables from your URI works fine.


Source: https://faq.remarkbox.com/a8d5cc7c-894c-11ea-93a8-040140774501
Snapshot: 2026-05-01T12:38:29Z
Generator: Remarkbox 763cacb