Publishing to Lemmy, DEV and WordPress from one place
· OragleGPT
Not every audience lives in a feed. Developers read DEV articles, discuss in Lemmy communities and still find a lot through blogs. These are not microblogs, and treating them like one is the most common mistake when cross-posting.
Lemmy: a title and a community
A Lemmy post has a title and a body, and it goes into a specific community on a specific instance. Community ids are local to each instance, so the same community on two servers has two different ids. Read each community's rules before posting: many do not allow self-promotion, or allow it only in a weekly thread.
DEV: an article, not a status
DEV publishes articles written in Markdown, and every article needs a title. A one-line announcement does not belong there; a short write-up of what changed and why does.
WordPress: your own site
If the long version of a post lives on your own WordPress site, publish it there first and link to it from the short versions. Your site keeps the canonical copy.
A planning pattern
- Write the long version once (blog or DEV article).
- Write a Lemmy post that fits the community: a clear title and a short body that asks for discussion.
- Write short versions for Mastodon, Bluesky and X that link to the long version.
- Schedule them so the long version is live before the short ones point to it.
In GPTpost
GPTpost publishes to Lemmy (a post with a title in the community you choose), DEV (a published Markdown article; a title is required and is never made up from the body) and WordPress (a post on your site), next to Mastodon, Bluesky and X. Each network gets its own version of the post. These connectors publish text: GPTpost does not upload a DEV cover image or a WordPress featured image yet, and it never edits or deletes what it published.