Lobsters Publisher
Prepare Lobsters submissions that fit the computing-focused community. A
request to submit or a queue item marked 排队 authorizes the final submission;
do not ask again at the last button. Stop only when the task is limited to a
draft or preview.
Inputs
- Source URL, GitHub repo, paper, demo, blog post, or topic.
- Optional tags, title, text, or follow-up plan.
If the source URL is missing, inspect recent docs/blog/posts/, relevant
GitHub repos, and canonical eunomia.dev URLs before asking the user.
Platform Entry Points
Use a browser surface with the logged-in session when UI work is required.
References
Load references/platform-preferences.md when choosing Lobsters fit, tags,
title, source URL, self-promotion safety, browser checks, promotion balance, or
follow-up. Do not load broad strategy drafts for routine submissions unless the
user asks for campaign or content-platform planning.
Browser-Only Platform Boundary
Do not use unofficial submission automation, internal endpoints, or vote-related
actions. All checks and submission prep must come from normal browser
interactions.
Draft Preparation
- Check whether the item is narrowly about computing.
- Prefer the original/canonical source and remove tracking parameters.
- Choose predefined tags that accurately match the story.
- Keep the title factual and unpromotional.
- Disclose affiliation in comments when relevant.
Draft Archive
Before opening the Lobsters submit page or comment box, write or update the
Lobsters draft under draft/media/YYYY-MM-DD/<source-slug>/lobsters.md using
the local date. Include title, URL, tags, duplicate-check state, affiliation
note, and any full paste-ready comment options.
Browser QA
- title, URL, and tags are correct
- duplicate/recent same-topic searches are clean
- the account is allowed to submit the domain and tags
- tracking parameters are absent
- the final action matches the task: submitted when authorized, untouched for a draft-only task
Follow-Up
After confirmed submission, capture the story URL. Monitor comments and private
messages only when the user asks or follow-up was part of the task. Draft
substantive replies and move durable implementation work to GitHub.
Ledger Update
After confirmed submission, update .github/publisher/media/published.md with
source path or URL, Lobsters URL, date, tags, title, and follow-up notes.
1---2name: lobsters-publisher3description: Prepare or publish Lobsters submissions and follow-up drafts for eunomia.dev content, GitHub projects, papers, demos, and computing-focused technical posts. Use when asked to submit, adapt, publish, QA, or record Lobsters posts. Covers tag selection, computing-topic fit, self-promotion safety, browser duplicate checks, publication authorization, comment/private-message follow-up, and media ledger updates.4---56# Lobsters Publisher78Prepare Lobsters submissions that fit the computing-focused community. A9request to submit or a queue item marked `排队` authorizes the final submission;10do not ask again at the last button. Stop only when the task is limited to a11draft or preview.1213## Inputs1415- Source URL, GitHub repo, paper, demo, blog post, or topic.16- Optional tags, title, text, or follow-up plan.1718If the source URL is missing, inspect recent `docs/blog/posts/`, relevant19GitHub repos, and canonical eunomia.dev URLs before asking the user.2021## Platform Entry Points2223- New story: <https://lobste.rs/stories/new>24- About/guidelines: <https://lobste.rs/about>25- Recent: <https://lobste.rs/recent>26- Search: <https://lobste.rs/search>2728Use a browser surface with the logged-in session when UI work is required.2930## References3132Load `references/platform-preferences.md` when choosing Lobsters fit, tags,33title, source URL, self-promotion safety, browser checks, promotion balance, or34follow-up. Do not load broad strategy drafts for routine submissions unless the35user asks for campaign or content-platform planning.3637## Browser-Only Platform Boundary3839Do not use unofficial submission automation, internal endpoints, or vote-related40actions. All checks and submission prep must come from normal browser41interactions.4243## Draft Preparation44451. Check whether the item is narrowly about computing.462. Prefer the original/canonical source and remove tracking parameters.473. Choose predefined tags that accurately match the story.484. Keep the title factual and unpromotional.495. Disclose affiliation in comments when relevant.5051## Draft Archive5253Before opening the Lobsters submit page or comment box, write or update the54Lobsters draft under `draft/media/YYYY-MM-DD/<source-slug>/lobsters.md` using55the local date. Include title, URL, tags, duplicate-check state, affiliation56note, and any full paste-ready comment options.5758## Browser QA596061- title, URL, and tags are correct62- duplicate/recent same-topic searches are clean63- the account is allowed to submit the domain and tags64- tracking parameters are absent65- the final action matches the task: submitted when authorized, untouched for a draft-only task6667## Follow-Up6869After confirmed submission, capture the story URL. Monitor comments and private70messages only when the user asks or follow-up was part of the task. Draft71substantive replies and move durable implementation work to GitHub.7273## Ledger Update7475After confirmed submission, update `.github/publisher/media/published.md` with76source path or URL, Lobsters URL, date, tags, title, and follow-up notes.
eunomia-bpf