221 Commits

Author SHA1 Message Date
Enno Gelhaus
450f0b4486
fix(sentry): reduce tracesSampleRate to 0.1 for better performance 2026-09-21 06:35:36 +02:00
Nevo David
f5d83b19f6 fix(clipping): close the clip and draft creation races from review
- createClips takes the row of the clipping before looking for clips, so a
  timed out attempt and its retry can no longer both store a set
- a clip is claimed (draftedAt off null) before its draft is created and
  released when creation fails, so a retry cannot draft it twice
- urls are stripped from the logged processor failure
- Turkish billing label reads correctly after the number

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-09-19 14:22:48 +07:00
Nevo David
9aad99cde1 feat(clipping): YouTube video clipping workflow with REST, MCP tools and widget
Turns a YouTube video into captioned vertical clips that land in the media
library and as draft posts. Adds the Clipping / ClippingClip models, the
clipping_minutes credit type, clippingWorkflow + per-clip child workflows,
the /clipping REST routes, the MCP clipping tools and the ui://postiz/clipping
status widget.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-09-19 13:58:02 +07:00
Nevo David
6fad9852b3 Merge remote-tracking branch 'origin/main' 2026-09-16 16:12:23 +07:00
Nevo David
e2d5b9c592 feat: runpod 2026-09-16 16:12:07 +07:00
Enno Gelhaus
19f095f338
fix(sentry): lower profiling even further 2026-09-16 08:10:54 +02:00
Gilad Resisi
73f5e2d1f3 fix(sentry): sample traces and session replays to stay under quota
Backend traces were sent at 100% (about 77M spans/day) and every
browser session was recorded. Sample /public/v1/analytics/* at 1% and
all other backend traces at 20%, frontend traces at 20% and session
replays at 40%. Error events and error-session replays stay at 100%.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-15 20:01:30 +07:00
Gilad Resisi
8ce68f1a47 fix(farcaster): show the approval QR in a modal instead of a blank tab
After the managed-signer migration, clicking Farcaster on the login and
signup pages opened a new tab to the approval link, which only redirects
to the farcaster:// scheme and stays blank on desktop, while the QR was
squeezed into the narrow provider button slot.

The approval view now opens straight in a modal on the login and signup
pages and replaces the intermediate button step in the add/reconnect
channel modal. No tab opens; a Copy Farcaster link button replaces the
Open in Farcaster link. The auth layout mounts the shared modal manager
and the toaster, so errors on those pages are visible. A response
without an approval link (for example the rate limit) now shows the
failure toaster instead of leaving the modal empty, and the signer
creation limit is raised from 10 to 30 per hour per address.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01R8gvBNgPqqayC9zGPB5R5a
2026-09-15 12:55:55 +07:00
Gilad Resisi
2c2f788e12 feat(farcaster): migrate from SIWN to Neynar managed signers, fix login state
Neynar retired Sign In With Neynar, so the hosted popup used for Farcaster
login and channel connect no longer completes. Replace it with Neynar managed
signers: the backend creates a signer, signs the EIP-712 signed key request
with the app custody mnemonic (viem), registers it with Neynar and renders the
approval deep link as a QR (qrcode) since the link is a bare 302 to the
farcaster:// scheme. The frontend polls the new public /auth/farcaster/signer
routes and builds the same base64 blob the popup produced, so authenticate(),
the auth provider, the stored token format and existing users/channels are
unchanged. @neynar/react is removed.

Also thread the oauth_state nonce through the Farcaster login button: since
the Apple login change, checkExists rejects logins without a matching state
cookie, which broke Farcaster login independently of the SIWN retirement.

New env vars: NEYNAR_APP_FID, NEYNAR_APP_MNEMONIC, NEYNAR_SPONSOR_SIGNERS.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01R8gvBNgPqqayC9zGPB5R5a
2026-09-14 20:47:22 +07:00
Nevo David
3cbe20b86b feat: wallet rejection 2026-09-12 15:00:18 +07:00
Nevo David
c9382d983d feat: other agents 2026-09-03 15:27:53 +07:00
Nevo David
4f296fc090 feat: better onboarding 2026-09-03 14:49:58 +07:00
Nevo David
9ddbd73cf1 Merge remote-tracking branch 'origin/main' 2026-08-15 14:27:29 +07:00
Nevo David
14c3a2f83d feat: apple login 2026-08-15 14:27:15 +07:00
Enno Gelhaus
2de6dd763d
feat(sentry): adjust replay options 2026-08-14 20:22:25 +02:00
Gilad Resisi
ff3019b495 fix(sentry): send the account email with bug reports instead of asking for it
The "Report a bug" widget asked the reporter to type their email. It was
prefilled from the Sentry scope user but stayed editable and optional, so a
report could arrive with a typo'd, someone else's, or an empty email — and we
could not tie it back to an account.

Setting showEmail: false does not drop the field: the SDK renders it as a
hidden input whose value is the scope user's email (the one we already set from
GET /user/self), and that hidden value is what the form submits. Nothing on our
side has to read or attach the value.

The Name field is left as-is. No user in the production DB has name/lastName —
we never collect it at signup, never pull it from the OAuth profile, and there
is no UI to set it — so hiding it would submit an empty name forever. Keeping
the input lets the reporter tell us who they are; it has no prefill for the
same reason, and an untouched field is no worse than today.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-10 18:25:02 +07:00
Nevo David
7c566dadb3
Merge pull request #1841 from gitroomhq/fix/republish-guard
fix: require explicit opt-in to republish a published post
2026-08-06 04:29:01 +00:00
Gilad Resisi
b631036442 fix: require explicit opt-in to republish a published post
A schedule-type save targeting a PUBLISHED post silently requeues it:
state back to QUEUE, releaseURL/releaseId nulled, workflow restarted -
and since the workflow's initial sleep is max(0, publishDate - now), a
save that carries (or leaves) a past date publishes again within
seconds. When editing an existing published post the date field holds
its old (past) date, so confirming a reschedule without touching the
date is an accidental instant republish. The existing protection
(2813ed01) is a frontend-only modal: it doesn't cover the public API or
MCP agents at all, and even in the dashboard it never states that
republishing can mean publishing right now.

- changeDate now defaults action to 'update': clients that don't send an
  action can no longer requeue a post by accident
- schedule/now saves (createPost) and action 'schedule' (changeDate)
  targeting a PUBLISHED post are rejected with a 400 explaining what
  happened and how to proceed, unless the new optional republish flag is
  sent - the error body is the confirmation dialog for automation
- the dashboard modals send republish: true on explicit confirmation and
  now state the consequence (channel, date, recurring note)
- new modal strings added to the locale files via lingo.dev

No behavior change for DRAFT/QUEUE posts.

Testing: 16 service-layer assertions against a stubbed repository + local
Temporal (400 + message for schedule/now saves, rejection before any
write, republish passthrough requeues and restarts the workflow, update
stays date-only, QUEUE posts unaffected), plus a live end-to-end run in
the dashboard: modal confirm -> republish: true -> requeue -> real
publish to an Instagram channel.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-04 19:23:23 +07:00
Nevo David
0f5b0b1f3c
Merge pull request #1800 from gitroomhq/feat/sentry-user-context
feat(sentry): attach user id, org id and Stripe customer id to all telemetry
2026-08-04 11:50:10 +00:00
Gilad Resisi
45aecfbe98 fix(sentry): clear organization tag when frontend user logs out
Sentry.setUser(null) does not remove custom tags; without this, events
fired after logout but before reload kept the previous org's tag.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-04 13:00:47 +07:00
Gilad Resisi
8c4ed8e288 feat(sentry): include user email in Sentry user context
Per review on #1800: send the acting user's email alongside the id, on both
backend (auth middleware paths) and frontend (post-login setSentryUser).
Public-API events are unchanged (no user there). Also gives Sentry a proper
avatar/display identity instead of the "?" placeholder.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-04 12:56:33 +07:00
Gilad Resisi
dbb331e46d feat(billing): translations for the admin apply-coupon modal
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-28 13:23:06 +07:00
Gilad Resisi
ad7c879685 feat(sentry): attach user id, org id and Stripe customer id to all telemetry
Sentry events had zero user context, so issues/traces/replays could not be
tied to a customer. Enrich the per-request (backend) and per-tab (frontend)
Sentry scope with the acting identity, so every element emitted afterwards -
errors, spans, profiles, metrics, replays - carries it automatically:

- New setSentryUserContext helper in the shared server sentry lib: sets
  Sentry user (id only), organization.id tag, and stripe.customer_id tag -
  the latter only when Organization.paymentId starts with "cus_" (legacy
  orgs hold non-Stripe values there). Wrapped in try/catch so telemetry can
  never break a request; a no-op when Sentry is not initialized (no DSN).
- auth.middleware calls it once req.user/req.org settle, in both the normal
  and impersonation branches (the impersonated user is the acting identity).
- public.auth.middleware calls it with org only (no user exists there) -
  setUser(null) also guarantees no stale user attaches.
- Frontend: setSentryUser helper next to initializeSentryClient; called from
  a useEffect on the /user/self SWR result in the layout, clearing the user
  when absent. IDs only - no email/name; paymentId is deliberately not
  exposed to the frontend, backend events carry the Stripe id.

Deliberately NOT enriched (no identity exists at emission time):
- Orchestrator/Temporal activities - no HTTP context and no generic hook
  without changing workflow/activity signatures, which is forbidden;
  publish-time failures therefore still have no org tag.
- Unauthenticated backend routes (login/register/OAuth callbacks), webhook
  endpoints (signature-authed, no user), errors thrown inside the auth
  middleware itself, and startup/background errors.
- Frontend pre-login pages, errors before /user/self resolves, and Next.js
  server/edge events.

Verified e2e: backend events captured locally (envelope capture server)
confirmed user.id + organization.id + stripe.customer_id on authenticated
errors, org-only on public-API errors, no stripe tag for legacy paymentId,
and no cross-request leakage (per-request isolation scopes). Real Sentry
issues then verified in the cloud project for both backend (user, org and
stripe tags) and frontend (user + org, replay attributed to the user id).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-28 12:25:32 +07:00
Nevo David
fd4a816fde
Merge pull request #1677 from gitroomhq/fix/shortlink-dialog-cancel-label
fix(launch): use a clear cancel label in the shortlink confirmation dialog
2026-07-23 10:38:46 +07:00
Gilad Resisi
9d0919f851 feat: block subscribing when a same-email account is already subscribed
A person can create two accounts with the same email (LOCAL + OAuth)
because User uniqueness is @@unique([email, providerName]). Guard the
subscribe path: if another account with the same email owns an org with
an active subscription (deletedAt: null), block the subscribe flow and
tell them to sign in to that account instead. Excludes the current user
by id, so renewing your own plan is unaffected.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-20 17:02:12 +07:00
Gilad Resisi
75d9eef05d fix(tiktok): stop offering settings TikTok silently ignores
A production user ticked "Video made with AI" on a TikTok post using the
UPLOAD posting method and the label never appeared: with
content_posting_method=UPLOAD, TikTok's inbox/upload endpoints accept
nothing but the title, so every other setting is silently discarded.
The settings panel still offered all of them, so there was no way to
know the flag would be dropped.

- Frontend: hide all DIRECT_POST-only settings when UPLOAD is selected
  (fields stay mounted so their values survive the switch and the DTO
  stays valid), and explain in the helper text above the method
  selector that the additional settings only apply when posting
  directly. Regroup the video-only settings (Allow Duet, Allow Stitch,
  Video made with AI) under a "Video features" header and move "Allow
  Comments" down next to the settings that apply to both videos and
  photos.
- DTO: document each field's DIRECT_POST-only / video-only / photo-only
  constraint via @JSONSchema descriptions, surfaced to the agent tools
  and the public integration-settings endpoint. Validation unchanged.
- Provider @Rules: tell the agent that UPLOAD drops every setting
  except the title and that duet/stitch/video_made_with_ai are
  video-only, so it stops promising settings that won't apply.
- Locales: relabel Duet/Stitch/Comments to "Allow ...", add the new
  header key, extend the upload helper text (lingo.dev run included).

No change to what is sent to TikTok.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-15 12:11:48 +07:00
Gilad Resisi
ec91d106cc fix(i18n): add missing no_original_urls key to ka_ge locale
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-14 15:29:03 +07:00
Gilad Resisi
1dc655dbe0 fix(launch): use a clear cancel label in the shortlink confirmation dialog
The shortlink question dialog used the generic "No, cancel!" cancel
label, which reads as aborting the whole post instead of declining
shortlinks. Pass a custom cancel label ("No, original URLs") via the
existing deleteDialog cancelButton param.

Adds the no_original_urls key to the English source, translates it to
all 14 lingo.dev locales, and hand-fixes 8 machine translations that
rendered the label as "there are no original URLs" instead of a choice.

Manually tested locally: the dialog now shows "Yes, shortlink it!" /
"No, original URLs", and both choices schedule the post with/without
shortlinked URLs accordingly.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-05 18:43:02 +07:00
Gilad Resisi
7367309717 fix(plugs): translate renamed empty-state key across locales
Follow-up to #1666: run lingo.dev to translate
you_have_to_add_x_linkedin_page_threads_or_bluesky in all 14 locales,
replacing the stale you_have_to_add_x_or_linkedin_or_threads entries.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-02 11:52:27 +07:00
Gilad Resisi
1fcbe3327c fix(plugs): list actual plug-supported channels in empty state
The plugs page empty state said to add 'X or LinkedIn or Threads', but
plugs only exist for LinkedIn Page (not personal LinkedIn), and Bluesky
was missing. Renamed the translation key so non-English locales fall
back to the corrected English text instead of stale translations.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-02 11:21:14 +07:00
Gilad Resisi
daffe5b4ec feat: add reusable MultiSelect form primitive
Add a controlled multi-select (scrollable checkbox list) to the shared
react form components, alongside the existing Select. It is purely
presentational - options in, full selected array out via onChange - so
the caller owns selection state (pair it with react-hook-form setValue).
Matches Select's conventions: TranslatedLabel, useFormContext error
display, and the same newBgColorInner / newTableBorder design tokens.

The app had no general multi-select primitive (only single Select and
the npm react-tag-autocomplete based *.tags.tsx inputs), so this fills
that gap for any provider/form that needs to pick several known options.

Testing: exercised end-to-end in the next commit in this PR, which wires
this primitive into the WordPress categories/tags selectors. Selecting
multiple options there persisted correctly and posted the chosen term
IDs to WordPress.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-30 13:51:12 +07:00
Nevo David
ebe3a6b666 feat: chatbase 2026-06-12 12:48:50 +07:00
Nevo David
6173b1679a feat: groups endpoint 2026-06-02 15:35:18 +07:00
Nevo David
17fa64726c feat: tracking 2026-05-14 18:10:01 +07:00
Santosh Bhandari
80b6bdcabe feat: hasExtension helper for media type detection 2026-05-12 16:23:11 +05:45
Enno Gelhaus
1145e51ea6
feat: sentry replay 2026-04-13 07:10:56 +02:00
Nevo David
92b82837e9 feat: remove Image 2026-03-25 16:51:13 +07:00
Nevo David
a8c8428ae2 feat: fix direction 2026-03-25 16:08:30 +07:00
Nevo David
f675dd5179 feat: change dir 2026-03-25 15:57:46 +07:00
Nevo David
358bf62804 feat: layout 2026-03-25 15:17:35 +07:00
Nevo David
072c6bac4a feat: fix language, dont cache cookies 2026-03-25 14:52:49 +07:00
Nevo David
c7a88b98bc feat: language switch 2026-03-25 14:42:00 +07:00
Nevo David
3bc3d004fa feat: language switch 2026-03-25 14:24:26 +07:00
Nevo David
b71297db57 feat: upgrade nextjs to the latest version 2026-03-25 13:55:45 +07:00
Nevo David
6c39e810db feat: seperate mcp url 2026-02-28 16:53:03 +07:00
Nevo David
e3c3854840 feat: platforms with a chrome extension 2026-02-08 20:53:28 +07:00
Nevo David
7e1e5f36e3 feat: kick 2026-01-24 15:00:42 +07:00
Nevo David
43ced2e7b6 feat: onboarding 2026-01-23 16:37:28 +07:00
Nevo David
99889d59e2 fix: autoplay video 2026-01-19 17:31:14 +07:00
Nevo David
47e7c843c9 feat: better biling 2026-01-17 12:03:28 +07:00