Appearance
Feed & posts
The home feed at zeeker.com is a blend of posts from people you follow, communities you joined, and a discovery layer that surfaces what's getting reactions across Zeeker.
Feed tabs
| Tab | What it shows |
|---|---|
| Trending | Fresh posts weighted by activity, topic density, and your preferences. |
| Popular | Posts with the strongest engagement, weighted toward freshness and your preferences. |
| Recent | Freshest eligible posts, with your preferences influencing their order. |
The Following only preference applies to whichever tab is selected, and the feed continues loading that same sort as you scroll. In Trending, Popular, and Recent, a selected country excludes posts explicitly assigned to another country, and a selected city excludes news explicitly local to another city. Matching-city news, broader national and World coverage, and posts without an explicit geographic restriction remain eligible. All cities includes local news across the selected country. Selected topics also restrict eligibility: posts must meet the geographic rules and match at least one selected topic. Clearing all topics removes the subject restriction. See Explore preferences for location controls and examples. Public discovery results are cached by location and topic preferences; account-specific following, save, and reaction state is resolved for the signed-in user.
The first feed page is kept as a small account- and preference-scoped cache so returning to Home can paint immediately. Social then revalidates that page in the background. Additional pages use the opaque continuation returned by the server; each page keeps the server's order and does not download, merge, or re-sort the reader's earlier history. New posts, edits, deletions, replies, and reactions update the affected cached entities and query generations instead of clearing every unrelated screen.
Home-feed posts must contain something a reader can consume or an active discussion to join. Short text posts remain eligible, as do titles, images, polls, ratings, references, connected posts, playable third-party embeds, useful link previews, and thread roots with visible replies. A link preview containing only its URL, publisher hostname, or favicon after preview fetching fails is not enough on its own. The underlying thread still exists at its direct URL and in its originating Embed; it simply does not consume a Trending, Popular, Recent, or Following home-feed slot until it has meaningful preview data or visible replies.
A community may replace these visible sort tabs with an automatic, text-only All lane followed by up to four admin-selected post-tag filters. All is selected by default and displays every community post. Filter names are never shortened with an ellipsis; the strip scrolls horizontally when the full labels do not fit. Swiping moves between All and the tag filters just as it moves between sort tabs. Trending, Popular, and Recent remain available in Preferences and determine the order inside the active lane. The same lane and scrolling treatment are retained for pagination and full community Embeds; individual post pages do not show community tag-filter tabs.
Post types
Zeeker recognises several post types, all of which share the same reply/reaction/share/save engine.
| Type | When it's used |
|---|---|
text | Plain post or long-form post with a title. |
link | A URL share (rendered as a link card). |
image | One or more images (up to 4). |
video | A single video (≤ 60s, mp4/mov, up to 200MB). |
repost | A boosted copy of another post. |
quote | A repost with your own commentary. |
question | A question using the normal post page, replies, reactions, and community moderation. |
answer | A direct reply to a question, using the normal reply card, actions, moderation, and Answer badge. |
review | A review using the canonical rating/review fields and the normal post/reply engine. |
poll / trivia | A post with existing vote options and voting behavior. |
Long-form posts (≥ 260 chars, or ≥ 160 chars and ≥ 3 sentences) get a title field in the composer. Shorter posts are bare text.
Communities decide which available post types members may use. Embed Element presets may narrow that allowed set—for example, to question or review posts—but they do not define another post model or an Element-only card/header.
When someone sends a plain direct reply to a question, Social stores it as an answer. Replies beneath that answer remain ordinary nested Social replies. Product Q&A embeds select and present this same model; they do not infer an Embed-only answer type.
Current News cards
Current News uses the existing post and thread system rather than a separate post type:
- A concise event summary is a normal post marked Current News. It is the discussion hub for that event.
- Publisher articles, relevant videos, and supported third-party posts remain separate source cards that reference the hub. Open Related coverage to see them together; the first two appear initially and the rest can be expanded.
- A poll about the broader issue is a reply to the summary, so its votes and discussion stay in the same thread.
- Broader news-inspired discussion prompts are standalone question posts. They intentionally avoid relying on the names, numbers, or trivia of one exact story.
Current News hubs expire from discovery after 24 hours. The same country and city eligibility rules apply to news summaries and publisher news cards. Choosing a city keeps its local coverage alongside broader national and World stories; a national story remains eligible even when it mentions another city. These stories must also match at least one selected topic when topics are selected. The feed continues looking through older candidates when the newest batch has too few matches.
A summary's primary supporting media is ordered as a relevant YouTube video, an article image with recorded licensed-reuse or publisher-authorized hotlink rights, then a linked publisher-brand banner using the publisher name, domain, and favicon. Source cards keep their publisher attribution and outbound link.
Composing
The composer lives at the top of every feed view and in a floating + button on mobile.
- Text: rich plaintext with @mentions, #hashtags and auto-linked URLs.
- Attachments: Add image and Add link live once in the rich-text toolbar. Add link lets you choose Show URL to insert or link textbox content, or Link card to attach a rich preview without changing the textbox.
- Mentions trigger an inline username picker.
- Hashtags become tappable links to the tag's feed (
/tag/<tag>). - Community tags come from the community's configured catalog (for example Feedback, AMA, Z4Z, Spoiler Free, or Explicit). A community may allow one or multiple descriptive tags per post or reply; post-type indicators such as Poll remain separate.
- Link previews are unfurled server-side; you can dismiss the preview to post the URL as plain text.
- Image upload supports drag-and-drop, paste, and the file picker. Images are auto-rotated by EXIF, stripped of GPS metadata, and re-encoded to AVIF + WebP fallbacks.
- Video upload is transcoded asynchronously; the post publishes immediately with a "processing" placeholder.
- Community picker lets you post into a community you've joined. Posts not assigned to a community land in your general feed.
- Visibility:
public(default),followers-only, orcommunity-only(when posting into a community). - Drafts auto-save every 5 seconds while you compose.
- Schedule lets you queue a post for a future timestamp (up to 60 days out).
Connected sequences keep each slot's link card and images separate while you move between slot numbers. A continuation may contain only a link card or image—the composer still saves, uploads, and publishes that slot even when its textbox is empty. Clearing the last text or attachment from an existing slot removes that slot from the sequence. A sequence may contain up to 20 media attachments in total, with the normal per-post limit still applying. The same toolbar and sequence behavior is used in Social, Explore, and publisher Embeds.
Edit & delete
- Posts can be edited within 15 minutes of publishing — replies above 15 minutes show an "(edited)" badge if changed afterward via support tools.
- Edits preserve replies and reactions.
- Deleting a post leaves a
[deleted]tombstone if there are replies underneath; a freshly loaded list can omit a reply-free deleted post. - An already-visible post you delete changes to its Deleted tombstone or badge immediately, even when a fresh list would omit it; you do not need to refresh the page.
In Admin view, verified community staff see moderation actions in More options on both the community feed and individual thread pages. Pin/unpin and accept/reject/remove remain available for root posts, connected sequences, and replies.
Reporting a post
Open a post's More options menu and choose Report. Select one or more reasons and optionally add context for the moderation team.
Reporting is available without logging in or creating an account. Reports are anonymous to the post author; signed-in reports retain the reporter identity only for internal trust-and-safety review. Guest submissions are rate-limited to prevent automated abuse.
Repost vs quote
- Repost = pure boost; counts toward the original's metrics and shows in your followers' feeds with a
"<your-name> reposted"header. - Quote = a new post with your text + an embedded card linking the original. Quotes can be reposted/quoted/replied-to in their own right.
A user can repost a post once; reposting again undoes it.
Post metrics
Each post displays:
- Replies count (descendant total, not just direct children)
- Reactions count + the top 3 reaction types
- Reposts + quote count combined
- Saves (count visible to author only)
- Views (intentional post opens; visible to author only)
Authors can open More options → View insights on a post to see aggregate views, engagement, and top countries. A view is counted once per post per browser session when the post page or a genuinely visible published Embed has finished loading. Feed-card impressions, hidden/preloaded Embed frames, signed dashboard previews, and managed no-analytics readers are not counted. A published read-only Embed still exposes this private insights action to its signed-in author while keeping edit, delete, reply, reaction, and other participation controls disabled.
URL shape
| Page | URL |
|---|---|
| Single post | zeeker.com/p/<post-id> |
| User profile | zeeker.com/u/<username> |
| Tag feed | zeeker.com/tag/<tag> |
| Community | zeeker.com/c/<slug> |
| Search | zeeker.com/search?q=... |
Post URLs are stable forever; deletion shows a tombstone page, not a 404.