Skip to content

Settings

Configure FenLiu's behavior and export filters in the Settings page.

Accessing Settings

Click Settings in the main navigation to access all configuration options.

Export Filters

Export filters determine which approved posts are eligible for export to Curated Queue.

Don't Reblog Users

Block specific Fediverse accounts from being exported.

Add a blocked user: 1. Enter the account identifier (e.g., @spammer@mastodon.social) 2. Click Add 3. Posts from this user will never be exported

Remove a blocked user: 1. Find the user in the blocklist 2. Click Delete 3. Posts from this user are now eligible for export

Use cases: - Block accounts that frequently post low-quality content - Exclude automated/bot accounts - Prevent problematic users from appearing in your reblogs

Don't Reblog Hashtags

Block posts containing specific hashtags from being exported.

Add a blocked hashtag: 1. Enter the hashtag (without #) 2. Click Add 3. Posts containing this hashtag will never be exported

Remove a blocked hashtag: 1. Find the hashtag in the blocklist 2. Click Delete 3. Posts with this hashtag are now eligible for export

Use cases: - Exclude off-topic content - Block NSFW hashtags - Prevent community drama (e.g., #drama, #discourse) - Filter regional content you don't want

Attachments-Only Export

When enabled, only posts with media attachments are exported to Curated Queue.

Enable: 1. Toggle Attachments-Only to ON 2. Only posts with images, videos, or other media are exported 3. Text-only posts won't be exported

Disable: 1. Toggle Attachments-Only to OFF 2. All approved posts (with or without media) are exported

Use cases: - Curate media-focused content (photography, art, memes) - Reduce text-heavy posts - Focus on visual content only

Auto-Reject Settings

Auto-Reject Blocked Posts

When enabled, posts from blocked users or with blocked hashtags are automatically rejected during fetch.

Enable: 1. Toggle Auto-Reject Blocked Posts to ON 2. Posts matching blocklists are rejected immediately 3. Reduces review burden

Disable: 1. Toggle Auto-Reject Blocked Posts to OFF 2. All posts appear in review interface 3. You manually approve/reject

Recommendation: Enable this to avoid reviewing posts you'll never approve anyway.

Auto-Reject Bots

When enabled, posts from accounts flagged as bots (author_is_bot = true) are automatically rejected during fetch.

Enable: 1. Toggle Auto-Reject Bots to ON 2. Bot-authored posts are rejected on import 3. Keeps the review queue focused on human content

Disable: 1. Toggle Auto-Reject Bots to OFF 2. Bot posts appear in the review interface for manual review

Auto-Reject Summary

When fetching posts, FenLiu automatically rejects posts if: - The author is in the "Don't Reblog Users" list and Auto-Reject Blocked Posts is ON - The post contains a blocked hashtag and Auto-Reject Blocked Posts is ON - The author is flagged as a bot and Auto-Reject Bots is ON

Reblog Controls Summary

After configuring filters, the queue preview shows which approved posts are eligible:

  • Eligible for export: Meet all filter criteria
  • Blocked by user: Author is in "Don't Reblog" users list
  • Blocked by hashtag: Post contains blocked hashtag
  • Missing attachments: Attachments-Only enabled but post has none

API Access

Manage settings programmatically:

# Get reblog settings
curl http://localhost:8000/api/v1/reblog-controls/settings

# Update settings
curl -X PUT http://localhost:8000/api/v1/reblog-controls/settings \
  -H "Content-Type: application/json" \
  -d '{
    "attachments_only": true,
    "auto_reject_blocked": true
  }'

# List blocked users
curl http://localhost:8000/api/v1/reblog-controls/blocked-users

# Add blocked user
curl -X POST http://localhost:8000/api/v1/reblog-controls/blocked-users \
  -H "Content-Type: application/json" \
  -d '{"account_identifier":"@spammer@mastodon.social"}'

# Delete blocked user
curl -X DELETE http://localhost:8000/api/v1/reblog-controls/blocked-users/1

# List blocked hashtags
curl http://localhost:8000/api/v1/reblog-controls/blocked-hashtags

# Add blocked hashtag
curl -X POST http://localhost:8000/api/v1/reblog-controls/blocked-hashtags \
  -H "Content-Type: application/json" \
  -d '{"hashtag":"drama"}'

# Delete blocked hashtag
curl -X DELETE http://localhost:8000/api/v1/reblog-controls/blocked-hashtags/1

See Reblog Controls API Documentation for details.

Best Practices

Build Blocklists Gradually

  1. Start with few filters
  2. As you review, identify patterns
  3. Add blocked users/hashtags based on patterns
  4. Refine over time

Use Auto-Reject Wisely

Enable auto-reject after your blocklists are stable. Initially, keep disabled to see what would be rejected.

Monitor Queue Health

  1. Check Queue preview regularly
  2. See how filters affect what's exported
  3. Adjust filters if too strict or too lenient

Balance Curation

Too many filters: - Queue becomes empty - Export slows down - Might reject good content

Too few filters: - Bad content exports - Overwhelms your audience - Requires more review

Examples

Photography-Only Curation

  1. Enable Attachments-Only: ON
  2. Block common text hashtags
  3. Approve only high-quality photos
  4. Result: Clean, visual-focused queue

Tech News Curation

  1. Add hashtags like #spam, #promo, #ads to "Don't Reblog"
  2. Add tech spam accounts to blocklist
  3. Enable Auto-Reject Blocked
  4. Only quality tech posts export

NSFW-Free Curation

  1. Add common NSFW hashtags to blocklist
  2. Block adult-focused accounts
  3. Enable Auto-Reject Blocked
  4. Family-safe queue

Troubleshooting

Queue Suddenly Empty

  1. Check if you added too many filters
  2. Review blocked users/hashtags
  3. Consider relaxing criteria
  4. Check auto-reject is not overly aggressive

Unwanted Posts Still Exporting

  1. Add source accounts to blocklist
  2. Add problematic hashtags to blocklist
  3. Ensure Auto-Reject Blocked is enabled
  4. Review more carefully before approving

Can't Find a Post in Queue

  1. Check if blocked by user filter
  2. Check if blocked by hashtag filter
  3. Check if attachments-only is enabled (post has no media)
  4. Use Queue preview to see why post is excluded

Next Steps