How ArabDev protects your account, and what you can do to help.
How passwords are stored
ArabDev never stores your password. It stores a one-way hash made with Argon2id, a method designed to be slow and memory-hungry for anyone trying to guess passwords. Even the people running ArabDev cannot see your password. When you sign in, ArabDev hashes what you typed and compares the results.
Confirmation codes
A password can be guessed, reused from another site or read over someone's shoulder. So the actions that matter most are confirmed with a six-digit code sent to your email:
- Creating an account. The account is created only once the code is entered, so a mistyped address cannot leave behind an account nobody can reach.
- Signing in, unless you switched this off under Settings → Security.
- Changing your email. The code goes to the new address.
- Changing your password. The new password takes effect only when the code is entered.
The screen shows which inbox to check, partly hidden (for example l***a@example.com), and a countdown. The code:
- arrives from noreply@arabdev.site, with the code at the start of the subject line;
- is valid for 10 minutes and works once;
- allows five tries; after that, start again;
- can be sent again after 60 seconds, up to four times. Only the newest code works.
Typing the sixth digit submits the code; you do not need to press a button. ArabDev stores only a keyed hash of each code, never the code itself.
Never share a codeArabDev will never ask you for a code or your password, by email, message or anywhere else. If someone asks, it is an attempt to take over your account.
Security alerts
ArabDev emails you when your password changes and when a new browser signs in, with the browser and network address it used, so you can tell whether it was you. When your email address changes, the old address is always told. You can switch the other alerts off under Settings → Security.
Authenticator app
An authenticator app on your phone makes a new six-digit code every 30 seconds. With one turned on, signing in needs your password and the code the app shows at that moment, so someone who learns your password still can't get in. ArabDev works with Google Authenticator, Microsoft Authenticator, 1Password, Authy and any other app that supports standard time-based codes (TOTP).
Turning it on
- Go to Settings → Security and choose Set up next to Authenticator app.
- Enter your password.
- Scan the QR code with the app. If you can't scan it, add the account by hand with the key shown under it.
- Type the six-digit code the app shows, and choose Turn on.
- Save the ten recovery codes that appear: copy them, download them as a file, or write them down. You won't see them again.
From then on, after your password ArabDev asks for the code from your app instead of emailing you one. You get five tries; after that, start signing in again. A code that has already been used is refused, even before it changes in the app.
Recovery codes
Each recovery code gets you in once, in place of the app's code, if you lose your phone or it is reset. Settings shows how many you have left. New recovery codes makes a fresh set of ten and cancels the old ones. Recovery codes are stored only as one-way hashes, so ArabDev can't show them to you again.
Turning it off
Choose Turn off under Settings → Security and enter your password and a code from the app (or a recovery code). Your recovery codes are deleted, and signing in goes back to emailed codes if you have those switched on.
With account alerts on (they are by default), ArabDev emails you when the app is turned on or off, when a recovery code is used, with how many are left, and when new recovery codes are made.
Leaked passwords
Passwords stolen from other sites end up in lists that attackers try everywhere. When you choose a new password, ArabDev checks it against the Have I Been Pwned list of passwords from public breaches and refuses it if it is there, with the message "This password has turned up in a data breach". Your password is not sent: only the first five characters of its SHA-1 hash are, and the comparison happens on ArabDev's server. If the list can't be reached, the password is accepted.
The security check
Cloudflare Turnstile checks that a real browser, not a script, is sending a request. Signing in, signing up, resetting a password, changing your email or password, publishing and commenting each get a check of their own. Everything else you do while signed in (likes, saves, reposts, follows, blocks, reports, uploads, drafts, edits and profile changes) is covered by a check that runs in the background about once every 30 minutes. For almost everyone all of this is invisible. Once in a while Cloudflare shows a small box to tick, above a button or at the bottom of the screen.
- Each pass from Turnstile is used once and expires after five minutes, and ArabDev checks it with Cloudflare before doing anything. The background check is traded for a 30-minute pass that works only for your account; signing out everywhere or changing your password cancels it.
- If you see "Please complete the security check and try again" or "We couldn't confirm you're not a robot", reload the page and try again. Strict privacy extensions or blocked scripts from challenges.cloudflare.com can stop the check from running.
- Turnstile does not tell ArabDev who you are, and its result is not stored.
How sessions work
- When you sign in, your browser receives a short-lived access pass that lasts 15 minutes and is kept only in the page's memory, never in storage.
- A longer-lived sign-in cookie renews that pass automatically. The cookie is HttpOnly, so scripts on the page cannot read it, and it is only sent to ArabDev's sign-in endpoints.
- Every renewal replaces the cookie with a new one. If an old cookie is ever used again, which is a sign it was copied, ArabDev ends that whole session. A short grace period prevents this from happening by mistake when two tabs renew at the same moment.
- The server stores only a hash of each sign-in cookie, the browser description, and when it was created and when it expires.
- You can see every signed-in browser under Settings → Security → Where you are signed in, and end any of them.
Signing out
Choose Sign out from the account menu. This ends the session on that browser and removes the sign-in cookie. To sign out somewhere else, use Where you are signed in. Changing your password or resetting a forgotten password signs you out of every other browser too.
Resetting a forgotten password
- On the sign-in page choose Forgot password?
- Enter the email address you signed up with and choose Send reset link.
- ArabDev always answers the same way, whether or not the address has an account, so nobody can use this form to find out who is registered.
- Open the link in the email within 30 minutes. It works only once. Each inbox receives at most five reset emails an hour.
- Choose a new password. All your existing sessions are signed out, you receive an email confirming the change, and you can sign in with the new password.
Protection against guessing and abuse
ArabDev limits how often sensitive actions can be repeated. When a limit is reached you see "Too many attempts. Wait a moment and try again." The limits are shared by all of ArabDev's servers, and the network address they count is the one ArabDev's own hosting recorded, which a visitor cannot fake.
| Action | Limit per network |
| Sign in | 10 per minute |
| Create account | 10 per hour |
| Enter a confirmation code | 20 per 5 minutes |
| Send another code | 10 per 15 minutes |
| Forgot password | 5 per 15 minutes |
| Reset password | 10 per 15 minutes |
| Change email | 10 per 15 minutes |
| Change password | 10 per 15 minutes |
| Delete account | 10 per 15 minutes |
| Download my data | 5 per hour |
| Username and email availability checks | 60 per minute |
| Session renewal | 60 per minute |
| Publish a post | 30 per hour |
| Comment | 60 per 10 minutes |
| Like, save and repost | 300 per hour |
| Follow | 120 per hour |
| Upload an image | 30 per 10 minutes |
| Search | 120 per minute |
| Report a post | 10 per hour |
Some limits also apply to each account, however many networks the attempts come from:
| Action | Limit per account |
| Sign in | 8 attempts per 15 minutes |
| Password reset emails | 5 per hour for each inbox |
| Wrong confirmation codes | 5 per code |
| Reports | 20 per day |
Other protections
- Every request that changes something is checked on the server. The buttons you see in the app are for convenience; permission is always decided by the server.
- Post content is cleaned on the server and again in the browser. See What happens to your post when you publish.
- Uploads are decoded as images and re-encoded; any other kind of file is refused. An image's size is read from its header first, so an oversized image is refused before it is ever decoded.
- Every page is sent with security headers: browsers must use HTTPS, no other website can show ArabDev inside a frame, plugins and forms that post elsewhere are blocked, files are never guessed as another type, and camera, microphone, location and payment access are switched off.
Tips
- Turn on an authenticator app, and keep the recovery codes somewhere other than your phone.
- Use a unique password for ArabDev and keep it in a password manager.
- Keep Email me a code when signing in and the account alerts switched on.
- Protect the email account itself with its own two-step verification: whoever reads your inbox can confirm codes.
- Uncheck "Keep me signed in" on shared or public computers, and sign out when you are done.
- Check Where you are signed in now and then. If you think someone else knows your password, change it: that signs every other device out.