coilysiren/website

Watch

Evaluate second-wave syndication targets: Hashnode and Bluesky #104

New issue

Closed

opened 2026-08-10 20:09:26 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-08-10 20:09:26 +00:00

Collaborator

Context

dev.to is the first syndication target because its API does create and update for free. Two follow-on targets are worth evaluating once that pipeline works, and both are deliberately deferred until then.

Candidates

Hashnode. GraphQL at https://gql.hashnode.com, with publishPost and updatePost mutations and an originalArticleURL field serving as the canonical URL. Full-fidelity article sync, same shape as the dev.to work. Caveat: multiple 2026 sources report that write access sits behind Hashnode Pro at roughly $5/month. Verify current pricing at signup before committing. This is the only paid item in the syndication plan.
Bluesky. Kai already holds the handle and the coilysiren/bluesky-apps repository exists. This is link announcement rather than article sync, and posts are effectively create-only, so it behaves as fire-and-forget notification driven off the RSS feed rather than a synced copy.

Ruled out, recorded so they are not re-evaluated

Medium - stopped issuing integration tokens in 2025 and permits no new integrations. RSS import is a one-shot copy with no update path.
LinkedIn - no article API. Share posting requires an approved app and does not cover long-form.
Substack - no public write API.
Lobste.rs and Hacker News - submission is social by design and should stay manual.

Acceptance criteria

Confirm current Hashnode API pricing and write-access requirements from Hashnode's own documentation, not third-party guides.
Decide whether the reach justifies the subscription. Record the decision either way.
If Bluesky proceeds, it consumes the RSS feed rather than reimplementing the promotion-flag logic.
Any target that proceeds reuses the canonical-URL and idempotency conventions from the dev.to work.

Dependencies

Blocked on the dev.to syndication issue and the RSS feed issue. Do not start until one target is proven end to end.

## Context dev.to is the first syndication target because its API does create and update for free. Two follow-on targets are worth evaluating once that pipeline works, and both are deliberately deferred until then. ## Candidates * **Hashnode.** GraphQL at `https://gql.hashnode.com`, with `publishPost` and `updatePost` mutations and an `originalArticleURL` field serving as the canonical URL. Full-fidelity article sync, same shape as the dev.to work. Caveat: multiple 2026 sources report that write access sits behind Hashnode Pro at roughly $5/month. Verify current pricing at signup before committing. This is the only paid item in the syndication plan. * **Bluesky.** Kai already holds the handle and the `coilysiren/bluesky-apps` repository exists. This is link announcement rather than article sync, and posts are effectively create-only, so it behaves as fire-and-forget notification driven off the RSS feed rather than a synced copy. ## Ruled out, recorded so they are not re-evaluated * **Medium** - stopped issuing integration tokens in 2025 and permits no new integrations. RSS import is a one-shot copy with no update path. * **LinkedIn** - no article API. Share posting requires an approved app and does not cover long-form. * **Substack** - no public write API. * **Lobste.rs and Hacker News** - submission is social by design and should stay manual. ## Acceptance criteria * Confirm current Hashnode API pricing and write-access requirements from Hashnode's own documentation, not third-party guides. * Decide whether the reach justifies the subscription. Record the decision either way. * If Bluesky proceeds, it consumes the RSS feed rather than reimplementing the promotion-flag logic. * Any target that proceeds reuses the canonical-URL and idempotency conventions from the dev.to work. ## Dependencies Blocked on the dev.to syndication issue and the RSS feed issue. Do not start until one target is proven end to end.

coilyco-ops added the

priority

autonomy

async-consult

labels

2026-08-10 20:09:55 +00:00

coilyco-ops referenced this issue from a commit

2026-08-25 07:24:16 +00:00

feat: ship an Atom feed scoped to the promoted posts

coilyco-ops added the

role/engineer

label

2026-08-25 08:12:22 +00:00

coilyco-ops commented

2026-08-27 03:19:14 +00:00

Author

Collaborator

Closed in the 2026-08-26 backlog burn-down (coilyco-bridge/agentic-os-kai#901).

Closing during a P3 burn-down. This is a deferred evaluation behind a pipeline that has not shipped; the ruled-out research stays readable here if syndication is revisited.

This was priority/P3, the default tier that unsure and unscored issues land in, so it had never been positively judged worth keeping. The 2026-08-26 burn-down ranked the whole P3 pool and cut the bottom. Closed here means not on the list, not wrong or worthless.

If this is live work, reopen it. The whole set is recoverable with state:closed label:burndown-2026-08.

Closed in the 2026-08-26 backlog burn-down (coilyco-bridge/agentic-os-kai#901). Closing during a P3 burn-down. This is a deferred evaluation behind a pipeline that has not shipped; the ruled-out research stays readable here if syndication is revisited. This was `priority/P3`, the default tier that unsure and unscored issues land in, so it had never been positively judged worth keeping. The 2026-08-26 burn-down ranked the whole P3 pool and cut the bottom. Closed here means not on the list, not wrong or worthless. If this is live work, reopen it. The whole set is recoverable with `state:closed label:burndown-2026-08`.

coilyco-ops

2026-08-27 03:19:16 +00:00

closed this issue
added the
burndown-2026-08
label

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilysiren/website#104

No description provided.

Rows
Columns