Where is what, and how does it work?

Registration has three preparation steps and an email confirmation.

1. Choose the country of your usual residence. This value is used by central protection rules and cannot simply be overwritten later in the registration form.
2. Read and individually accept every mandatory admission condition. FaceDistrict is for adults aged 18 or over; the date of birth is checked during registration.
3. Create a username and enter a valid email address, a password of at least 12 characters, your real first and last name, date of birth, locality, basic relationship status, gender and who you are interested in. The last name is not shown on the public profile.
4. Upload exactly one JPEG, PNG or WebP profile picture of no more than 10 MB. Apply the fixed 3:4 crop; the published image is 225 × 300 pixels. The server keeps the processed AVIF version, not the original upload.
5. The live availability hints are helpful, but the final server check decides whether the username and email address can be used.
6. An 8-character confirmation code is sent by email and is valid for 10 minutes. Registration is completed only after the correct code is entered.
7. The language selector remains available throughout registration. A first visit starts in English; a chosen language is remembered.

Important: Never share confirmation codes or passwords with another user.

Use the login page for access and the protected code process for a new password.

1. Log in with either your username or your email address plus your password. A successful login opens Home, not the Dashboard.
2. Use “Forgot password” when access is lost. The page gives the same response for known and unknown addresses so that accounts cannot be discovered by testing email addresses.
3. A valid active account receives an 8-digit code. The modal shows a 10-minute countdown; after too many incorrect attempts the process must be restarted. Requests are also rate-limited.
4. After the code is accepted, enter the new password twice. It must contain at least 12 characters. Saving it invalidates existing sessions for that account.
5. Logout ends the current authenticated session through a protected POST request. Suspended, deleted or otherwise inactive accounts cannot continue using protected pages.

Important: Check the spam folder when an expected code does not arrive, and avoid repeatedly requesting new codes.

The selected language controls all public and logged-in interface texts.

1. The first visit uses English. Selecting another language stores the choice in the session and in a language cookie for later visits.
2. The logged-in menu leads to Home, Dashboard, your public page, Groups, this Wiki, Find friends, Edit profile, Messages and Logout. The bell beside Logout opens personal notifications.
3. On narrow screens the menu can scroll horizontally rather than squeezing every button into unreadable text.
4. About FaceDistrict and the Wiki are also linked in the footer, so both pages remain available from login and registration screens.
5. If old styling remains after an update, reload without the browser cache. This changes only cached files, not account data.

Home is the first page after login and combines profile context, feed and recent community events.

1. The left column shows your own compact profile information. The centre contains the shared feed. The narrow right panel shows the newest 20 activity entries with the newest item at the top.
2. Activities can include new feed posts, newly confirmed friendships and confirmed relationships. Older items automatically move out when the list exceeds 20 entries.
3. Muted and blocked users are excluded from your automatic feed and activity overview. Your own content remains visible to you.
4. The feed can show public posts from active members as well as posts from friends, subject to protection, country and blocking rules.
5. You can choose how many feed posts are loaded: 3, 5, 10 or 50. The current choice is remembered for the session.

The block editor supports text and images, while ownership and reporting rules remain server-controlled.

1. A feed post may contain up to 12 ordered blocks. Text blocks allow up to 5,000 characters each and 12,000 characters in total. A post can contain at most three images.
2. Uploaded feed images may be JPEG, PNG or WebP up to 10 MB. They are processed to a maximum long edge of 1,600 pixels, and a separate preview no larger than 640 × 480 pixels is generated.
3. Only the author sees Edit and Delete for the post. Editing reopens the same block editor. Removing an existing image is final only after saving, so cancelling keeps the original post.
4. Likes can be added or removed. Replies are text-only and may contain up to 2,000 characters; reply image uploads are intentionally unavailable.
5. A report sends the selected category and reason into the moderation case system. Deletion and other destructive actions use the FaceDistrict Yes/No modal, not a browser alert.
6. Feed images receive a one-year expiry time. Expired image files are removed by the automatic cleanup while the remaining text structure can stay available.

Important: Do not place private information in a public feed post merely because the intended reader is a friend.

The activity panel describes community events; the bell describes events that concern you directly.

1. Latest activities on Home are a compact community timeline. Personal notifications are opened with the bell to the right of Logout.
2. The bell can notify you about feed likes and comments, gallery likes, friendship and relationship events, guestbook activity, group events and other supported personal actions.
3. Unread notifications are counted in the badge. Opening an item follows its stored link to the related profile, post, image, guestbook entry or group.
4. “Mark all as read” clears the unread state without deleting the notification history. The panel shows at most the newest 20 entries.
5. The notification counter refreshes automatically while the user remains online; blocked users are excluded from visible notifications.

The Dashboard is for managing your own account content, not for editing the public profile fields.

1. The left column repeats your profile overview, the middle workspace contains the Gallery and Visitors tabs, and the right column is the place for managing friends.
2. The Gallery tab contains one upload control and then only the images that actually exist. New pictures fill the four-column grid in order; there are no 100 empty upload boxes.
3. The Visitors tab shows up to 100 different users who opened your public profile, ordered by the most recent visit. Your own visits are never recorded.
4. Repeated visits by the same person within 10 minutes update the time but do not increase the visit counter. Protection and block rules can prevent a visit from being recorded or displayed.
5. Friend controls in the right column include profile access, muting, removal, blocking and the list of blocked users.

Profile fields, settings and relationships are separated into three tabs.

1. “Your profile” edits the current personal fields and profile picture. The public profile never displays the stored last name.
2. The profile picture is cropped to 225 × 300 pixels and saved as AVIF. Replacing or removing it affects the image shown throughout FaceDistrict.
3. “Settings” controls whether the friend list is visible publicly, whether the guestbook is enabled and whether only confirmed friends may write in it.
4. The “Hide” checkbox beside relationship status controls the separate public status panel. Without a confirmed romantic relationship, the normal profile status is shown when the panel is visible.
5. “Relationships” manages confirmed family and romantic labels with friends. It is not a replacement for the normal profile editor.
6. Interests are edited on their own page. A maximum of five valid interests can be selected in total.

The gallery keeps up to 100 processed pictures and gives each picture its own audience setting.

1. Upload one image at a time and choose 4:3, 3:4, 1:1, 16:9 or 9:16 as the crop ratio. Smaller source images are not enlarged.
2. Landscape results are limited to 1,080 × 768 pixels and portrait results to 768 × 1,080 pixels. The cropped result is stored as WebP; the original upload is discarded.
3. A small non-transparent “FaceDistrict” watermark is burned into the lower-right corner. A separate thumbnail is created for the grid; clicking it opens the larger version.
4. An unchecked image is visible to allowed non-friends. “Friends only” restricts it to confirmed friends. The master checkbox changes all existing image checkboxes before visibility is saved.
5. Public-profile visitors may give a heart to an image they are allowed to see. The owner can delete an image with the custom confirmation modal.
6. After 100 gallery images, another upload is rejected until at least one existing image is deleted.

Friend search combines profile filters with optional common-interest matching.

1. Find friends can filter by username, age range, gender, country, locality and online status. Common-interest matching can be set to any, 50, 60, 70 or 80 percent.
2. Search results show the profile picture, age, location, online state, match percentage and shared interests when available.
3. A request can be sent, accepted, declined or withdrawn. Only accepted friendships appear in friend lists and unlock friend-only content.
4. Protection rules can hide profiles or prevent connections even when a matching username exists.
5. Removing a friend requires confirmation and ends a confirmed relationship between the same users. It does not silently delete either account or the other user’s content.

Muting changes your automatic content view; blocking removes the other user’s access to you.

1. Muting keeps the friendship but removes that user’s posts and activities from your automatic Home views. You can later unmute the friend.
2. Blocking is asymmetric: the blocked user can no longer find or open your profile or interact with you, while you can still open the blocked profile and report misconduct.
3. Your visits to a user you have blocked are not shown in that user’s visitor list. Content from blocked users is not inserted into your normal feed.
4. Blocking hides an existing friendship and ends a confirmed relationship. Unblocking restores the hidden friendship when it existed before the block, but it does not restore the ended relationship.
5. The Dashboard lists blocked users so you can view, report or unblock them. A block is not a substitute for a report when rules were broken.

Important: Use Report as well as Block when another member has posted threats, harassment or other prohibited content.

A label becomes active only after the selected friend confirms it.

1. The Relationships tab lists confirmed friends. Opening the action modal lets you choose exactly one label such as father, mother, brother, sister, cousin, uncle, aunt, in a relationship, engaged or married.
2. The other user receives a relationship request modal during login or while online and can accept or decline it. A pending request can be withdrawn.
3. After confirmation the relationship is shown from both users’ perspectives. Family wording is adapted where the stored gender makes an opposite label necessary.
4. Family and relationship labels can appear below a friend’s name in the public friend list. A confirmed romantic status can also replace the ordinary status text in the separate public status panel.
5. The public status panel can be hidden in Edit profile. Ending a relationship removes the confirmed link for both users but keeps the friendship itself.

The guestbook allows controlled public messages directly on a user profile.

1. The profile owner can enable or disable the guestbook and may restrict new entries to confirmed friends. A user cannot write a top-level entry in their own guestbook.
2. A top-level entry may contain up to 800 characters. The newest 30 entries are shown with the newest first.
3. Replies may contain up to 600 characters and are limited to the profile owner and the author of the original entry. Replies are displayed oldest first below that entry.
4. Visible entries and replies can receive hearts, except that authors cannot like their own text. Relevant actions create personal notifications.
5. The author or the profile owner may delete an entry as allowed by the server rules. Entries can also be reported through the structured moderation form.

Messages are one-to-one text conversations between confirmed friends.

1. The Messages button is between Edit profile and Logout. A red badge at its upper-right corner shows the number of unread messages and updates automatically.
2. Start a conversation by selecting a confirmed friend. Each text message may contain up to 2,000 characters; image attachments are not part of the current version.
3. Opening a conversation marks received messages as read. The conversation view refreshes while it is open so new text can appear without navigating away.
4. If the friendship ends, the existing conversation remains readable but new messages are blocked. Blocking in either direction also prevents further messaging.
5. Muting a conversation suppresses its normal attention state without deleting it. Reporting the user opens the existing report workflow.
6. Deleting a conversation removes it only from your own inbox. The other participant keeps their copy. A later new message makes the conversation visible again, but the history you deleted remains hidden for you.

Important: Private means restricted to the participants in the interface; it does not make unsafe information risk-free to share.

Groups are the main place for self-organised topics and communities.

1. The Groups page searches names and topics and lists available public groups plus private groups that may be joined by request. A user may own up to 10 groups.
2. A new group needs a name of 3–80 characters and a description of 10–2,000 characters. It can be public or private and may have an optional JPEG, PNG or WebP cover image up to 10 MB, processed as a 2:1 WebP image.
3. Joining a public group is immediate. A private group creates a membership request that an authorised group role can accept or decline. A pending request can be withdrawn.
4. Confirmed friends can be invited. The invited user chooses whether to accept or decline the invitation.
5. Public group content is visible according to platform protection rules. Private group posts and the member list require confirmed membership.

Owner, administrator and moderator permissions are deliberately different.

1. The owner has complete control, may edit settings, assign roles, manage members and delete the group. The owner cannot simply leave; ownership ends only when the group is deleted in the current version.
2. Administrators can manage group settings and members. Moderators handle membership requests, invitations and content moderation. Only the owner assigns or changes these roles.
3. Group settings include name, description, rules up to 5,000 characters, visibility and the cover image. Changing public/private visibility changes who can see posts and members.
4. Authorised roles can remove members, ban them from the group and later unban them. A group ban is separate from a platform-wide user block.
5. A group feed post may contain up to 3,000 characters and a comment up to 1,000. Members can like and comment; authorised moderators can remove content and pin or unpin important posts.
6. Group posts can be reported. Membership requests, invitations, decisions, likes and comments can create personal notifications.

Reports create traceable cases instead of sending an unstructured complaint.

1. Users, feed posts, gallery or guestbook content and group posts expose report actions where supported. Select the closest category and describe the concrete problem clearly.
2. A successful report returns a case number. Duplicate or incomplete reports may be rejected so that the case system is not flooded with identical entries.
3. Blocking prevents contact but does not itself create a moderation case. Use both tools when you need immediate distance and formal review.
4. Moderation roles work with structured cases, sanctions and conflict checks. Sensitive permissions are enforced on the server, not granted by merely showing a button.
5. False reports, harassment through reporting or attempts to bypass protection rules can themselves violate the platform rules.

Processed media, server checks and session controls reduce avoidable exposure.

1. User media is delivered through the controlled media endpoint rather than relying only on predictable public file paths. Visibility rules are checked before protected content is returned.
2. Profile, gallery, feed and group images are processed into the required size and format. Originals are not kept as the normal published copy, and processing removes embedded metadata in the generated output.
3. Anything visible on a screen can still be copied or photographed. Watermarks and restricted resolution discourage reuse but cannot provide absolute screenshot protection.
4. Forms that change data use CSRF protection. Password resets invalidate active sessions, and inactive or sanctioned accounts are checked again while protected pages are used.
5. Do not publish addresses, identity documents, passwords, confirmation codes or other information that would be dangerous if copied by another member.

Most missing content is explained by visibility, membership, blocking or a pending action.

1. A friend-only gallery image is visible only after the friendship is accepted. A private group stays limited until the membership request or invitation is accepted.
2. Muted users disappear from automatic Home content but remain friends. Blocked users lose access to the blocker’s profile and interactions.
3. A relationship label is not displayed until the other user confirms it. The separate public relationship panel can also be hidden in profile settings.
4. A deleted conversation disappears only from the deleting user’s inbox. A later message can restore the conversation entry without restoring the locally hidden old history.
5. If a confirmation email is delayed, check spam and wait before requesting another code. If a page still shows old styling after an update, reload it without the browser cache.
6. When an action remains impossible despite the expected permissions, record the page, action and exact message rather than repeatedly clicking; this makes a real bug easier to reproduce.