Browser push and SMS
Push notifications with the site's own keys and no third-party service, enabling a device, what is sent; SMS through Twilio, BulkSMSBD or any HTTP gateway, phone verification by code, the kinds that go by SMS, the log and test sends.
Notifications reach members four ways: the in-app bell, e-mail, browser push and SMS. Each member chooses per kind under Account -> Notifications (orders, offers, auctions, membership, portfolio, reviews and so on); push and SMS are off until the member switches them on.
1. Browser push
The marketplace sends push notifications itself, with its own VAPID key pair made on first use and stored encrypted: no Firebase, OneSignal or any other service, and nothing leaves the server except the encrypted notification sent to the browser's push service (Google, Mozilla, Apple). The site must run on https (browsers allow push only there; localhost is the exception for testing).
- The member: Account -> Notifications -> Browser notifications -> Enable on this device. The browser asks for permission, the service worker at
/push-sw.jsregisters, and the device appears in the list (label from the browser, added, last sent); Remove or Send me a test are there too. Up to 10 devices per member (setting). - What is sent: the title, a short text and the link of the notification, encrypted for that browser (RFC 8291, aes128gcm) and signed for the push service (a VAPID token with the site contact). A browser that unsubscribed answers 404 / 410 and is dropped; one that fails five times is dropped too.
- Staff: Developers -> SMS & Push shows subscriptions, members with push, sent and failed in 24 hours, a test push to a member, and the push log. Settings -> Push & SMS: push on / off, the contact address sent to push services, the notification icon, devices per member.
push_problem()on that page explains when push cannot work (no openssl, no https).
2. SMS
SMS goes through a provider plugin switched on under Plugins (category Notifications):
| Plugin | Needs |
|---|---|
| Twilio SMS | account SID, auth token (stored encrypted), a Twilio number or a Messaging Service SID |
| BulkSMSBD | the API key and an approved sender ID; Bangladeshi numbers (+880) only |
| HTTP SMS gateway | any provider with an HTTP API: the request address with {to} {text} {from} {key}, GET / POST form / POST JSON, extra headers, the word the provider answers on success, the field that holds the message id |
Then Settings -> Push & SMS: SMS on, the provider code (or leave empty when one plugin is on), the kinds that may go by SMS (default security, order, auction, offer), texts per member per day, verified numbers only, one account per number, whether the link goes into the text.
- The member verifies their mobile number under Account -> Notifications -> Text messages: the number in international form (a local Bangladeshi number is completed to +880), a six-digit code by SMS, good for ten minutes, three codes per quarter hour, five tries per code. Only a verified number receives texts (unless the owner allows unverified ones). Then the SMS column in the preferences table.
- Staff: Developers -> SMS & Push: the provider and whether it is ready, sent / failed in 24 hours and 30 days, verified numbers, a test send to any number, and the log (date, member, number, kind, provider, status, provider reference or error, the text). Every text the marketplace sends is in that log; API keys never are.
- Texts are short: the site name, the notification title and, when allowed, the link; long ones are cut at 320 characters.