FAQ

So you can log in with either one, even after the other stops working -- e.g. a school email once you graduate, or a work email if you change jobs. Add one you'll always have access to (like a personal address) alongside the one you're using today.

Your real name is private by default -- both "show first name" and "show last name" start unchecked when you register, especially since this platform is used by minors. Turn either one on from Account Settings any time you want your name shown instead of your username.

Once, for free. After that self-service change is used, only an account manager or the owner can grant you another one from the admin side -- ask a moderator if you need a second change.

There's no self-service password reset yet. Contact a moderator with proof you own the account (e.g. reply from one of your two registered emails) and they can help from the admin side.

No. Your emails are only ever visible to you, and to admin/account managers if they need to look something up. No other user can see either of your email addresses anywhere on the site.

It means that person has a Professional account -- our paid tier. Professional accounts get full read/write/delete access to their own blogs through the public API, not just through the website.

Right now, Professional access is granted manually -- either by an admin/account manager, or automatically if you register with an email from a school or organization that has an active domain exemption with us (ask your school if they've set one up). Self-serve checkout isn't live yet.

The free Professional grant only applies at registration -- if your school's domain was added after you already signed up, register a note with a moderator so they can grant it manually. If you haven't registered yet, make sure to use your school email as one of your two emails when you sign up.

Sign in, go to Account Settings → API Keys, and generate one. Keep it secret -- anyone with your key can read your blogs, and if you're a Professional account, write/edit/delete them too.

A 401 means the request has no key, or the key is invalid/revoked. Double check you're sending it as `Authorization: Bearer <your key>` exactly, with no extra quotes or whitespace, and that the key hasn't been deleted from Account Settings.

Writing through the API (creating, editing, deleting your own blogs) is a Professional-tier feature. Reading your own blogs works for everyone; writing needs a Professional account. See the previous question for how to get one.

The /docs page has every endpoint, request/response shapes, and copy-pasteable code for curl, JavaScript/fetch, Python, React, and Next.js.

This platform is used by minors, so profanity is automatically filtered out of blog titles, excerpts, content, and comments. Rephrase without the flagged words and it'll go through.

Links, bare domains, IP addresses, and email addresses aren't allowed anywhere in blog content or comments -- even written in sneaky ways like "example dot com" or "example[.]com". This applies to anything that points off this site, not just clickable hyperlinks. If you were flagged by mistake (e.g. a normal sentence with a period got misread), try rewording that part.

A private post is only visible to you (and, if you're an API user, to you through your own API key). A public post shows up everywhere -- the homepage, /blogs, your profile, tag pages -- and notifies anyone following you.

Open the post and use the Edit page to switch it back to Private, or delete it outright from there or from your My Blogs list.

Open the post and click the Report button, then describe what's wrong. A moderator will review it -- reporting doesn't remove the post by itself, that only happens after review.

Try logging in as normal -- the login page will show you the reason, and if it's a suspension, how long it lasts. From that same screen you can submit a formal written response, which gets saved on your account for a moderator to review.

There's no fixed turnaround time posted yet -- a moderator reads appeals from the admin panel. If it's been a while, that's worth telling the team directly rather than assuming it was missed.