Blah Features

Account

Email and Blah Number sign-up ¹
Browser sign-up ²
Sign-in by email or Blah Number, using email codes or TOTP
QR sign-in from an existing device
Login email setup and changes
New-login notices and confirmation
Client-app verification notices ³
Two-step verification password and recovery email
Delayed password reset ⁴

Sessions and account lifecycle

Active sessions, session termination and automatic expiry
Connected website list and access revocation
Account deletion, including automatic deletion after inactivity
Premium tier ⁵

Profile and contacts

Privacy

Chats

Private chats and chat list

Groups and channels

Group-specific features

Anonymous admins and custom member ranks
Anonymous admin actions and silent pin announcements in group history
Posting as an owned channel ¹⁷
Forum topics
Group photo history
Members-only sending
Admin log ¹⁸
Seen By / read receipts for recent messages
Basic groups ¹⁹

Channel-specific features

Communities

Communities linking channels, groups and bots ²¹
Visible or hidden linked peers
Collaborative linking or administrator approval requests
Community administrators, title, description, picture and deletion
Community-scoped bans ²²
Collapse a community in the chat list ²³
Search within a community ²⁴

Messaging

Content

Text formatting, links, mentions, hashtags, cashtags, phone numbers, bank card numbers and bot commands
Photos, videos, audio, voice messages and documents
Albums and custom emoji in text
Reactions, polls and quizzes in private chats, groups and channels
Checklists in private chats and groups
Typing and recording indicators

Actions and search

Replies, editing and forwarding
Delete for self or everyone
In-chat search
Search across chats ²⁴
Hashtag and cashtag search in chats and public channel posts ²⁴
Shared media, files, links, music and voice panels

Drafts, scheduling and import

Stickers and custom emoji

Set installation, archiving, reordering and search
Sticker and custom emoji set creation and editing
Synced static, animated and video stickers render in channel and supergroup messages, including existing imports
The bridge reuses a Telegram pack’s mirror across synced chats and background copying
A sticker of a mirrored pack sent from Blah arrives in Telegram as that pack’s own sticker rather than as a copied file
Mask, Premium sticker, dice and official reaction sets

Bots and applications

Bots

Connected accounts, web and files

No real phone number is required. Blah Numbers are virtual +999 numbers; email sign-up assigns one automatically. ↩
An unregistered email on the control panel’s or an application’s Blah sign-in page starts account creation. Verify the emailed code, choose a name and continue to that site; sign in to a messenger separately. ↩
Unregistered client apps may sign in, but Blah shows an in-app warning. ↩
Without a recovery email, a forgotten password resets after a delay; a signed-in device can cancel the request. ↩
Premium is granted by a Blah administrator, not sold. Until it expires, it raises upload, pinned-chat, public-link and per-message reaction limits and enables personal accent-color changes. ↩
Administrators choose the available palettes and custom-emoji patterns. Changing your own name/message or profile palette requires Premium; changing a chat’s requires permission to edit its info. Groups can color only their profile; channels can color both. Blah does not enforce boost requirements. ↩ ↩² ↩³
Block and unblock users or bots, manage your block list, and prevent private messages, typing, profile-photo and presence access across data centres. Existing chat history and shared groups remain available. ↩
New non-contacts need Premium to reach you; contacts and existing conversations remain reachable. ↩
Each chat list — the main one and the archive — keeps its own pinned order, and a pinned chat keeps its pin when you archive it. The limits depend on your account tier. ↩
Chats you archive leave your main list. An archived chat comes back when you write to it, and when it gets a new message unless you muted it — the privacy settings let you keep unmuted or foldered chats archived instead. You can also have first messages from people who aren’t your contacts arrive archived and muted. ↩
A folder can select chats by kind (contacts, groups, channels, bots), always include or always exclude particular chats, and pin chats within itself. How many folders you can keep, and how many chats one can name, depends on your account tier. ↩
A link can share a folder’s groups and channels with other people. Only chats someone else can join can be shared, and sharing a folder turns it into a plain list of chats. People who import your folder can be offered chats you add to the link later; their copy of the folder is their own. ↩
Appears once an app you granted peer access to shares a chat with you, and holds exactly those chats. The server keeps it current, so its name, its chats and its settings are not yours to change — you can only move it among your own folders. It is absent while no app shares a chat with you. ↩ ↩²
The designated group’s creator and administrators receive deployment root access, including accounts hosted on another data centre. Changes sync automatically; the environment root administrator retains access independently of the group. ↩
Only the group or channel owner can enable it. Forwarding out is refused even for the owner; saving, copying and screenshot restrictions depend on the client. Existing copies are unaffected, and private chats have no such switch. ↩
Only the owner can delete a group or channel, and it disappears for every member at once, including members on another data centre. Its public links are immediately free for someone else to claim. Its history, media and the storage they used are removed in the background shortly afterwards, so a large channel’s storage is released over the following minutes rather than instantly. ↩
An owned channel hosted separately from the destination may be unavailable as a posting identity. ↩ ↩²
Only entries within the server’s recent retention window are available. ↩
Creating a basic group creates a supergroup instead. ↩
Blah deliberately leaves channel posts unpinned in linked discussion groups. ↩
A community groups peers, not messages. Membership comes from its linked chats; a peer can belong to only one community. Older clients may not show communities or their management controls. ↩
A ban removes access to the community and its listings, not membership in its linked chats. ↩
A community shows either as one entry or as the chats inside it, and the choice is yours per community. A community created by an app you signed into starts collapsed for everyone in it — the app is what those chats are — until each member expands it. ↩ ↩²
Cross-chat, community and public-post search can omit groups or channels hosted separately from your account. Open a chat and search there to search its own history. Public channel web pages also search the channel’s own history across data centres. ↩ ↩² ↩³
Imported messages retain their source sender and time. In a group, a sender connected to a Blah account is shown as that account; otherwise only the source attribution is shown, without the importing bot’s identity. Existing imports refresh automatically. Messages dated more than a minute away from the current time arrive silently through history refreshes, without push notifications or new mention alerts. Recent imports arrive live. ↩
Requires a configured bridge and matching chat types. The bridge bot’s private-chat command menu lists /sync, /sync_sticker_set and /status on both services, plus /bind_bot and /unbind_bot on Telegram. Mappings accept usernames or numeric channel IDs, including with two-way backfill. Copies into Telegram are bot posts, not original-user messages, and unsupported content is skipped. Replies in Blah to synced Telegram messages reply to their originals when copied back, including messages synced earlier. In two-way sync, changing a mirrored copy does not rewrite its original. A message the bridge cannot read is skipped rather than stalling the chat, and a sync that stops is reported to whoever set it up and retried on its own, leaving your other syncs running. ↩
Connect your Telegram account in the Blah control panel, create a managed bot through the syncer’s creation link from that account, and add it to the Telegram destination with permission to post. It sends only your Blah messages; other users keep the shared syncer with their names attached. If the syncer did not pick the bot up when you created it, bind it by hand from that Telegram account with /bind_bot @your_bot, or /bind_bot and its token for a bot you have the token of; /bind_bot alone lists the bots already representing you, and /unbind_bot gives one up. Live reactions use your personal bot and follow changes and removals, including on imported Telegram messages. Only your latest standard emoji is copied; custom and paid reactions are excluded. Previously recorded reaction targets are checked again after restart. ↩
Timed and view-once photos, videos, voice notes and video notes in private chats between users. The timer starts when the recipient opens the content. This is separate from chat auto-delete; secret chats are not supported. ↩
@bot replaces BotFather for bot creation and management. ↩
An enabled bot can answer a mention or /command@bot without joining; its reply names who invoked it. Managed guest bots currently work only in chats hosted on the same data centre as the bot. ↩
Existing accounts approve through @blah. Newly created web accounts review the application’s permissions in the browser instead. ↩
A deployment can answer sign-in, sign-up and OAuth at extra domains, each its own OpenID Connect issuer and each able to call an account by its own name. On those domains an account with no Blah app signed in confirms with an emailed or authenticator code in the browser rather than being sent to the app; an account with two-step verification confirms in Blah as usual. ↩
An app owner requests a link and the bot’s owner approves through a message from @bot. The browser returns to the app page after confirmation. Peers owned by that bot remain ordinary chats, visible under the same membership and public-link rules in other clients too. ↩
Calls act as the signed-in account, within its permissions, on peers shared with the app’s linked bot. Newly created peers belong to that account, with the bot added as administrator. Requires the peers scope; does not read or send messages. ↩
Linking proves an external account is yours for import attribution. It neither signs you in to Blah nor starts synchronization by itself. ↩
Only peers with a public username have a public profile page, available at blah.ing/username or username.blah.ing. ↩
Browsers receive visible message and reaction notifications; silent housekeeping notifications remain app-only. ↩
Files above 10 MiB use Telegram’s large-file upload method. Temporary upload buffers and simultaneous uploads are bounded; clients may receive a retryable flood-wait response while uploading. ↩

Blah Features

Account

Sign-up and sign-in

Sessions and account lifecycle

Profile and contacts

Privacy

Chats

Private chats and chat list

Groups and channels

Group-specific features

Channel-specific features

Communities

Messaging

Content

Actions and search

Drafts, scheduling and import

Stickers and custom emoji

Bots and applications

Bots

Sign in with Blah and application API

Connected accounts, web and files

Footnotes