Author: gptadmin

  • The one tool you would keep: what social media teams really rely on

    Ask a social media manager to list their tools and you get a long answer: a scheduler, a design app, a link shortener, an analytics dashboard, a writing assistant, a shared drive. Ask which single one they would keep and the answer is often surprising.

    Common answers, and what they reveal

    • A plain spreadsheet of ideas. It shows that the hardest part is rarely publishing. It is having something worth saying on a Tuesday afternoon.
    • A calendar view. Seeing the week at a glance prevents the two classic mistakes: three similar posts in a row, and a silent week nobody noticed.
    • A second pair of eyes. A colleague or a client who reads every post before it goes out. Many teams rely on this more than on any app.
    • A notebook. Drafting by hand forces short sentences. Surprisingly common among people who write well.

    What to do with your own answer

    Whatever you would keep is the core of your process. Protect it. If the answer is the second pair of eyes, make review a formal step with deadlines instead of a favour. If it is the ideas spreadsheet, give it a fixed weekly slot to grow. If it is the calendar, make sure everyone who touches posts can see it.

    Then look at the rest of your stack and ask which tools support that core, and which are just there because they were there last year. Cutting one subscription you never open is a perfectly good Friday task.

    Tell us yours

    We build a scheduler, so we have a bias. That is exactly why we like hearing what people would keep instead. Reply on any of our social accounts or write to hello@oraglegpt.org. More about what we build at oraglegpt.org.

  • How to write a release announcement developers will read

    Release notes are written by people who know every detail of a change, and read by people who have a few seconds to decide whether it concerns them. Most announcements fail because they are written for the first group. Here is a structure that works for the second.

    1. What changed, in one sentence

    Describe the user-visible change, not the implementation. “Exports now include archived projects” is better than “Refactored export pipeline (PROJ-1432)”.

    2. Who it affects

    Say who should care and who can ignore it. “If you use the CSV export, check your scripts” saves everyone else a click and makes the right readers pay attention.

    3. One concrete example

    A before and after, a single command, or one screenshot with alt text. Examples make a change real much faster than a list of adjectives.

    4. A link to the full notes

    The social post is the headline. The details, migration steps and edge cases belong in the full release notes, so link them clearly.

    Adapting it per network

    • Bluesky and X: sentence one and the link. That is all that fits comfortably.
    • Mastodon: all four parts in under 500 characters, with one or two CamelCase hashtags such as #DevRel.
    • DEV, Lemmy or your blog: a real title and the full story, including why the change was made.

    What to leave out

    Internal codenames, ticket numbers, sprint names and long thank-you lists before the news. Credit contributors, but after readers know what happened.

    If you post releases often, it helps to keep this structure as a template and to feed your changelog into drafts automatically. We wrote about doing that for developer relations teams here.

  • Scheduling Bluesky posts with images and alt text

    Bluesky posts with images tend to get more attention in a busy feed, and they are also where accessibility most often slips. When a post is published by hand in a hurry, the image description is the first thing that gets skipped. Scheduling the post ahead fixes that, as long as the scheduler treats alt text as part of the post.

    What GPTpost supports

    • Up to four images per Bluesky post.
    • A separate alt text for each image, written in the composer.
    • The 300-character Bluesky limit checked when you schedule, so the text and images are ready together.

    Images and descriptions are visible to everyone in the approval flow, so a reviewer can catch a missing or vague description before the post is approved.

    Writing alt text that helps

    1. Say what matters for this post. A screenshot of a settings page needs the setting and its value, not “a screenshot”.
    2. Include any text shown in the image. If the image is a quote card, the quote belongs in the alt text.
    3. Keep it short. One or two sentences usually do the job. Skip “image of”.

    What about other networks?

    In GPTpost today, Bluesky takes up to four images and Telegram takes one photo or video. Mastodon, X, Discord and Slack are text only. If you publish the same idea everywhere, write the image version for Bluesky and a text version for the others in the same composer.

    Try it

    The trial is 14 days, includes 15 connected accounts and needs no card. Connect Bluesky with an app password, schedule an image post with alt text and check how it looks when it lands. More on Bluesky scheduling here.

  • Post more, go viral, do a TikTok: why these are not a content strategy

    Every team has sat in a meeting where the content strategy turned out to be a wish list. “We should post more.” “We need something that goes viral.” “Can we do a TikTok?” None of these are bad ideas. They are just not a strategy, and treating them as one is the fastest route to an account that posts a lot and says nothing.

    Why the wish list fails

    Post more assumes volume is the problem. Usually the problem is that nobody knows what the posts are for. Doubling frequency doubles the effort and rarely doubles anything else.

    Go viral is an outcome you cannot schedule. Posts that spread widely tend to be specific, useful or genuinely funny, and they come from accounts that post consistently enough to have a few lucky hits.

    Do a TikTok is a channel decision made before deciding what to say. A new network is a commitment of time every week, not a one-off.

    The three lines that are a strategy

    1. Who you are talking to. Not “everyone”. A role, a situation, a problem.
    2. What you help them with. Teach, save time, entertain, keep them informed. Pick one or two.
    3. A rhythm you can keep. Two good posts a week for a year beats ten a week for a month.

    From those three lines you can derive content pillars, formats and which networks are worth the effort. Without them, every planning meeting restarts from zero.

    A quick test

    Take your last ten posts. For each one, ask: who was this for, and what did it help them with? If you cannot answer for more than half, the issue is not frequency or virality. It is the missing sticky note.

    We plan our own calendar this way, with a handful of recurring themes and a fixed rhythm. More on how GPTpost helps with the scheduling part at oraglegpt.org.

  • GPTpost paid plans are live: Solo, Team and Agency explained

    On 20 October 2026 GPTpost started offering paid plans. This post explains what each plan includes, why we price per workspace and what happens to the free trial.

    The three plans

    • Solo, 12 USD per month: 1 seat, 5 connected social accounts, 300 posts per month.
    • Team, 39 USD per month: 5 seats, 15 connected accounts, 1,500 posts per month.
    • Agency, 99 USD per month: 25 seats, 60 connected accounts, 6,000 posts per month.

    Billing is monthly, in US dollars, through Stripe Checkout. GPTpost never sees your card details.

    Why per workspace

    Most of the people who touch a social post are not the person who writes it. There is a reviewer, sometimes a manager, often a client. Charging for each of them makes teams hesitate before inviting the people who should be checking the work. Each plan includes a set number of seats, and client reviewers who approve through a review link need no seat at all.

    The trial did not change

    You can still try GPTpost for 14 days without a card. The trial includes 5 seats, 15 accounts and 500 posts. It never converts to a paid plan on its own. When it ends, the workspace becomes read-only: posts, schedules, comments and files remain readable and exportable, and nothing is deleted. You choose a plan when you are ready, in Settings, Billing.

    What you get on every plan

    Every plan includes the same core: per-network versions of each post, a shared calendar, posting slots, multi-stage approvals, client review links, recurring posts, CSV bulk scheduling, RSS to drafts and the REST API and MCP server for AI agents. The plans differ in seats, accounts and monthly post volume, not in which features you are allowed to use.

    Which plan to pick

    If you post for one brand on your own, Solo is enough. If a few colleagues draft and approve together, Team gives you room. If you run social for several clients, Agency covers 60 accounts and 25 seats in one workspace.

    See the full comparison of limits on the pricing page.

  • GPTpost is live: plan, approve and schedule social posts

    GPTpost is live.

    Connect the social accounts your business already owns, write a post once, adjust it for each network, and schedule it on a shared calendar with approval before anything goes out.

    Developers and AI agents can draft and schedule through a REST API and a remote MCP server, with scoped keys and the same approval rules.

    Plans are per workspace: Solo USD 12, Team USD 39 and Agency USD 99 per month. The 14-day free trial needs no card and never turns into a paid plan on its own.

    Start a free trial: https://app.oraglegpt.org
    Pricing: https://oraglegpt.org/pricing/
    API and MCP docs: https://app.oraglegpt.org/developers

    This post was published from GPTpost.

  • GPTpost connector test

    GPTpost WordPress connector test post — self-hosted blog live.

  • Hello world!

    Welcome to WordPress. This is your first post. Edit or delete it, then start writing!