Verifying your Rentry URL

This guide is to help people regain access to their URLs if they have forgotten the edit codes.

Preparation

Use the following format to attach verified accounts to a post, that can later be used for us to verify you as the owner. When we see this format used, we will only verify using the instructions within it.
If you do not provide this, we will verify using any links within the page that lead to a profile, such as a Twitter account.
Any other instructions given to us in any other way will be ignored!

Put this at the very top of your code. It starts with a comment, so will not appear on the page itself.

[//]: (VERIFY Twitter: @handle / spotify: https://spotify.com/accountname)

Anything written within this comment will be followed as part of the verification process. Be careful not to change the usernames of profiles you have linked here.

To prevent us from ever resetting your edit code (including for you, we won't accept any forms of verification at all), put None:
[//]: (VERIFY None)
This does not protect it from the claim system.

To privately link an email, you can follow a process called hashing. Follow these steps:

1. Paste your email address into the box on this site (or choose your own alternative). Make sure to remove spaces before and after the email address! https://xorbin.com/tools/sha256-hash-calculator
2. Copy the result into your VERIFY comment and add the type of hash.
   For example (using: support@rentry.co):
   [//]: (VERIFY sha-256: 376a6513b296c2a400d1da515a4cec233c59127082e29deef85271d0f5422495 )
3. Double check by returning to the hash service and pasting your email again. The outcome should be exactly the same.
   Note that if even a single character is different, the hash will be completly changed. It's a non reversible process, making it a safe to provide your hash on your pages.
4. (Optional) Salting
   You may also choose to 'salt' your hashes, to make them even more secure. To do this, add a short code before your email address, and include this in your verify comment like this:
   For example (using: 98h823support@rentry.co):
   [//]: (VERIFY sha-256: 98h823:555f5f397ace77d21d329ccb4c96dfdd44d1d884829a95b8220fe505ccb3cf1a )
   Note that even this will not stop someone that knows your email and is guessing your identity by trying multiple options and figuring it out. This won't allow them to steal your URL, but it will let them figure out who you are.
5. Verifying
   To verify after using this method, you must email us from the address used for this hash. If we can hash it to be the same as the hash in your VERIFY comment, we can reset the edit code for you.

We have a better solution for this baked into the next update, so this extra complication will not be necessary for too long.

Recovery

Please follow these steps:

1. Select a link within your page that you still have control over. For example a Twitter profile, a carrd page, a Retrospring page.

   If you set a VERIFY comment, you must use something mentioned in there.

2. Tell us which one you have chosen. Let us know if it is something you can edit or an email.

If you have chosen something you can edit:

1. We will give you a randomised code, like this: *nfni3avh
2. Edit this code into the page your Rentry links to.
3. Let us know and we will validate it.

If you chose an email:

1. Email us from the account mentioned.

Note that links to Rentry pages cannot be used to verify, as this was open to abuse through the claim system.

Notes on Evidence

Screenshots are not permitted as evidence, as they are too easily faked.
We may use your IP as evidence of ownership, however this requires that there are no signs of a trade.
Showing that you are the most recent claimer may allow us to verify you, but only if there are no signs of a trade.

Notes on Modify Codes

In order to prevent people with your modify code stealing your URL through verification, we have the following internal rules:

• The latest edit must not be a modify.