Modbot Docs
Moderation

Bluesky

Connecting Modbot to your group's Bluesky account, with an app password or by signing in with Bluesky, so posts from the Marketing page can go to Bluesky too.

Modbot can send your group's posts to a Bluesky account, beside Discord and your VRChat group. You make an app password for the account in Bluesky, give it to Modbot with the account's handle, and press Check: Modbot signs in and tells you who it is signed in as, and whether the account is marked as automated. Then you turn Posting on, and a post on the Marketing page can tick Bluesky.

When your Modbot has a public https:// address, you can instead Sign in with Bluesky on Bluesky's own sign-in page, with no app password at all. See Sign in with Bluesky.

Everything here is in Settings, Bluesky, and needs Change settings.

What you need

  • A Bluesky account for your group. An account of its own is best, so Modbot never signs in to a person's own account.
  • An app password for it, or a public https:// address for your Modbot to sign in with Bluesky. Never give Modbot the account's main password: Modbot refuses it.

Set it up

1. Mark the account as automated

Bluesky asks accounts that post by themselves to say so. In the Bluesky app, open the account's settings and mark it as an automated (bot) account. Modbot's Check shows whether the account says so.

2. Make an app password

In the Bluesky app, signed in as your group's account:

  1. Open Settings, Privacy and security, App passwords.
  2. Click Add App Password and name it Modbot.
  3. Leave access to direct messages off. Modbot never reads or sends messages.
  4. Click Create. Bluesky shows the password once, as four groups of four letters and digits, such as abcd-efgh-ijkl-mnop. Copy it.

An app password can post and delete posts as the account, but cannot change the account's email or its main password. You can revoke it in Bluesky at any time, and Modbot stops posting.

3. Give it to Modbot and Check

In Modbot, go to Settings, Bluesky:

  1. Type the Handle, such as ourgroup (Modbot adds .bsky.social), ourgroup.bsky.social or ourgroup.com. A leading @ is fine, and so is a profile link from bsky.app.
  2. Paste the App password and click Save. The page shows App password: Saved. The password is never shown again.
  3. Click Check.

Modbot refuses anything that is not shaped like an app password with Use an app password.

Sign in with Bluesky

When a Public address is saved under Settings, Server, and it starts with https:// and has no port (such as https://modbot.example.com, not :8443), Settings, Bluesky also has Sign in with Bluesky. Without such an address the button is not there: Bluesky has to reach your Modbot from the internet to sign it in, and only an https:// address with no port will do.

  1. Type the Handle, such as ourgroup (Modbot adds .bsky.social), ourgroup.bsky.social or ourgroup.com, and click Sign in with Bluesky.
  2. Bluesky's sign-in page opens. Sign in as your group's account there, and allow Modbot.
  3. Bluesky sends you back to Settings, Bluesky, which says Signed in. and shows Sign-in: Bluesky, the account and whether it is marked as automated, as Check does.

Modbot never sees the account's password this way. It asks Bluesky only for what posting needs: making and deleting posts, making and deleting the records that say who can reply to a post and whether it can be quoted, pinning a post on the account's profile, uploading a post's picture or video, reading the account's replies and mentions, and changing the profile's name, bio, picture and banner. If Bluesky does not offer that yet, Modbot asks for what an app password can do instead.

A sign-in made before pinning was added cannot pin, and one made before replies were read cannot read them. Click Sign in with Bluesky again once, so Bluesky asks you to allow what is missing. One sign-in covers both. Posting is not affected, and Health says Sign in with Bluesky again to read replies and mentions. An app password already allows it.

A sign-in made before who can reply and quote posts were added cannot set them. A calendar event's post that limits who can reply, or turns quote posts off, waits, and Marketing says Sign in with Bluesky again to let Modbot set who can reply. Click Sign in with Bluesky again once. Posts that anyone can reply to and quote go out as before, and an app password already allows all of it.

One way of signing in at a time. Signing in with Bluesky forgets a saved app password, and saving an app password ends the sign-in with Bluesky.

Changing the public address ends a sign-in with Bluesky, because Bluesky knows Modbot by that address. Sign in with Bluesky again after you change it.

If the page says something went wrong instead:

What it saysWhat to do
Bluesky sign-in was cancelled.You said no, or went back, on Bluesky's page. Try again.
The Bluesky sign-in took too long. Try again.Finish on Bluesky's page within ten minutes.
You were signed out of Modbot before Bluesky sent you back.Sign in to Modbot and try again. The person who starts it must finish it.
This Bluesky sign-in was already used.The page was loaded twice. Look at Settings, Bluesky: the first one may have signed in.
Bluesky signed in another account than this handle.On Bluesky's page, sign in as the account the handle names.
Bluesky did not finish the sign-in.Try again.
Could not reach Bluesky.Try again later.

What Check shows

Check finds the account from its handle, signs in, and reads the account's profile. It never posts and changes nothing on the account.

LineWhat it means
Signed in asThe account's handle and its display name.
AutomatedYes when the account is marked as automated, No when it is not.

When something is wrong, Check says what:

What it saysWhat to do
Could not find this handle.Check the spelling. A handle that is a website of your own must still point at the account.
Could not reach the account's server.Bluesky, or the server the account lives on, did not answer. Try again later.
Bluesky did not accept the handle or app password.Make a new app password and save it. Modbot does not sign in again until you do.
The Bluesky sign-in has ended.Bluesky no longer takes Modbot's sign-in with Bluesky. Click Sign in with Bluesky again.
Too many sign-ins. Try again after …See Sign-ins below.
Bluesky is limiting Modbot. Try again after …Bluesky asked Modbot to slow down. Nothing is sent to Bluesky until then.

What Check found stays on the page until you change the handle or the app password. Change either and Check again; posts wait until it passes.

Posting

Once Check has passed, the Posting switch appears. It is off to start. On, posts that tick Bluesky go out at their time; off, they wait and show Off. The same switch is in Settings, Posts, as Bluesky posts.

Post numbers

A Bluesky post that went out shows its likes, reposts and replies beside its Bluesky badge on the Marketing tab. Modbot asks Bluesky's public API for them, with no sign-in. A post sent in the last 30 days is counted again every 30 minutes; an older one keeps its last numbers, and so does a post that is gone from Bluesky. Nothing shows before the first count. If Bluesky limits Modbot, Modbot waits until the limit resets, and the problem shows on Health under Posts until a count goes through.

Replies and mentions

New replies, mentions and quotes of the group's Bluesky account are saved in the audit log as entries, and Now shows a line Bluesky replies and mentions with a count that opens the audit log at those entries. Each entry keeps who wrote it (their name and handle), what they wrote and a link to the post on Bluesky; a reply also names the post it answers when Modbot sent that post. Likes, reposts and follows are not saved: there are too many to be useful.

While Posting is on, Modbot asks the account's own server for them about every 3 minutes, and saves each one once. With Posting off it does not read them, and Health says nothing about them. The account's own posts are left out. The first time, it starts from then and saves nothing from before. Each pass reads at most the newest 300, so more than that in 3 minutes would leave the oldest out.

Reading needs the account's own sign-in: an app password allows it, and so does a Sign in with Bluesky made after replies were added. An older one has to sign in again.

If Bluesky limits Modbot, Modbot waits until the limit resets and never asks again before then. Any other failure waits 5 minutes. Posting is not held up by either. The problem shows on Health under Posts, as Bluesky · Replies and mentions, until a read goes through. Bluesky's limit for this call has not been measured, so Modbot's pace is a cautious guess.

Profile page

Under Integrations, next to VRChat and Discord, the Bluesky page shows your group's account the way Bluesky does: the banner, the round picture, the name and @handle, how many follow it, how many it follows and how many posts it made, and the bio. It has two tabs:

  • Posts: the posts Modbot sent to the account, newest first, with their likes, reposts and replies.
  • Replies: the replies and mentions Modbot saved in the audit log.

You need See analytics to open the page, See posts for the Posts tab and See the audit log for the Replies tab.

Edit profile

Edit profile changes four things on Bluesky: the name, the bio, the picture and the banner. It needs Change settings. Anything you leave alone stays as it is, and an empty name or bio clears it. It does not touch the pinned post or anything else on the profile. It does not change your VRChat group.

Bluesky's limits:

Limit
NameUp to 64 characters
BioUp to 256 characters
Picture and bannerA PNG or JPEG, under 1 MB each

Your browser makes a copy of each picture you choose, under 1 MB, the way it does for posts, so any picture your browser can open will do. Modbot checks the limits before it asks Bluesky anything.

If somebody changed the profile on Bluesky while you were saving, Modbot saves nothing and says so; open Edit profile again and save once more. Saves are a few seconds apart at least. If a save fails, the page and Health under Posts say why, until a save goes through. If Bluesky limits Modbot, nothing is sent until the limit resets. Bluesky's limits for these calls have not been measured, so Modbot's pace is a cautious guess.

The page reads the numbers from Bluesky's public API, with no sign-in, and keeps them for 10 seconds. Each change is saved in the audit log with the settings changes.

Calendar events

An event on the Calendar can post itself here: tick Bluesky on the event, pick Post it (1 hour, 1 day, 3 days or 1 week before), and every date of the event gets its own post, sent that long before it starts. These posts appear in Marketing like any other, and follow the same rules: Posting, Pause all posting, the hourly limit and Bluesky's rate limit.

The event's Bluesky tab also sets who can reply (Anyone, Nobody, or your followers, the people you follow and the people you mention), whether quote posts are allowed, and the post's language (up to three). The languages go in the post itself; who can reply and quote posts go in two small records Modbot makes right after the post.

Bluesky cannot edit a post, so when an event changes, Modbot deletes the post that already went out and posts again. A cancelled date, a cancelled or deleted event, or Bluesky turned off on the event, deletes its post and makes no new one. While Posting is off, Modbot neither makes nor deletes these posts: a cancelled event's post stays on Bluesky until Posting is on again.

A post ends with the tags of the event's categories, then the tags under Tags on every post (up to five, such as #VRChat #Karaoke; type # or leave it out, split them with spaces or commas). Changing any tag changes the words of every post that carries it, so the posts of dates that have not started and are already up are deleted and posted again. See Tags.

When the first person is in the instance of a date whose event has Announce on Bluesky when the first person joins ticked, Modbot replies under that date's post: We're live in and the world's name, then a link (the instance's join link when Who can join is Anyone, otherwise your VRChat group's page). The reply is in Marketing too and is sent once. It needs the date's post to be on Bluesky; without one there is no reply. See Announce when the first person joins.

A calendar event's post carries up to four pictures as full pictures under the text, each with its own alt text (the post's title when the alt text is left empty), and has no link card; a link in the text stays clickable. The event's cover is the first picture until the pictures are changed on the Bluesky tab. Modbot sends a small copy of each picture, made in your browser when the picture is chosen: at most 2000 pixels on its longer side and under 1 MB. An event whose cover has no such copy (chosen before this was added) gets its copy the next time someone who can manage the calendar or templates opens the Calendar page; their browser makes it without a word on screen. Until then it sends the cover itself when it is 1 MB or smaller; otherwise the post goes with its link card and no picture.

A calendar event's post can carry one video instead of pictures: Bluesky allows a video no pictures beside it, so adding a video takes the pictures out and adding a picture is not possible while there is a video. The video is a file (an MP4, MPEG, WebM or QuickTime file of at most 50 MB) or a link. A file is kept by Modbot from the moment it is picked, because Bluesky deletes an upload that no post points to within hours and the post goes out days after the event is saved; it goes up to Bluesky only as the post is made, and Modbot deletes it once no event, template or post still to be sent uses it. A link is kept only as an address: Modbot downloads the video from it as the post goes out, and the link must start with https:// and point at a public address. Like a picture, the video has an alt text (the post's title when left empty). Bluesky shows a video a few seconds after the post is up. When the video cannot go (the link does not answer or is not a video, the file is gone, Bluesky refuses it, or the sign-in is older than video uploads), the post goes up without it and its line in Marketing says why. A sign-in made before video uploads were added needs Sign in with Bluesky done again for a post with a video.

A calendar event's post can carry one GIF from Klipy instead of pictures or a video. The GIF button under the post's box searches Klipy; it is there once the Klipy key is set under Settings, Bluesky, GIF search, Klipy key, and with no key there is no button. The key can only have letters, numbers, - and _. The GIF goes up the way Bluesky's own app posts one, as a link card with the GIF's Klipy address, so Bluesky's apps play it in the feed. Modbot keeps only that address and the GIF's alt text, never a copy of the GIF, and refuses any address that is not on Klipy's static.klipy.com. The key goes to everyone who can manage the calendar or its templates, because their browsers do the searching.

Pin the next event

Under Settings, Bluesky, the Pin the next event switch (shown once Check has passed) keeps the post of the next date pinned on the account's profile. Of the dates whose post is on Bluesky, it pins the one that starts first and has not ended. When that date ends it pins the next date's post, and when no later date has a post it takes the pin off. A pass looks at the profile at most once every 15 minutes unless something changed, and only while Posting is on and Pause all posting is off.

A post you pinned by hand stays. Modbot pins only while nothing is pinned or while the pinned post is an event post Modbot made; a post written on the Marketing tab and pinned by hand is left alone. Unpin yours on Bluesky and Modbot pins the next date's post at its next look. Modbot changes nothing else on the profile: it writes the profile back as it read it, only if nobody saved it in between, with just the pinned post changed. Pinning and unpinning are recorded as Post pinned and Post unpinned. When Bluesky refuses a pin (a sign-in made before the profile right was asked for needs Sign in with Bluesky again), the Posts card on Health says why, until a pin goes through. Turning the switch off leaves the pin where it is.

Weekly line-up

Under Settings, Bluesky, the Weekly line-up switch (shown once Check has passed) makes one post a week that lists the next seven days. Pick the Day, the time (At, on the hour) and the Time zone; it starts on Monday at 12:00 in UTC. Turning it on never posts for a time that has already gone by.

The post starts with This week at and the group's name, then one line for each date, in order: the day, the time in the line-up's time zone on a 24-hour clock, and the title (such as Mon 20:00 Karaoke).

  • Which dates. Every date in the next seven days of an event that everyone can see: Visible to is Everyone and no role is needed. Where the event goes (VRChat, Discord, Google) and whether it goes to Bluesky itself do not matter, so a Discord-only event counts. Visible to is always shown in the form and starts as Group, so set it to Everyone for an event that belongs in the line-up. A members-only event is never in it, and neither is a cancelled date or a cancelled or deleted event.
  • Too long. A post holds 300 characters. Modbot lists as many dates as fit, then +N more.
  • The link. When the group's Google calendar is set up and public, the post ends with its public page, which gives the post a link card. Without that there is no link.
  • A week with no dates gets no post.
  • After it is posted the post is left alone. A date changed or cancelled later does not change it, and it is never deleted or posted again.
  • A missed time. A time more than an hour past (because Posting was off, say) is skipped, and the next week's post goes out as usual.

It is an ordinary post: it shows in Marketing and follows Posting, Pause all posting, the hourly limit and Bluesky's rate limit, and Modbot never sends it again after a rate limit. When it fails, the Posts card on Health shows it. See Weekly line-up.

Remove

Remove asks first, then forgets the handle, the app password or the sign-in with Bluesky, and Modbot's sign-in, and turns Posting off. Posts already on Bluesky stay there, calendar events' posts included; delete them from Marketing first if you want them gone. Revoke the app password in Bluesky too.

Sign-ins

Modbot signs in once and keeps its sign-in, encrypted in its database, so a restart does not sign in again. It renews the sign-in by itself as Bluesky asks. It signs in with the app password again only when the kept sign-in stops working, and then at most once every 10 minutes and 20 times a day, far under Bluesky's own limits. Saving a new app password lets the next sign-in go at once.

A sign-in with Bluesky is renewed the same way, with Bluesky's sign-in server, a little before each short-lived token ends. It has no app password to fall back on: when Bluesky stops taking it, posts wait, the page says The Bluesky sign-in has ended., and someone clicks Sign in with Bluesky again.

When Bluesky rate limits Modbot, Modbot stops every request to Bluesky until the time Bluesky says, and never sends the request again before then.

What leaves your server

SentToWhen
The handleBluesky's public API, or the handle's own websiteCheck
The account's lasting idplc.directory, or the account's own websiteCheck, and to find where an older post lives
The account's lasting id and the app password, then Modbot's sign-inThe account's own serverSigning in and renewing
Modbot's address, the handle, and requests signed with Modbot's own keyBluesky's sign-in server, which the account's own server namesSign in with Bluesky, and renewing that sign-in
A post's text, and either its pictures (a small copy of each, with the alt text you wrote, or the post's title when you wrote none; up to four for a calendar event, one for any other post), or a calendar event's one video (a file or the video found at a link, with its alt text), or a calendar event's one GIF (its Klipy address and alt text, as a link card), or, when it has none of these, its link card (the post's title and the link)The account's own server, and from there public on BlueskyOnly for posts with Bluesky ticked, and for each date of a calendar event with Bluesky on
The post's languages (up to three codes such as en), when you picked some; and, when you limited who can reply or turned quote posts off, a record saying so, with the address of the post it belongs toThe account's own server, and from there public on BlueskyOnly for a calendar event with Bluesky on and those choices set, with each date's post
A reply: "We're live in" the world's name and a link, with the address and content id of the date's post it answersThe account's own server, and from there public on BlueskyOnly for an event with Announce on Bluesky when the first person joins ticked, once for each date, when the first person is in the instance
The weekly line-up: the group's name, and the title and time of each public date in the next seven days, with the link to the Google calendar's public pageThe account's own server, and from there public on BlueskyOnly with Weekly line-up on, once a week
The account's profile (its name, description, pictures and pinned post), written back with only the pinned post changedThe account's own server, and from there public on BlueskyOnly with Pin the next event on, when the pinned post changes
The account's profile (its name, description, pictures and pinned post), written back with only the name, bio, picture and banner you changed, and a picture you choseThe account's own server, and from there public on BlueskyOnly when you press Save in Edit profile
The account's lasting id (to ask for its profile and its numbers)Bluesky's public API, with no sign-inWhen the Bluesky page is opened, at most once every 10 seconds
The address of a post Modbot madeThe account's own serverWhen Modbot deletes a post, such as one a changed or cancelled calendar event made
The addresses of the posts Modbot made in the last 30 days, up to 25 in a requestBluesky's public API, with no sign-inAbout every 30 minutes for each post, to read its likes, reposts and replies
Modbot's sign-in, asking for the account's replies, mentions and quotes (a request for the account's own notifications)The account's own server, which passes it on to BlueskyAbout every 3 minutes, once the account has passed Check

Posts on Bluesky are public, and other services copy them. Deleting one removes it from Bluesky, not from copies others already took.

Modbot never mentions anyone in a Bluesky post: an @handle in the text stays plain text, because a mention would notify that person. Nothing about your members goes in a post. See Privacy and Security.

With Sign in with Bluesky, Bluesky's sign-in server also reads Modbot's client document at /oauth/bluesky/client-metadata.json on your public address: Modbot's name, its address, where to send you back, and the public half of Modbot's own signing key. The private half never leaves your server.

Not built yet

The world's picture is not added to a post for you; add it yourself as one of the post's pictures. See Not built yet.

Modbot is not endorsed by or affiliated with VRChat Inc. or Discord Inc. VRChat is a trademark of VRChat Inc. Discord is a trademark of Discord Inc. SteamVR is a trademark of Valve Corporation. Windows is a trademark of Microsoft Corporation. Docker is a trademark of Docker, Inc. PostgreSQL is a trademark of the PostgreSQL Community Association of Canada. Railway is a trademark of Railway Corp. Other names are trademarks of their respective owners; see Legal. Modbot and its logo are trademarks of the Modbot project. Open source under AGPL-3.0.

On this page