Social current limitations
What the current Openfront Social source does not do.
This page describes the current source. It is not a security review or a privacy-compliance assessment. Openfront Social does not provide certification under GDPR, CCPA, or any other privacy law; the privacy request queue records requests and human decisions only.
No external publishing
External destinations are consent records. There is no OAuth flow, stored provider token, adapter, job worker, or dispatcher. Every external request ends as not_configured with a failed zero-attempt job. Share links open public intent pages in the visitor's own browser session.
No community features
There are no comments, likes, follows, reposts, mentions, notifications, direct messages, or feeds that aggregate several creators. Visitors cannot sign in as readers; accounts exist for creators and people managers only.
No organization tenancy
Ownership is per creator: one user, one site. There is no organization, team, or shared site; a site cannot have several editors. People managers with canManagePeople can see every creator in the directory and act on privacy requests.
One site per creator
PersonalSite.owner is unique. A creator who wants another site needs another account. A site with real (non-sample) publication history cannot be deleted through deleteSite; it can only be hidden, renamed, or edited.
Content and media
- Item bodies are markdown; there is no rich-text block editor, scheduled publishing, or draft sharing link.
- Collection
isFeaturedis stored but unused. - Image uploads require the five S3 variables. Without them, uploads fail.
- Privacy erasure deletes
MediaAssetrows; the current source does not delete the underlying bucket objects.
Privacy
Requests (request_access, request_correction, request_erasure) are events reviewed by a person. Only erasure has an automated "carry out" action. Access is served by the creator's own paged export; correction has no dedicated tool beyond normal editing. There are no deadlines, reminders, or notifications.
AI and MCP
The MCP transport route is disabled and returns 404, so /api/completion has no working tool set. Do not rely on the dashboard AI assistant for studio actions.
Operations
npm run devandnpm run builddo not apply migrations; runnpm run migrateexplicitly (the Railway start command does this).- There is no license file or package license declaration in the repository.
- Sessions are stateless cookies signed with
SESSION_SECRET; rotating it signs everyone out, and there is no server-side session revocation. - Password reset needs SMTP configuration; without it, reset email cannot be delivered.