Skip to content

lofter-platform.md

Latest commit

 

History

History
92 lines (65 loc) · 6.17 KB

lofter-platform.md

File metadata and controls

92 lines (65 loc) · 6.17 KB

LOFTER Platform Notes

Use this file when you need platform-fit facts rather than literary guidance. Platform rules and monetization conditions can change; tell the user to verify current in-app terms before relying on revenue or eligibility details.

Sources checked on 2026-05-02:

  • LOFTER community norms: https://www.lofter.com/front/homesite/agreement/community-norms
  • NetEase LOFTER service agreement: https://www.lofter.com/agreement
  • LOFTER beginner course and community norms page: https://www.lofter.com/beginnercourse
  • LOFTER gift service terms: https://www.lofter.com/front/homesite/agreement/gift-service
  • LOFTER recommended tags page: https://www.lofter.com/recommendTag
  • LOFTER algorithm service explanation: https://www.lofter.com/cms/150517/algorithm.html
  • LOFTER intellectual property page: https://www.lofter.com/CreativeCommons
  • LOFTER infringement complaint guide: https://www.lofter.com/antitorts

What Is Officially Supported

  • LOFTER presents itself as a community for publishing, sharing, responding to, and discovering interest-based content.
  • The web editor supports text, images, music, video, and long articles; the app supports common mobile publishing flows.
  • The beginner page encourages interaction through likes, comments, recommendations/reposts, sharing, private messages, and questions.
  • The community norms prohibit illegal, harmful, privacy-infringing, repeated/spammy, harassing, misleading, and order-disrupting information, including behavior that disrupts tags, comments, and private messages.
  • The community norms specifically warn against using AI or other technology to generate or spread pornographic, vulgar, or infringing content, and against AI/edited/old-news manipulation that creates false information.
  • The service agreement says users must not use deep learning, virtual reality, generative AI, or similar technologies to make, upload, publish, or spread legally prohibited false news information, or pass generated/synthetic content off as real or natural content.
  • The gift service terms describe gifts as encouragement for creators and allow creators to set return gifts, while requiring compliance with LOFTER service rules.
  • The algorithm explanation says recommendation can consider interaction and tag-interest similarity. Search can use creator-added tags and model-extracted tags, and creator-added tags are generally in the 1-10 range.
  • Content and tags are subject to safety review before public display. Do not position any advice as a way to force exposure.

Practical Implications For This Skill

1. Optimize For Tag Discovery

LOFTER readers often discover works through tags before they discover authors. Treat the tag set as a distribution surface, not as an afterthought.

Recommended grouping:

  • Main CP or relationship tag, if appropriate for the fandom
  • Character tags only when the fandom's etiquette allows them
  • IP/world tag
  • Form tag, such as forum thread, chat log, viewing, daily, serial, or short story
  • Mood/content tag, such as sweet, HE, comedy, angst, modern AU, canon-adjacent

Important etiquette:

  • Ask the user for known tag customs if the fandom is unfamiliar.
  • Some communities separate CP direction strictly; do not guess AB/BA if the user has not specified it.
  • Some communities dislike CP posts entering single-character tags. Mention this as a check, not an absolute rule.
  • Do not overload unrelated hot tags. Misleading tags can annoy readers and may be treated as platform disruption.
  • Prefer a compact set of accurate tags. The official algorithm note mentions creator-added tags generally in the 1-10 range.

2. Keep Packaging Compact

  • Keep titles readable and focused on mood, premise, or hook.
  • Avoid titles that contain the entire plot, long dialogue chunks, or misleading ships.
  • Summaries should tell readers what kind of emotional experience they are opening.
  • Add content notes when a post contains heavy themes, major canon divergence, death, violence, intense angst, spoilers, or other potentially sensitive material.
  • Do not turn the post intro into a synopsis wall.

3. Use Collections Deliberately

Use collections for series, same-CP clusters, same universe, or recurring format projects. Good collection names are short, searchable, and stable. For serials, keep a consistent summary and chapter numbering pattern.

4. Treat Timing And Interaction As Soft Guidance

Non-official creator experience suggests evenings and weekends may perform better, and that replies or long comments help build readership. Treat this as experience-based guidance, not a platform guarantee.

Interaction prompts should invite a real response:

  • "Which clue did you notice first?"
  • "Do you want the next chapter to go public reveal or private confrontation?"
  • "Which character should get the next POV?"

Avoid manipulative or spam-like engagement requests.

5. Do Not Hardcode Monetization Claims

The official gift service terms support gifts and creator return gifts, but exact eligibility, revenue, and in-app product names may change. When advising on monetization:

  • Recommend verifying current LOFTER app rules.
  • Do not imply guaranteed earnings.
  • Keep paid extras related to the work, clearly described, and compliant.
  • Do not lock essential safety/context warnings behind paid content.
  • Do not use gifts for crowdfunding, gambling/lottery-like activity, selling physical or virtual goods, or inducements unrelated to creator support.
  • Mention that official terms describe monthly withdrawal windows and minimum withdrawal thresholds, but tell the user to confirm the current amount and fee/tax treatment in-app before planning revenue.

6. Handle AI-Assisted Work Transparently

LOFTER's public rules and agreements require transparent handling of generated or synthetic content. For a publish pack:

  • Add an AI note when AI materially assisted writing, editing, images, or video.
  • Use platform-provided declaration controls when available.
  • Include tags such as #AI生成# or #AI辅助# when the platform or current community rule calls for them.
  • Do not hide AI assistance, perform AI "washing" of others' works, flood tag pages with low-quality AI posts, or train on community content without authorization.