LLL Live Feed / 公開記事RSS配信

Is saving a draft enough to publish?

No. Save changes only the draft. Review and explicitly Enable feed to replace published settings. Disable stops the public endpoint; Clear draft leaves any enabled published configuration intact.

What is included?

One collection, one exact non-empty locale, latest20 published entries, title, URL, opaque GUID, valid past publication date, and optional plain summary. Blank/non-string titles use the public entry ID as a label and the private review reports this. Full body, revisions, SEO, author data and other locales are not emitted.

Are routable fields automatically safe to expose?

No. You must verify anonymous access and selected fields in your actual theme. Custom member-only policies cannot be detected automatically. Null locales are excluded, without fallback to the site locale.

Do stopped or deleted articles disappear immediately?

A commit completed before GET is excluded from that next response. There is a final configuration/list recheck, not an atomic snapshot. RSS reader polling and previously downloaded copies are outside plugin control.

Does this track readers or need external credentials?

No visitor tracking, mail, network allowlist, API key, publication write or cron. It stores one bounded plugin KV configuration key. The SDK content:read grant is broader than the emitted projection.

Capabilities: content:read and schema:read. The SDK grants are broader than this emitted projection. Code lists only one selected collection with published status and exact locale, never loads revisions and never publishes/updates CMS content. No external hosts, cron, email, AI or visitor tracking.

Private POST uses host plugins:manage and CSRF. Fixed plugin KV key live-feed-config-v1 stores at most16KiB of namespace/draft/published/enable settings, never article copies, actor information or credentials. One-key CAS binds saves and immutable confirmations. Public GET/HEAD has no-store, raw RSS2 MIME and host security headers. Invalid/off/race/read/budget states fail closed without old-feed fallback.

Selected strings are XML1.0 validated. RSS item descriptions use HTML then XML escaping; titles/channel text use XML escaping. Reader implementations differ: normalized text must not be treated as HTML-safe by a consumer. No DOCTYPE/ENTITY/CDATA or arbitrary HTML is generated. Contact contact@lx3.cafe for support and vulnerability reports.

0.1.0

Initial single-feed release: explicit public-field acknowledgement, private draft/review/CAS enable, exact locale/live projection, stable opaque GUIDs, bounded RSS2 raw GET/HEAD and distinct disable/clear operations.

Requires EmDash1.4 and a supported sandbox runner. Tested on Node22, Astro7.3.2 and sandbox-workerd0.9.6. Cloudflare deployment has not been accepted in this release.

1. Install and enable LLL Live Feed. Open its Live Feed admin page with permission to manage plugins.
2. Edit the saved draft, choose a routable collection, continue, then open a fresh form. Select schema-backed plain string/text fields, one exact non-empty locale, title and description. Null-locale legacy content is excluded.
3. Verify that the selected articles and fields are anonymously public in your real theme. Do not select member-only or custom-authenticated content. Explicitly acknowledge this before saving.
4. Save draft only. Review the exact saved draft, current published configuration, RSS URL and latest public projection. Enable feed to publish that reviewed snapshot.
5. Copy the exact URL shown on the page into an RSS reader. No theme code or cron is required for the feed endpoint; article links still require your real theme routes.

Clear draft and Disable public feed are separate. Reload discards unsaved form values. A competing save requires a reload and fresh review. Keep namespace/KV state when moving installations if GUID continuity matters. Reinstalling without state can reset GUID identity.