No description
0db9e0706d
* feat: visible Terms/Privacy links on the auth screens Social-platform app reviews (TikTok explicitly) require both links to be reachable from the public site without logging in or opening a menu. * Cover the legal links with tests and tidy the layout The links are a compliance artifact an outside reviewer checks, but nothing asserted they exist. A refactor of this layout could drop the footer silently and the next platform submission would fail the same check that prompted the PR. A feature test asserts the shared prop reaches both guest screens and carries whatever the install configured, and a browser test asserts the two links actually render to a logged-out visitor. Declares legal on SharedData, so the props read through the interface rather than its index signature and the inline cast goes away. Adds rel="noopener noreferrer" to both anchors, matching every other target="_blank" in the codebase, and orders the imports the way eslint expects so the file lands clean rather than relying on --fix in CI. Drops the comment explaining why the links are there: that rationale belongs in the commit and the pull request, and the sibling comments in this file describe markup rather than justify decisions. * Reuse the legal sentence the register screen already had The register screen has shown "By continuing, you agree to our Terms of Service and Privacy Policy" in production for a long time, translated into all sixteen locales. Only the login screen was missing it, and the two URLs were hardcoded inside the translated string, so a self-hosted install could not point them at its own documents. So this keeps what already worked and changes only those two things. The markup moves into one component, which the login screen now renders as well. The translated sentence keeps its wording and its link labels; only the href becomes an i18n placeholder that the component fills from config. That is one line per locale, and no new translation keys. Reverting the footer out of AuthSplitLayout also stops the links from appearing on the workspace index and create screens, which reach that layout too and are seen after login rather than before it. The sentence no longer hides on a self-hosted install. It was hidden because it named TryPost's own documents; now that the URLs are configuration, an install that sets them wants it shown. A feature test covers the shared prop on both screens and the placeholder in every locale; a browser test covers the rendered sentence, since the links are a compliance artifact an outside reviewer checks and nothing guarded them. * Let the browser assertions do their own waiting The test hand-rolled a polling loop in injected JavaScript to wait for the element to mount, because the project notes say browser assertions do not wait for SPA paint. They do. visit() returns a PendingAwaitablePage backed by AwaitableWebpage, whose __call wraps every method in Execution::waitForExpectation and retries until the Playwright timeout, which defaults to five seconds. The plugin even deprecates waitForText in favour of assertSee for this reason. The loop was re-implementing the retry that already surrounded each call, less well and with a helper whose name has to be unique across the whole suite because these are global functions. Halves the file and drops the injected script. assertSeeLink also says more than the old check did: it asserts the labels are links, not just text that happens to appear. --------- Co-authored-by: Paulo Castellano <paulo@castellanos.llc> |
||
|---|---|---|
| .agents/skills | ||
| .claude | ||
| .codex | ||
| .cursor | ||
| .github | ||
| app | ||
| bootstrap | ||
| config | ||
| database | ||
| docker | ||
| lang | ||
| maizzle | ||
| public | ||
| releases | ||
| resources | ||
| routes | ||
| storage | ||
| stubs | ||
| tests | ||
| .dockerignore | ||
| .editorconfig | ||
| .env.ci | ||
| .env.example | ||
| .env.testing | ||
| .gitattributes | ||
| .gitignore | ||
| .mcp.json | ||
| .prettierignore | ||
| .prettierrc | ||
| AGENTS.md | ||
| artisan | ||
| boost.json | ||
| Caddyfile | ||
| CLAUDE.md | ||
| components.json | ||
| compose.override.yaml.example | ||
| compose.prod.yaml | ||
| compose.yaml | ||
| composer.json | ||
| composer.lock | ||
| eslint.config.js | ||
| GEMINI.md | ||
| LICENSE.md | ||
| package-lock.json | ||
| package.json | ||
| phpunit.xml | ||
| pint.json | ||
| README.md | ||
| tsconfig.json | ||
| vite.config.ts | ||
Run your whole social presence from one calendar
An open-source social media scheduler with an AI copilot, native publishing to 12 networks,
and an MCP server so your AI assistant can post for you. Self-host it, or skip the setup on cloud.
Try on Cloud • Documentation • Community
What you get
| 📅 One calendar, every network | Plan a month at a glance, drag any post to a new slot, and publish natively to 12 platforms. No redirects, no "finish in the mobile app." |
| ✨ An AI copilot that knows your brand | Captions, hooks, full drafts, and multi-slide carousels in your tone, voice, and colors. It reads your brand profile on every generation. |
| 🤖 Built for AI agents | A first-class MCP server and REST API. Claude, Cursor, ChatGPT, or your own scripts can draft, schedule, and publish for you. |
| ⚙️ Automations that run themselves | A visual workflow builder: triggers, conditions, RSS, webhooks, and AI generation, all server-side. Set it once, let it post. |
| 🗂️ Made for many clients | Workspaces, roles, and approval flows so an agency or freelancer can run a roster of brands without the spreadsheets. |
Features
| Visual calendar | Month, week, and day views. Drag and drop to reschedule across networks. |
| Multi-platform composer | Write once, then tailor the preview per network in parallel. |
| AI generate & review | Draft from a prompt, get inline feedback before you publish. |
| AI carousel builder | Prompt to a multi-slide carousel with images, on-brand. |
| Brand profile | Tone, voice, language, and colors applied to every AI call. |
| Automations | Schedule / RSS triggers, conditions, publish steps, and webhooks. |
| Asset library | Reusable workspace media, plus Unsplash and Giphy search built in. |
| Signatures & labels | Reusable hashtag and CTA blocks, color-coded post tags. |
| Team collaboration | Owner / Admin / Member roles, comments with @mentions on drafts. |
| Workspaces | Isolate each brand, client, or project in its own space. |
| REST API + MCP | Full programmatic control; AI assistants integrate natively. |
| Native analytics | Per-account reach and engagement across every connected platform. |
| Multi-language | English, Ukrainian, Spanish, Portuguese, French, German, Italian, Dutch, Polish, Greek, Japanese, Korean, Chinese, Russian, Turkish, and Arabic. |
Supported platforms
Posts publish natively through each platform's official API.
 |
 |
 |
 X (Twitter) |
 TikTok |
 YouTube |
 |
 Threads |
 Bluesky |
 Mastodon |
 Telegram |
 Discord |
Get started
| ☁️ Cloud | The fastest way in. We host, update, and scale it for you. Start at trypost.it → |
| 🛠️ Self-host | Free forever, your servers, your data. Installation guide → |
| 🤖 Drive it with AI | Connect Claude, Cursor, or ChatGPT over MCP. MCP setup → |
Own your stack
TryPost is open source on purpose. Self-host it and your posts, drafts, and metrics stay on your infrastructure, under a license that is yours to keep. No seat tax, no feature gates, no vendor deciding when to lock you out. Read every line, fork it, and ship it. When you would rather not run servers, the same product is one click away on cloud.
Contributing
Contributions of any size are welcome. Pick an issue, say hi in Discussions, or open a PR with what you would like to see.
Short on time? A star is the most valuable thing you can give. It helps more people find the project.
License
GNU Affero General Public License v3.0. Use, modify, fork, self-host, and redistribute, including commercially. If you run a modified version as a network service, make your changes available to its users (AGPL §13).
Built in the open. Star TryPost on GitHub and tell a friend.