How to use a Righthand with Mastodon

Quick answer

Use Righthand to prepare a Mastodon publishing review that retains instance identity, visibility, and conversation context. Federated accounts need more than a bare display name.

Start with a reviewable deliverable, keeping Mastodon as the accepted home for its records. This guide uses an explicitly approved snapshot or browser read; it does not assume that every provider API action is exposed by your Righthand connection.

Evidence and access

Mastodon documents status methods and OAuth scopes. See the official Mastodon reference. Provider capabilities and Righthand's available tools are separate checks.

Request the approved account's instance, post drafts, visibility instructions, and relevant community rules; keep cross-instance assumptions explicit. Verify the required tools and owner-approved scope through Righthand integrations; use the supplied packet when a native read is unavailable.

Define the objects and authority

Include these fields in the working input: full account address, instance, status URL, content, visibility, content warning, media references. These are the requested review columns, not a promise that every provider endpoint returns them under those exact names.

A public status and a followers-only message have different audiences. The owner approves visibility and any cross-posting.

Illustrative first-run brief

Use the owner-provided Mastodon snapshot or approved read-only view. Review ten supplied status drafts for source claims, links, intended visibility, and content-warning needs. Return an approval packet; do not publish. Run once for the agreed sample, using America/Los_Angeles for the review deadline and preserving source timestamps separately. Return the draft in this conversation by Friday at 3 PM Pacific for the account owner to review. Include source references and missing fields. Do not write records, spend money, change permissions, or send external messages. Stop and report an unavailable source rather than substituting another account.

Expected result and verification

A draft intended for followers remains separate from the public announcement. The packet highlights the audience choice rather than silently defaulting it.

Compare the full account address and visibility with the owner's intended audience. Record the source cutoff, applied filters, and items excluded from the sample. The reviewer should be able to follow each consequential finding back to an original object. A well-written summary is not evidence that a proposed action happened. If a later write is authorized, verify its specific result separately before changing the task's status.

Illustrative input and draft output

These synthetic entries show the requested review, not live account results or a provider field schema.

Common failure and recovery

Instance policies and scopes can differ. Confirm the relevant server and permitted method instead of assuming another instance's settings apply.

If a supplied handle omits its instance, hold identity-dependent wording and ask for the full account reference before continuing.

FAQ

What should the reviewer verify first?

Verify the full account identity, intended visibility, and source-supported claims. Public, followers-only, and other visibility intentions should not be inferred from the draft text.

How should a repeat run be scoped?

Keep instance, account reference, draft version, visibility instruction, and review date. Recheck community rules and conversation context before a separate authorized post.

For connection and permission details, use Righthand Docs. Review Pricing alongside any separate provider charges before expanding the workflow.