Things still needing implementation for a complete client

[Preloading]

API Endpoints

DMs

• GET /1/direct_messages.xml
• GET /1/direct_messages/sent.xml
• POST /1/direct_messages/new.xml

Users

• GET /i/activity/about_me.json (connect tab)
• GET /1/statuses/friends.xml
• GET /1/statuses/following_timeline.json (no bsky equivalent)
• GET /1/statuses/followers.xml
• GET /1/favorites/:id.json (pageation)
• GET /1/:handle/lists/memberships.xml
• GET /1/:handle/lists.xml
• GET /1/:handle/lists/subscriptions.xml
• GET /1/followers.xml (and json)
• GET /1/friends.xml (and json)

Account

• POST /1/account/push_destinations.xml (/1/account/push_destinations/device.xml should be impleneted first)
• GET /1/saved_searches.xml (no bsky equivalent)
• GET /1/account/push_destinations/device.xml (need XML Root)
• The settings one (need XML Root)
• POST /1/account/update_profile.xml

Discovery

• GET /i/discovery.json (no bsky equivalent) (need info)
• GET /1/trends/1.json
• GET /i/search.json (need info)
• GET /1/users/recommendations.json
• GET /1/users/suggestions.json (no bsky equivalent)

Posting

• upload.twitter.com/1/statuses/update_with_media.json (needs patches, and easter egg making my life miserable)

Interaction

• /1/statuses/destroy/:id.json (implemented, but deleting retweets sets the id to (null)
  More to come as more gets implemented

[upintheairsheep]

Have you also remembered the client labels (Twitter for ____ usually)? They have to be stored on the database if you are the one posting it, while others will just say "BlueSky" or "Mastodon".

[Preloading]

be stored on the database if you are the one posting it, while others will just say "BlueSky" or "Mastodon".

@upintheairsheep I just always default to Bluesky as the source. It doesn't need to be stored in the database

[retrofoxxo]

Oh yeah additional url for the connect tab

GET /1/statuses/mentions.json

And an additional url for posting tweets/skeets with Media

POST /1/statuses/update_with_media.json