muskit/NijiHolo_EN_ID_Bot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Updated README.md

Browse Source
This commit is contained in:
muskit
2022-09-25 23:57:06 -07:00
committed by msk
parent b9b26d462d
commit 0038439728
1 changed files with 19 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+19 -20
View File
@@ -4,28 +4,27 @@
**This project is intended to run [this account](https://twitter.com/NijiHolo_EN_ID).** **This project is intended to run [this account](https://twitter.com/NijiHolo_EN_ID).**
## Running modes
The bot will be runnable in three modes:
* Catch-up (`c`): intended to run only once, scan all accounts for cross-company tweets and post them. Terminate when done posting all.
* Listen (`l`): post any new tweets that come up if it's cross-company
* may implement short-term catch-up function
* Command-line: TBA
## Roadmap ## Roadmap
* Read past tweets of members from both companies * ~~Read past tweets of members from both companies~~
* Track tweets in queue and history/log files * ~~Create screenshot of tweet~~
* Create image of tweet, including up to three image attachments from that tweet * Track tweets in queue files
* Combine image(s) with quote retweet * Post tweets along with screenshot of tweet
* Don't tweet already-existing tweets (check our past quote RTs; might be saved in a file for quicker access) * Include screenshot of tweet being replied to?
* Listen for live tweets as soon as they post * Track posted tweets in a history file
* Combine image with quote tweet
* Don't tweet already-existing tweets (check our past quote tweets; might be saved in a file for quicker access)
## Notes ## Notes
* Tweets should only occur if involved parties are cross-company * Tweets should only occur if involved parties are cross-company
* Tweets should only occur if interaction involves [EN and EN] or [EN and (former) ID] parties * Tweets should only occur if interaction involves [EN and EN] or [EN and (former) ID] parties
* cross-company ID interactions are regular enough * cross-company ID interactions are regular enough IMO
* Text of our tweet should include involved names (w/o @) and the message, up to our tweet limit * Our tweets should include:
* this, along with image, helps archive deleted tweets * involved names (w/o @) and the tweet (as a quote tweet)
* screenshot of the tweet (+ maybe image of tweet being replied to when applicable)
## API Calls
**retrieving tweets from a user**
https://oauth-playground.glitch.me/?id=usersIdTweets
* `id`: user
* `max_results=100`: 100 is the highest number of tweets we can retrieve
* `pagination_token`: token that takes us to the next/prev page of tweets
* use `meta[next_token]`
* `expansions=entities.mentions.username,in_reply_to_user_id`
* exposes mentions and replied users