mirror of
https://framagit.org/veretcle/oolatoocs.git
synced 2025-07-20 12:31:18 +02:00
📝: update doc
This commit is contained in:
18
README.md
18
README.md
@@ -1,10 +1,13 @@
|
|||||||
# oolatoocs, a Mastodon to Twitter bot
|
# oolatoocs, a Mastodon to Twitter/Bluesky bot
|
||||||
|
## A little bit of history
|
||||||
|
|
||||||
So what is it? Originally, I wrote, with some help, [Scootaloo](https://framagit.org/veretcle/scootaloo/) which was a Twitter to Mastodon Bot to help the [writers at NintendojoFR](https://www.nintendojo.fr) not to worry about Mastodon: the vast majority of writers were posting to Twitter, the bot scooped everything and arranged it properly for Mastodon and everything was fine and dandy. It was also used, in an altered beefed-up version, for [Nupes.social](https://nupes.social) to make the tweets from the NUPES political alliance on Twitter, more easily accessible in Mastodon.
|
So what is it? Originally, I wrote, with some help, [Scootaloo](https://framagit.org/veretcle/scootaloo/) which was a Twitter to Mastodon Bot to help the [writers at NintendojoFR](https://www.nintendojo.fr) not to worry about Mastodon: the vast majority of writers were posting to Twitter, the bot scooped everything and arranged it properly for Mastodon and everything was fine and dandy. It was also used, in an altered beefed-up version, for the (now defunct) Mastodon Instance [Nupes.social](https://nupes.social) to make the tweets from the NUPES political alliance on Twitter, more easily accessible for Mastodon users.
|
||||||
|
|
||||||
But then Elon came, and we couldn’t read data from Twitter anymore. So we had to rely on copy/pasting things from one to another, which is not fun nor efficient.
|
But then Elon came, and we couldn’t read data from Twitter anymore. So we had to rely on copy/pasting things from one to another, which is not fun nor efficient.
|
||||||
|
|
||||||
Hence `oolatoocs`, which takes a Mastodon Timeline and reposts it to Twitter as properly as possible. And since Bluesky seems to be hype right now, it also incorporates Bluesky support since v3.0.0.
|
## And now…
|
||||||
|
|
||||||
|
Hence `oolatoocs`, which takes a Mastodon Timeline and reposts it to Twitter as properly as possible. And since Bluesky seems to be hype right now, it also incorporates Bluesky support since v3.
|
||||||
|
|
||||||
Bluesky support is mandatory for now on: you can’t have Twitter or Bluesky, you must have both. I might change this behaviour in a near future, especially when I will inevitably have to drop support for Twitter. If you just want Twitter support, just stick with v2.4.x release, it’ll get the job done exactly as the newer version for now.
|
Bluesky support is mandatory for now on: you can’t have Twitter or Bluesky, you must have both. I might change this behaviour in a near future, especially when I will inevitably have to drop support for Twitter. If you just want Twitter support, just stick with v2.4.x release, it’ll get the job done exactly as the newer version for now.
|
||||||
|
|
||||||
@@ -16,8 +19,11 @@ What it can do:
|
|||||||
* Reproduces the Toot content into the Tweet/Record;
|
* Reproduces the Toot content into the Tweet/Record;
|
||||||
* Cuts (poorly) the Toot in half in it’s too long for Twitter/Bluesky and thread it (this is cut using a word count, not the best method, but it gets the job done);
|
* Cuts (poorly) the Toot in half in it’s too long for Twitter/Bluesky and thread it (this is cut using a word count, not the best method, but it gets the job done);
|
||||||
* Reuploads images/gifs/videos from Mastodon to Twitter/Bluesky
|
* Reuploads images/gifs/videos from Mastodon to Twitter/Bluesky
|
||||||
|
* ⚠️ Bluesky does not support mixing images and videos. You can have up to 4 images on a Bsky record **or** 1 video but not mix around. If you do so, only the video will be posted on Bluesky.
|
||||||
|
* ⚠️ Bluesky does not support images greater than 1Mb (that is 1,000,000,000 bytes or 976.6 KiB). I might incorporate soon a image quality reducer or WebP transcoding to avoid this issue.
|
||||||
* Can reproduce threads from Mastodon to Twitter/Bluesky
|
* Can reproduce threads from Mastodon to Twitter/Bluesky
|
||||||
* Can reproduce poll from Mastodon to Twitter/Bluesky
|
* Can reproduce poll from Mastodon to Twitter
|
||||||
|
* ⚠️ Bluesky does support polls for now. So the poll itself is just presented as text from Mastodon instead which is not the most elegant.
|
||||||
* Can prevent a Toot from being tweeted/recorded to Bluesky by using the #NoTweet (case-insensitive) hashtag in Mastodon
|
* Can prevent a Toot from being tweeted/recorded to Bluesky by using the #NoTweet (case-insensitive) hashtag in Mastodon
|
||||||
|
|
||||||
# Configuration file
|
# Configuration file
|
||||||
@@ -26,7 +32,7 @@ The configuration is relatively easy to follow:
|
|||||||
|
|
||||||
```toml
|
```toml
|
||||||
[oolatoocs]
|
[oolatoocs]
|
||||||
db_path = "/var/lib/oolatoocs/db.sqlite3" # the path to the DB where toot/tweet are stored
|
db_path = "/var/lib/oolatoocs/db.sqlite3" # the path to the DB where toots/tweets/records are stored
|
||||||
|
|
||||||
[mastodon] # This part can be generated, see below
|
[mastodon] # This part can be generated, see below
|
||||||
base = "https://m.nintendojo.fr"
|
base = "https://m.nintendojo.fr"
|
||||||
@@ -41,7 +47,7 @@ consumer_secret = "<REDACTED>"
|
|||||||
oauth_token = "<REDACTED>"
|
oauth_token = "<REDACTED>"
|
||||||
oauth_token_secret = "<REDACTED>"
|
oauth_token_secret = "<REDACTED>"
|
||||||
|
|
||||||
[bluesky]
|
[bluesky] # this is your Bsky handle and password + a writable path for the session handling
|
||||||
handle = "nintendojofr.bsky.social"
|
handle = "nintendojofr.bsky.social"
|
||||||
password = "<REDACTED>"
|
password = "<REDACTED>"
|
||||||
config_path = "/var/lib/oolatoocs/bsky.json"
|
config_path = "/var/lib/oolatoocs/bsky.json"
|
||||||
|
Reference in New Issue
Block a user