Beta

Sockethub 5.0.0-beta.2 is the current active-use release. See the changelog.

Sockethub

News

Sockethub 5.0.0-beta.2 adds email, Messenger, and Instagram

·Nick Jennings ·1 min read

Sockethub 5.0.0-beta.2 is out, and it brings three new platforms:

npm install -g sockethub@next

The container image follows at ghcr.io/sockethub/sockethub:next.

Email

@sockethub/platform-email receives mail over IMAP and sends it over SMTP. Your mail server stays the message store: Sockethub keeps no mailbox database and never changes read flags, moves messages, or deletes mail.

  • fetch pages through one or more folders, filtered by sender and recipient, with per-folder cursors so your app can resume where it left off.
  • watch follows a folder with IMAP IDLE and pushes new messages to the browser as post activities.
  • send submits a message over SMTP and reports which recipients the server accepted or rejected.

Credentials take a password or an access token for each of IMAP and SMTP. Connections require TLS or STARTTLS. See the email section of the platforms page for the envelopes.

Messenger and Instagram

@sockethub/platform-messenger and @sockethub/platform-instagram send text messages through Meta's Messenger and Instagram APIs. Both are stateless: store a token, then send. No connect step and no webhook hosting. Sockethub sends as a Facebook Page or an Instagram professional account, not as a personal profile, and your app brings the recipient's scoped ID from its own incoming-message integration.

These are outgoing-only. Incoming messages, delivery receipts, attachments, and OAuth onboarding stay with your application and Meta's review process.

Also in beta.2

  • The metadata platform now surfaces a schema.org Event embedded as JSON-LD, so link previews for Luma, Meetup, and Eventbrite pages carry the event name, start and end, location, and status.
  • CalDAV accepts and round-trips STATUS on events, and calendar and address book discovery is cached across requests.
  • XMPP roster activities are schema-valid, and inbound subscription requests now arrive as request-friend.
  • IRC refuses to connect to private and loopback addresses, and incoming NOTICE lines are attributed to their sender.
  • The server rate-limits persistent platform starts per client IP.

The full changelog has every fix. The documentation on this site tracks beta.2: get started and platforms.