Community

Feeds, monitoring & Minecraft

Deduplicate external updates, monitor sites and connect Minecraft securely.

Last updated: 17 July 2026

Feeds and website monitoring

  • RSS/Atom and the official YouTube Atom feed initialize without flooding old posts.
  • GitHub uses the official releases REST API; Twitch uses Helix client credentials.
  • Server admins enter only a channel name, @handle, repository or feed address in the dashboard—never API keys or tokens.
  • Website monitoring stores change/status hashes rather than complete pages.
  • Persistent source IDs prevent duplicate posts after restart; health is visible in the dashboard.

Minecraft status and linking

  1. Add a Java or Bedrock server using a public host and port; private/local targets are rejected.
  2. Configure destination, offline role, debounce and notification cooldown.
  3. A member creates a short-lived /minecraft link code and the plugin confirms it using a signed event.
  • Java uses Server List Ping; Bedrock uses RakNet Unconnected Ping.
  • Failure and recovery thresholds prevent flapping notifications.
  • Members or administrators can remove account links.

Signed plugin API

API key, endpoint and HMAC secret appear once. Every event sends immutable JSON plus timestamp, unique event ID and signature. The action queue only permits SET_MAINTENANCE, ANNOUNCEMENT, GET_PLAYER_COUNT, GET_STATUS, GET_PLAYER_INFO and START_EVENT—never arbitrary console commands.

X-Byterider-Timestamp: 1784300000
X-Byterider-Signature: sha256=<HMAC-SHA256_HEX>

signed = timestamp + '.' + rawBody
body.eventId must be unique per client