Notifications
The platform delivers notifications in real time via WebSocket and by email.
Notification Types
| Event | Who receives it |
|---|---|
| Reply to a comment | Original comment author |
@username mention | Mentioned user |
| Reaction on a post | Post author |
| Reaction on a comment | Comment author |
| New post from followed author/community | Followers with notifications enabled |
| Comment on a post with notification subscription | Post subscribers |
| New follower | Followed user |
| Private message | Message recipient |
| Post unpublished | Post subscribers |
| Subscription payment succeeded / canceled | User with an active subscription |
Author or Community Notification Subscription
In addition to feed follows (POST /follows/{user}), users can enable push notifications for new publications:
- Subscribe to notifications:
POST /notifications(passes author or community) - Unsubscribe from notifications:
DELETE /notifications
Real-Time Delivery
Notifications are delivered via Laravel Reverb — a WebSocket server built into the platform stack.
When a notification arrives, the bell icon in the header updates without page reload. Clicking it opens the notification list.
Reverb is configured via REVERB_* variables in .env.
Email Notifications
Notifications can be duplicated by email — if the user has enabled the corresponding setting.
For email notifications to work, SMTP must be configured — see Email Configuration.
User Settings
Users manage notifications in Settings → Notifications (/settings):
- Enable / disable notifications by type
- Email notifications: enable / disable
Settings are stored in the user_notification_settings table.
Update settings: POST /settings/notification
Notification Management
| Action | Route |
|---|---|
| Get list | GET /notifications |
| Subscribe to author/community notifications | POST /notifications |
| Unsubscribe from notifications | DELETE /notifications |
| Mark all as read | POST /notifications/readAll |
| Mark all as seen | POST /notifications/sawAll |