TTYverse provides comprehensive posting features, supporting text posts, media uploads, polls, replies, and all fediverse visibility levels with accessibility-first design principles.

Basic Text Posts

Simple Posts

Create public posts with the /post command:

/post Hello fediverse! Just discovered TTYverse and loving the accessibility focus.

Post result:

Creates a public post visible to everyone
Appears in local and federated timelines
Uses your default visibility setting
Includes post confirmation

Multi-line Posts

For longer content, TTYverse handles multi-line text naturally:

/post This is a longer post that spans multiple concepts. 

I can discuss accessibility, command-line interfaces, and the importance of inclusive design in fediverse clients.

#accessibility #commandline #fediverse

Tips for multi-line posts:

Natural line breaks are preserved
Hashtags work anywhere in the post
Links are automatically detected
Character limits depend on your server (usually 500-1000 characters)

Visibility Levels

Understanding Visibility

TTYverse supports all fediverse visibility levels:

Public [Public]:

Visible to everyone
Appears in local and federated timelines
Discoverable through search
Default for most posts

Unlisted [Unlisted]:

Public but not in timelines
Viewable by direct link
Appears on your profile
Good for replies and casual posts

Followers-only [Followers]:

Only visible to your followers
Private but not direct
Good for personal updates
Won't appear in public timelines

Direct [Direct]:

Only visible to mentioned users
Functions like direct messages
Private communication
Requires @mentions to specific users

Setting Visibility

Current visibility system:

Posts use your account's default visibility
Check your server settings for default visibility
Individual post visibility may be adjusted by server

Future visibility control:

TTYverse may add per-post visibility controls
Server-dependent feature implementation
Check your instance's post visibility options

Replying to Posts

Basic Replies

Reply to any post using its menu code:

/reply a3 Great point about accessibility! TTYverse really does make the fediverse more inclusive.

Reply features:

Maintains conversation threading
Notifies the original poster
Inherits appropriate visibility
Preserves conversation context

Reply All

Reply to all participants in a conversation:

/replyall a3 Thanks everyone for this discussion! The accessibility insights are really valuable.

Reply all behavior:

Mentions all users in the original post
Creates inclusive conversation
Useful for group discussions
Respects privacy settings

Reply with Media

Combine replies with media attachments:

/reply a3 Here's a screenshot showing the accessibility feature you mentioned
/media /path/to/screenshot.png

Media Posts

Image Posts

Upload images with required alt-text:

/media /path/to/photo.jpg Beautiful sunset from today's hike

Image posting process:

TTYverse detects image file type
Prompts for alt-text description (required)
Prompts for optional post message
Uploads media and creates post

Alt-text requirements:

Required for all images (enforced)
Upload cancelled without alt-text
Promotes accessibility
Helps screen reader users

Example interaction:

TTYverse> /media ~/photos/garden.jpg
-- Detected file type: image/jpeg
-- Images require alt-text for accessibility
Enter alt text for garden.jpg: Tomatoes ripening on vines in a backyard garden
Enter post message (optional): Finally seeing some red tomatoes! #gardening
-- Uploading media file...
-- Media uploaded successfully
-- Post created successfully!

Audio and Video Posts

Share audio and video content:

/media /path/to/recording.mp3 Morning birdsong from the park
/media /path/to/video.mp4 Time-lapse of sunset over the mountains

Audio/video features:

No alt-text required (but consider descriptive post text)
Supports MP3, OGG, WAV, FLAC, M4A audio formats
Supports MP4, WebM, MOV video formats
File size limits depend on your server

Media with Text

Combine media with descriptive text:

/media /path/to/diagram.png Check out this accessibility flowchart I created for TTYverse users

Best practices:

Use post text to provide context
Describe video content for accessibility
Include relevant hashtags
Consider screen reader users

Poll Posts

Single Choice Polls

Create polls where users select one option:

/poll What's your favorite fediverse client feature?

Poll creation process:

Creating single choice poll: What's your favorite fediverse client feature?
Poll duration (default 24h): 2d
Enter options (press Enter with no text to finish):
Option 1: Accessibility features
Option 2: Command-line interface
Option 3: Cross-instance support
Option 4: Media handling
Option 5: [press Enter to finish]
-- Poll posted successfully

Multiple Choice Polls

Create polls allowing multiple selections:

/mpoll Which TTYverse features do you use most? (select all that apply)

Poll options:

Minimum 2 options required
Maximum 10 options (server may limit to 4)
Each option limited to 50 characters
Duration: minutes, hours, days, or weeks

Poll Best Practices

Effective poll design:

Clear, specific questions
Comprehensive option coverage
Appropriate duration for topic
Consider your audience's time zones

Poll duration guidelines:

1-6 hours: Quick decisions, urgent feedback
24 hours: General interest, broad participation
2-3 days: Community discussions, important decisions
1 week: Major surveys, comprehensive feedback

Advanced Posting Features

Content Warnings

Posts with content warnings display special formatting:

a5> {,POST_ID} <username> (1h ago) via Web [Public] [CW: Politics]
    [Content warning text] Political discussion about recent legislation...

Content warning usage:

Server-dependent feature
Hides sensitive content behind warnings
User choice to expand content
Common for sensitive topics

Hashtag Usage

Effective hashtag strategies:

/post Just released a new accessibility guide for fediverse clients! 

#accessibility #fediverse #inclusion #screenreader #commandline #ttyverse

Hashtag best practices:

Use relevant, specific tags
Mix broad and niche hashtags
Research community conventions
Avoid excessive hashtag spam

Mention Handling

Mention other users in posts:

/post Thanks @storm@stormux.org for creating such an accessible fediverse client!

Mention features:

Notifies mentioned users
Works across instances
Use full @username@domain format for remote users
Creates conversation opportunities

Posting Workflow Examples

Daily Updates

Personal sharing:

/post Starting the day with some TTYverse timeline reading. Love how accessible this client makes the fediverse! #morningroutine

/media ~/photos/coffee.jpg 
# Alt-text: "Steam rising from a dark coffee mug on a wooden desk"
# Message: Perfect morning fuel for productivity

Technical Discussions

Educational content:

/post New blog post: "Why Command-Line Fediverse Clients Matter for Accessibility"

Key points:
- Screen reader compatibility
- Keyboard-only navigation  
- Consistent text formatting
- Audio notification support

#accessibility #fediverse #inclusion

Link: https://myblog.example.com/cli-fediverse-accessibility

Community Engagement

Interactive content:

/poll What accessibility feature would you most like to see improved in fediverse clients?

# Options:
# 1. Better alt-text enforcement
# 2. Enhanced screen reader support
# 3. Audio notifications
# 4. Keyboard navigation
# 5. High contrast themes

Duration: 3d

Creative content:

/media ~/recordings/bird-song.mp3 Recorded this beautiful dawn chorus during my morning walk. The robins were particularly active today! 

#nature #birds #morningwalk #audio

Post Management

Post Engagement

Monitor your post performance:

Engagement indicators:

Posts show boost and favorite counts when > 0
Format: boosts: 5, favorites: 12 on metadata line
Helps gauge content resonance
Appears in timeline display

Post Interactions

Interact with your own posts:

/url a3                 # Open URL from your post
/thread a3              # View conversation thread
/boost a3               # Boost your own post (if supported)

Post Visibility

Understanding post reach:

Public posts:

Appear in follower timelines
Visible in local/federated timelines
Discoverable through search
Cross-instance federation

Unlisted posts:

Visible to followers
Not in public timelines
Accessible by direct link
Good for casual updates

Troubleshooting Posting

Common Post Issues

Post failed to send:

Check network connectivity: /refresh
Verify authentication: /rate
Check character limits (server-dependent)
Retry posting: repeat /post command

Media upload failures:

Check file exists and is readable
Verify file size limits (typically 8MB for images)
Ensure alt-text provided for images
Check supported file formats

Polls not working:

Verify server supports polls
Check option count (many servers limit to 4)
Ensure minimum 2 options provided
Verify option length (50 character limit)

Debug Posting Issues

Enable verbose mode:

/verbose                # Enable detailed output
/post test message      # Try posting with debug info

Check server limits:

/rate                   # Check API rate limits

Test media functionality:

/media /path/to/small-test-image.jpg
# Test with small file first

Best Practices

Accessibility-First Posting

Essential practices:

Always provide alt-text for images (TTYverse enforces this)
Use descriptive text for audio/video content
Write clear, concise posts for screen readers
Use hashtags thoughtfully for discovery
Consider your audience when posting

Content Quality

Effective posting:

Provide context for shared links
Use meaningful hashtags
Engage respectfully with others
Share diverse, valuable content
Respect community norms

Privacy Considerations

Posting privacy:

Consider post visibility before sharing
Be mindful of who can see your content
Remember that public posts are searchable
Respect others' privacy in replies and mentions

See also: Media Uploads | Polls | Basic Usage | Advanced Features

Posting