bolhaverse PT

mastodon 4.7.5 · bolha-tangerine

The bolha Mastodon, with more room

bolha.us runs its own Mastodon build: the upstream code with a few higher limits and a few extra features. This page lists everything that changes, the source code, the ready-made images and how to use them on your instance.

what changes

FeatureUpstream MastodonOn bolha
Post length500 characters2400 characters
Long posts without “read more”collapsed above 32 linescollapsed only above 100 lines
Profile bio500 characters2400 characters
Profile metadata4 fields24 fields
Pinned posts on the profile5 posts12 posts
Poll options4 options of 50 characters12 options of 60 characters
Short mutes6 hours and up10, 30 or 60 minutes
Markdown in postsnot availableheadings, lists and highlighted code
Self-destructing postsnot availablefrom 15 minutes to 24 hours
Local-only postsnot availablestay on the instance, never federate
Post time in the timelineonly “4h”exact time, like “today 02:03”, plus “4h”
Visibility icongreycolored by visibility
API rate limitsdefaultdoubled
Photo uploaded as PNGstays PNGbecomes JPEG, about 15× smaller
Uploaded videokept as sent, up to 4Kup to 1920 px on the long side and 5.5 Mbit/s
ThemedefaultBolha UI (yellow or red) and Tangerine UI in 5 colors

details

Markdown with highlighted code

The composer gets a button to write in Markdown. Code blocks are highlighted per language (highlight.js, with a set of common languages) and headings from H1 to H6 have distinct sizes. Instances that do not understand Markdown receive the post already converted to HTML.

Long posts shown in full

Upstream Mastodon cuts any post taller than 32 lines down to 15 lines with a “read more” button. Here a post is only collapsed above 100 lines, and then 25 lines stay visible. So a post of up to 2400 characters shows in full, even split into paragraphs or in a narrow column. This applies to the web interface; mobile apps have their own rule.

Self-destructing posts

An hourglass in the composer sets how long the post lives: 15 or 30 minutes, 1, 2, 4, 6, 12 or 24 hours. When the time comes the post is deleted as if its author had deleted it: it is gone for everyone and the deletion is sent to other instances. Each remote instance decides whether to honor it, as with any deletion in the fediverse.

Exact post time

In the corner of each post, above the “4h”, you see when it was published: “today 02:03”, “yesterday 21:30”, “Mon 3 Nov 14:12” within the last 6 days, “3 Nov 14:12” in the same year and “12 Aug 2025 09:40” before that. The time follows your browser time zone, and hovering shows the full date.

Colored visibility icons

Each post's visibility icon is colored: blue for public, green for quiet public, amber for followers only and red for private mentions, so you can tell at a glance who can read it. The idea comes from glitch-soc; here it is always on, with lighter shades for the dark themes.

Local-only posts

A button next to the hourglass marks the post as local-only. It is not sent to any other instance: only accounts logged in to the same instance can see it, on the home timeline of the author's followers, on the local timeline and in hashtags. It stays out of the federated timeline, the public profile, RSS and trends. Visitors who are not logged in do not see the post anywhere: not on the local timeline (/public/local), not on the author's profile, not through the direct link, which returns 404. It works with any visibility. Replies to, boosts of and quotes of a local-only post are local-only too. It is not a private post: any account on the instance can see it.

Color-marked posts

A local-only post shows up in the timeline with a green background and a “Local-only” label; a self-destructing one, with a red background. When a post carries both marks, the colors are combined.

Doubled API limits

The request limits per account, per token, for paging and for media were doubled. People using multi-column clients (the advanced interface, Phanpy, Elk) ran out of the upstream limit within minutes. Login, sign-up and password reset limits are unchanged.

Short mutes

The mute dialog gained 10, 30 and 60 minute options, next to the long durations that already existed.

Bolha UI theme

Our theme, with the bolha.io look: yellow (Bolha UI) or red (Bolha UI GCN), light, dark and high contrast, following each person's appearance settings. The accent tints the search box, the notification filters, the compose footer and the filtered-notifications banner. Pick it in Preferences › Appearance. It is an open project that works on any Mastodon 4.7: ui.bolha.us, with screenshots and how to install it. The installed version shows in the sidebar footer, as version-pipeline (for example 1.2.0-1687). Illustration:Bolha UI in yellow and red, dark and light: search, notification filters and compose footer tinted with the accent color

Bolha Custom Release card

Above the footer of the sidebar and the Explore page, a card says this is the bolha build and links to this page.

PNG photos become JPEG

A photo uploaded as PNG, 1 MB or larger and with no transparent pixel, is stored as JPEG, the same way Mastodon already handles HEIC and AVIF. Every fediverse server downloads its own copy of each image: an 8.8 MB PNG photo becomes about 460 KB as JPEG, with no visible difference. PNGs with transparency or under 1 MB (screenshots, art, logos) stay PNG.

Lighter videos

Videos uploaded here are capped at 1920 px on the long side (4K becomes 1080p) and 5.5 Mbit/s. A video already within that is stored as sent, with no re-encoding. In upstream Mastodon an H.264 video is stored as uploaded, up to 99 MB, and every fediverse server downloads its own copy. Videos from other instances are not changed.

bolha features

Not everything bolha offers is a Mastodon change. These apps live outside the Mastodon code, work with any bolha.us account and are open source.

Agendeagende.bolha.us

Schedules posts with everything this Mastodon offers: Markdown, media with descriptions, content warnings, self-destructing posts and local-only posts. It shows the queue in a weekly and monthly calendar, edits scheduled posts and repeats a post every week or month. The instance itself publishes them, so posts go out even if the site is down. It's our own app, in Go, inspired by mastodon-post-scheduler, with open source code.

descreve@descreve

Our alt-text bot. Mention it on a post with an image, or follow it, and it suggests a description (how to use it, in Portuguese). It is a fork of Altbot, not affiliated with the original project, and only serves bolha.us accounts. The code is open: open/custom/descreve. Below is what we changed in the fork.

Edit mode

In Altbot the description always comes as a reply. With descreve you can have it placed straight in the image's ALT, where screen readers find it. Authorize once at descreve.bolha.us and send @descreve --modo-edicao-no-post; to go back to replies, @descreve --modo-reply-no-fio. By default the bot shows the suggestion by private message and only edits after you approve; with confirm no it edits directly. It never overwrites a human-written description, keeps the local-only, expiry and quote marks, and replies instead of editing on posts with polls, since the edit would delete the poll. The token is stored encrypted (AES-256-GCM) and @descreve revoke ends the access.

Claude with a local fallback

Altbot talks to Gemini, Ollama, Transformers and OpenAI-compatible APIs. We added Claude, with a fallback. We have monthly Claude API credits and use them here: each person gets up to 20 images per day on Claude Sonnet 5.5, answered within seconds. After that, or if Claude fails, refuses the image or the credits run out, the bot uses Gemma on Ollama, on our own infrastructure, in about a minute and a half. The reply's signature names the model that actually wrote it. Claude is the default, but each person chooses: anyone who does not want images sent to Anthropic can reply Yes local to the consent request or send @descreve --use-ollama at any time, and go back with @descreve --use-claude. If someone else asks for a description of your image, your choice applies. With Claude, images go to Anthropic: see the bot privacy policy.

Smaller changes

Replies are cut at the end of a sentence to fit in 1200 characters, which used to drop long descriptions. A mention on a post with an image describes that post's image, not the one in the post above. Consent messages are in Portuguese.

Encaminhaencaminha.bolha.us

Gives community members a yourname@bolha.us address that forwards everything it gets to the e-mail on their account. It only receives: you cannot send mail as @bolha.us. It is a perk for accounts that are already part of the place: older than 90 days, with a profile picture and bio, at least one profile field, 10 followers and 37 posts, and not limited by moderation. You confirm the e-mail first and can turn it off at any time. Our own app, in Go, with open source code.

Númerosnumeros.bolha.us

Shows bolha.us in numbers: who posts the most, what goes around and how the place is doing inside. Everything comes from the server itself, every hour, and only profiles set as discoverable make the rankings; adding #nonumeros to your bio keeps you out. Signed in, you see your own numbers and can, if you want, have a public page with them. Our own app, in Go, with open source code.

Círculoscirculos.bolha.us

Shows who is closest to you, from the favourites, replies and boosts on your latest public posts, and makes an image to post. Each person only sees their own circle; the app reads only your username and the token is revoked right after. Rewritten in Go from Mastodon-Circles, with open source code.

Mensagensmensagens.bolha.us

Makes a clean page with only your posts, no boosts or timelines, easy to read and share. The page is public, but it only exists while its link is on your profile: remove the link and it goes offline within minutes. Rewritten in Go from JustMyToots, with open source code.

Poesiapoesia.bolha.us

Turns a bolha.us post into a nice image to share, as PNG or PDF, with no sign-in. Rewritten in Go from Mastopoet, with open source code.

for client developers

The three new features show up in the post creation API. A local-only post comes back with local_only: true. The instance publishes the accepted durations in configuration.statuses.expirations, in the /api/v2/instance response.

# post that deletes itself in one hour (expires_in in seconds)
curl -X POST https://{domain}/api/v1/statuses \
  -H "Authorization: Bearer $TOKEN" \
  -d "status=gone in an hour" \
  -d "expires_in=3600"
# local-only post (never leaves the instance)
curl -X POST https://{domain}/api/v1/statuses \
  -H "Authorization: Bearer $TOKEN" \
  -d "status=stays here" \
  -d "local_only=true"
# markdown post
curl -X POST https://{domain}/api/v1/statuses \
  -H "Authorization: Bearer $TOKEN" \
  -d "content_type=text/markdown" \
  --data-urlencode $'status=# title\n\n```python\nprint("hi")\n```'

source code

The code is public, under the same AGPL-3.0 license as Mastodon. Each version is a branch with the bolha commits applied on top of the upstream tag, so you can read exactly what changes.

docker images

The images live in a public registry, no login needed. There are two per version, as in upstream Mastodon: web (also used by sidekiq) and streaming. Builds are linux/amd64 only. The registry keeps the version in production; older builds are pruned over time. To run an earlier version, build it from the bolha-X.Y.Z branch of the repository.

# pull the current version
docker pull registry.gutocarvalho.net/images/mastodon:v4.7.5-web-bolha-tangerine-prod-17
docker pull registry.gutocarvalho.net/images/mastodon:v4.7.5-streaming-prod-1
VersionWeb imageStreaming image
4.7.5 currentv4.7.5-web-bolha-tangerine-prod-17v4.7.5-streaming-prod-1

See every tag in the registry →

docker compose

Start from the upstream Mastodon docker-compose.yml and change only the three image lines. Everything else (database, Redis, .env.production, volumes) stays the same, and no new environment variable is needed.

  1. Back up your database first.

  2. Swap the images in docker-compose.yml:

    services:
      web:
        image: registry.gutocarvalho.net/images/mastodon:v4.7.5-web-bolha-tangerine-prod-17
      sidekiq:
        image: registry.gutocarvalho.net/images/mastodon:v4.7.5-web-bolha-tangerine-prod-17
      streaming:
        image: registry.gutocarvalho.net/images/mastodon:v4.7.5-streaming-prod-1
  3. Pull, run the migrations and start:

    docker compose pull
    docker compose run --rm web bundle exec rails db:migrate
    docker compose up -d
  4. Check the version and the limits:

    curl -s https://{domain}/api/v2/instance | jq '.version, .configuration.statuses'
Before you switch
  • Use the image for the same Mastodon version you already run, or follow the upstream upgrade notes for the target version first.
  • The migrations only add four columns and one index. On a table with 41 million posts, the index took about 100 seconds.
  • Local-only posts also depend on the streaming image of this version: it is what keeps the post away from people who are not logged in. Swap both images together.
  • Self-destructing posts depend on sidekiq processing the default and scheduler queues. If you split queues across processes, check both.
  • To go back to upstream Mastodon, just swap the images back. Long posts and extra metadata stay in the database.

who runs it

Instances running this build:

Does your instance run this build?

Tell @gutocarvalho@bolha.us and we will add you to this list.