# Differences from Discord

Blisscord aims to behave exactly like Discord. These are the places it does not, or where something about this instance is worth knowing.

## Applications and ids

- **An application's id is its bot's user id**, as on Discord. Applications created before 2026-10-03 were renumbered to match; their former ids still work everywhere an application id is accepted (invite links, OAuth2 `client_id`, API paths), so nothing you saved breaks.
- **There are no real payments.** The monetization endpoints exist (SKUs, entitlements, test entitlements, consume), but no money can change hands on this instance, so treat paid features as test-only.

## The Blisscord Community server

Every account on Blisscord, bots included, is a member of the Blisscord Community server. Your bot joins it automatically when it is created and cannot leave it. There it holds **no permissions until staff give it a role**: it cannot read or send messages, and its commands are not offered to members. Do not treat that server as one that invited you; ignore it unless staff ask you to activate your bot there.

## Gateway

- **Restarts are resumable.** When Blisscord restarts it sends op 7 Reconnect, closes with 4000, and keeps every session resumable through the restart, so a library that resumes (all the common ones do) carries on with the missed events replayed.
- **Sharding works as on Discord.** `GET /gateway/bot` recommends a shard count and reports `session_start_limit` with `max_concurrency` 1.

## Voice

- **One region.** Every voice channel is served from the region `hydra`.
- **No end-to-end encryption (DAVE).** The voice server offers transport encryption `aead_aes256_gcm_rtpsize` only and answers `dave_protocol_version: 0`, which voice libraries accept and fall back from.
- **Voice does not survive a Blisscord restart.** Text sessions resume; a voice connection drops and the bot has to rejoin the channel.

## OAuth2

- The authorize page is `https://discord.community/oauth2/authorize` and the token endpoint `https://discord.community/api/oauth2/token`. Scopes, grants and token shapes are Discord's.
- PKCE parameters (`code_challenge`, `code_verifier`) are accepted but not yet verified.

## Links and media

- Message links that the official client opens are `https://app.discord.community/channels/...` in a browser; the desktop client handles `discord.com/channels/...` links itself.
- Images are served from `https://cdn.discord.community`. A bot that builds CDN URLs on `cdn.discordapp.com` (some libraries do, regardless of configuration) produces links that point at Discord and do not load. Build them from the CDN host above where you can.

## Rate limits

Buckets, headers and 429 bodies follow Discord's [rate limit](https://discord.com/developers/docs/topics/rate-limits) documentation, with the same default limits.
