Manual freshness, verified authority

One command language. Two platform-native bots.

Open Community checks who can manage the Discord server or Telegram group before it accepts setup, bumps, or reminders. The bot records a freshness event; it does not sell trust, reviews, verification, or organic position.

DiscordAdd OpenCommunityView Channels · Send Messages · slash commands TelegramOpen @melloopencommunitybotAdd to a group, then grant the access needed for live admin checks.

Command directory

The same workflow wherever your community lives.

Discord uses guild-only slash commands. Telegram accepts matching group commands. For a channel, message the bot /setup listing-slug @channel, then /bump @channel. Privileged actions recheck platform authority when they run.

/setup listing-slugConnect this server or group to its Open Community profile.

/bumpSend one manual freshness event when the two-hour cooldown is clear.

/pageOpen the connected public profile.

/statusCheck eligibility, connection state, and cooldown.

/reminder on|offChoose whether the bot reminds the chat when freshness is available.

/inviteOpen secure account and installation links.

/helpShow the command guide inside Discord or Telegram.

Permission crosswalk

Enough access to prove authority. Nothing broader.

Discord user check: Manage Server or Administrator on that specific server.
Discord bot grant: View Channels and Send Messages. Administrator is never requested.
Telegram user check: Owner, or administrator with chat-management capability.
Content boundary: Discord Message Content is disabled. Ordinary Telegram messages are ignored.

Freshness without a popularity shortcut

A bump says “we are here,” not “we are best.”

Every accepted bump is manual, destination-scoped, append-only, and held to a rolling two-hour cooldown. Search relevance, listing quality, trust, satisfaction, and current evidence remain separate inputs.