How the network works.

A focused developer network for short build logs, long-form technical notes, shipped projects, profiles, messaging, and collaboration.

Verification protects account recovery and prevents disposable or mistyped addresses from becoming active profiles.

Check spam, wait briefly, then request one new code. Only the newest code is valid. If SMTP delivery still fails, open a support ticket.

Use a unique password, review active devices in Settings, log out sessions you do not recognize, and never share an email code.

Short, honest progress: what moved, what failed, a milestone, or the next technical decision. Progress can be tracked from zero to one hundred percent.

A blog-style technical article that preserves a durable lesson, implementation detail, comparison, or postmortem.

Show the result, problem, implementation, stack, source link, live demo when available, and real screenshots.

Field notes and shipped work can remain private drafts in the database until you publish. The editor does not store unpublished copies in browser local storage.

Useful actions earn XP and contribution signals. Reputation is context, not a guarantee of identity, skill, or endorsement.

Choose everyone, followers, or nobody in Settings. Blocking and moderation controls still take priority.

Private spaces for small teams to coordinate a build, share updates, and keep related activity together.

Use the report action where available or send a support ticket with the profile, content link, and specific concern.

Production uploads are stored in the configured Supabase Storage bucket. The application does not use a local uploads folder.

Yes. Settings provides a JSON export covering your profile and core publishing records.

It removes your account, public content, and associated media. Treat it as permanent and export anything needed before confirming.

Open the Support page and include the page, action, approximate time, exact error, and steps to reproduce. Never include credentials or verification codes.