Registro de alterações

Novidades do Subscriby

Cada versão e cada anúncio, da mais recente para a mais antiga. Subscreva o feed para saber da próxima.

Subscrever o feed
Versão 5.0.3

Subscriby 5.0.3

Marketing site

  • One page per payment method under /payments (Stripe, PayPal, Paystack, Razorpay, Skrill, CoinPayments, CeyPay and the connected platform's own in-app payment) and a /payments index that says which methods renew, where each works and how to choose. Whether a method renews a plan, runs in test mode or syncs plans, and how many currencies it settles in, is read from the code the checkout enforces, so the pages can never drift from it. The home page's payment logos and the gateways each creator-type page recommends link to them.
  • Every marketing page has its own share card, drawn on request in the hero's design from the page's headline and subline, so a comparison shared on social media previews as that comparison. The card's lines are measured with the renderer's own font metrics and centred above the footer, with the subline running to four lines when there is room.
  • The comparison hub at /vs and the creator-type hub at /for carry an intro, a six-point checklist and five questions beneath their cards; a new comparison, Tribute, with every rival figure read from the vendor's own pages; the TGMembership comparison follows the rival's rename to BotSubscription, and the old address redirects permanently in every language.
  • A public changelog at /changelog with every release back to the first commit, the product announcements woven in by date, twenty entries a page, an Atom feed at /changelog/feed and a footer link; the changelog and blog listings paginate with Newer and Older pills and round page chips in the site's own language.
  • The 24 comparison and creator-type pages and both hubs carry their title, description, heading, subline and every question and answer in all ten languages, with the platform words filled after translation; the payment-method pages join them.

Blog

  • An Atom feed at /blog/feed carries the twenty newest articles with their banners, announced from every marketing page's head.
  • Nine guides for 2026, one a week from 5 October to 30 November, lead platform-neutral in their titles and addresses and name the platform as the worked example; every article's title and description fit a search snippet, and the blog index says what the blog covers, in ten languages.

Performance

  • The marketing site is served without a session and marked cacheable at the edge for every visitor: the header's sign-in link is decided in the browser from a marker the dashboard sets on login, the locale cookie is written by the browser, and the dashboard's interface scripts no longer load on marketing pages.
  • A phone's home page shows a still of the dashboard preview instead of 2,846 live elements scaled into a thumbnail, with the sidebar pinned as the live preview pins it; the page falls from 9,530 to 3,298 elements and its largest paint from 7.6 to 5.0 seconds in emulation, while a desktop keeps the live preview.
  • Inter is served as a Latin subset (171 KB instead of 344, the italic 189 instead of 379) with the full font kept behind a unicode range for the scripts it carries; the early-hints header names the bundle the page runs and no longer pushes the italic fonts or the dashboard bundle onto marketing pages; the brand mark's paths are drawn once per page. A phone's transfer for the home page falls from 1,755 to 1,215 KB.

Fixes

  • Both Atom feeds answered a server error to every reader in production because of the way the server read their XML declaration; the declaration now comes from the response, and a check refuses any template that could bring the problem back.
  • The logo vanished from the header and footer on phones: the brand mark's symbol was defined inside the dashboard preview's inert template, which a phone never instantiates; every layout now defines it right after its body tag.
  • The hero's connector strip flashed on iPhones as the page scrolled back to the top: the strip rebuilt itself on every resize event, which iOS fires when the address bar shows or hides; it rebuilds only when its width changed.
  • The generated sitemaps are no longer shipped with the code, so a fresh deployment stops serving the pre-cutover files naming the beta host until its first sitemap run, and the IndexNow job remembers what it last announced across deployments rather than on a disk a deploy replaces.
  • The pricing page's plan tabs on a phone are a pill again; the tab button carried two class attributes and browsers keep only the first.
  • The All Projects page's loading skeleton mirrors the live table again: a name link, a Team badge, a Connectors badge, a square project image, a Connection badge, the portal link, the created time and the Active badge, at the widths the live columns take.
  • On phones the menu button of the floating nav ran off the right edge of the pricing, comparison, creator-type and changelog pages: the sheet those pages sit on drew its fade overlay as a box wider than the card, so the page laid out wider than the phone and the browser zoomed it to fit. The overlay is now painted outside the card the way a shadow is, adding nothing to the page's width; a long route in a changelog note wraps instead of widening the page; and a browser test measures every page family on a phone viewport.

Interface and copy

  • The passes ticket under the home hero is hidden on phones; the footer's Company column reads Blogs, Changelog, Roadmap and Status.
  • The rival counts quoted on the comparison pages (webhook events, MCP tools, REST resource families, team permissions, gateways) are read from the code that defines them, and the Subscriby tiers on those pages come from the live plan rows.
Versão 5.0.2

Subscriby 5.0.2

Billing and plans

  • The dashboards do the upgrade sum for a creator below the top tier: a fee outlook card shows this cycle's transaction fees, names the next tier as the "Subscriby Starter Plan" or "Subscriby Growth Plan", and shows the fees it would have saved as a figure of its own. Its three columns align, its sentences say what they mean, and its button reads "See Available Plans". A once-a-cycle email says when the tier above already pays for itself.
  • The cancel modal states what cancelling actually does: the date the plan stops, the bundled features and add-ons that end, the limits and the fee that change against the Free tier, the portal handles that revert, the fees still to be invoiced, and that projects, members and payments stay. The Close button reads "Keep my plan", the dialog is wide enough to read, and its seventeen strings ship in ten languages.
  • After a tier move, the billing page quotes the price the invoice charges: the subscription webhook reads the coupon back from Stripe with the discounts expanded, so the locked-in price is recorded.
  • A plan on sale is pushed to the gateways by the action that writes it, so publishing a draft, or creating or saving a plan over REST, MCP or an integration, no longer leaves it without a Stripe price. A start link to a draft says it is not on sale instead of opening a checkout the gateway refuses.

Connectors

  • A connector can be reserved for a platform tier: Slack, Zoom and Google Drive from Starter; WhatsApp and Microsoft Teams from Growth. Installing below the tier is refused with the plan it needs, under the existing CONNECTOR_TIER_REQUIRED code. The tier shows as a "Starter plan" or "Growth plan" chip on the public directory and in-app marketplace cards, as a Plan row and in the pricing box on both detail pages, in ten languages.
  • A roadmap connector's page asks search engines to follow but not list it until real copy lands.

Passes

  • A season's preview opens at the next pass instead of the dates already behind it, on the portal card and in the bot. The passes already run are counted in a line above, the "more passes" line counts what is left after the ones shown, and a pass running right now leads the preview.

Pricing page

  • A pricing page of its own at /pricing carries the one complete plan comparison: eight sections and sixty-odd rows read from the live plan catalogue and the product's own settings; sticky price cards that keep name, price, fee and button when stuck, in compact spacing; a billing-cycle toggle that flips every figure; a stacked phone layout; a Connectors section that reads every shipped and roadmap connector from the catalogue and shows a dash under a plan that cannot install one; Time-Limited Passes and Pass Series as two labelled rows sharing one value; addon cells shown as a price block ("+$19/mo" or "+$190/yr"); and a card-grid FAQ that also replaces the accordion on the vertical and comparison pages. The home cards and the in-app plans page link to it.

Marketing site

  • Every frontend hero takes the pricing page's dark treatment: the twelve vertical and twelve comparison pages and their indexes, the connectors directory and detail pages, the blog index and articles, and the four legal pages, which gain a hero for their title and last-updated line. The white sheet that overlaps a hero fades into the page from halfway down.
  • The home page's title is "Membership Bot for Paid Channels & Groups — Subscriby" and names no platform, because the product runs on connectors rather than on one platform. The home and pricing titles and the structured-data names read the brand from configuration.
  • The comparison pages quote catalogue counts (gateways, webhook events, REST resource families, abilities, MCP tools) from the code that defines them and build Subscriby's tier rows from the plan rows, so no figure can go stale again. The Zapier integration is no longer called an "official app", processing fees are named as the gateway's own, and the rival facts are as of 2026: InviteMember's codes, branding and gateways per plan, Memberful's single Standard plan, Ko-fi Gold at $12, LaunchPass Basic unable to charge, and BotSubscription's eight-step scale under the TGMembership name.
  • The blog article's closing call to action is a dark card with a lime button and a pricing link, in ten languages.
  • The chat bubble loads on the first pointer, key or touch, or after idle time within five seconds, instead of with every page.
  • The fixed nav renders its colours server-side and toggles them without fading, so nothing flashes on load; its white text yields to dark when the mobile menu opens over a dark hero; the phone's sticky plan bar keeps a constant height. Row labels on the pricing table carry a dotted underline that turns solid on hover. The home page's Questions marquee sits close under the compare link again.

Blog

  • Every article carries a byline and shows an "Updated" date once a revision lands a day or more after publication. The author is emitted as an Organization node linked to the blog, Open Graph carries article:published_time, modified_time and section, and an article without a banner falls back to the site card instead of failing.
  • Localised copies of an article name the English address as their canonical and declare no alternates, because articles exist in English only. A category page carries its own title, heading and description in ten languages, and an article's fallback description ends on a word.

SEO and structured data

  • The home page's structured data stops claiming a rating no visitor can see, prices its offers from the live plans as unit price specifications, and the site description names no single platform. The home, blog and legal pages stop emitting meta keywords.
  • The Organization node carries the company's legal name, founding date, founder, postal address and support contact, read from configuration, and lists only the profiles that exist: X, LinkedIn, GitHub and Facebook.
  • Every sitemap entry carries a real modification date or none; the blog's entries drop their locale alternates; blog category pages join the sitemap; the comparison and vertical indexes describe their pages as an ItemList; the legal pages carry one title each; the generated sitemaps are no longer shipped with the code.
  • IndexNow: when a marketing address changes, the sitemap job announces exactly those addresses to Bing, Yandex and the other IndexNow engines, never the whole site. The key is INDEXNOW_KEY, served at /{key}.txt.
  • Every public host answers its own robots.txt; the dashboard host tells crawlers to index nothing through X-Robots-Tag; sitemaps are served with an hour's cache instead of a year's.
  • /index.php, a path behind it and a trailing slash answer a 301 to the canonical spelling; the spelled-out default locale (/en) redirects permanently; an error page no longer claims a canonical address, an og:url or a breadcrumb.
  • The retired domain redirects to https whatever scheme the server sees behind the proxy, so links from the old domain land on the new site instead of a plain-http 404.
  • Marketing images state their width and height before the bytes arrive; the hero word mark and the blog banners above the fold ask for high fetch priority; connector logos lazy-load by default, load eagerly in a hero, and carry the connector's name as alt text; creator avatars in the hero are named by their creator. The exchange-rates strip and the cookie banner are marked data-nosnippet, and the two italic font files lose their preload.

Dashboard

  • The Acquisitions vs Cancellations chart fills its card beside the ranked revenue list on wide screens.

Under the hood

  • The plan sync resolves each gateway handler through a typed method.
  • AWS SDK and related packages updated to their latest versions.
Versão 5.0.1

Subscriby 5.0.1 : The contract release

Features

  • The connector contract release: the first connector's legacy columns and the invite-token pivot are gone, every read answers from the connector rows, and the connector SDK ships as 2.0.0. Nothing changes for creators or members.
  • An All Transactions ledger with search, sort and filters, linked from every Recent Transactions card; a cash flow card beside the portfolio; a calendar tile on every transaction and recent-subscriber row; Revenue per Plan as a ranked bar list.
  • A downgrade warns which chosen portal handles it will replace and sends the new links; a member is found by the account they connected, over REST and MCP; the platform bot's command menu is a catalogue in code and every entry answers.
  • The OpenAPI document carries the bearer scheme, the error envelope, paging, and the ability, events and MCP tools of every operation; every REST resource family and every webhook family is documented end to end with real examples; every documentation link carries its version segment.

Fixes

  • A fresh verification link is one click from the sign-in page and from an expired link, links live a day, and a typed address is lowercased instead of refused; the sign-up email stops at its first failing rule.
  • Every bot button fits the platform's 64-byte callback limit, so the project card, the plan's resource picker and the paged lists answer again; "Sign in with Telegram" answers again.
  • The quarter-hour sweep issues the access a purchase never received; a season is reissued one date at a time; opening a date no longer withdraws the next one's link; a removal's ban expires on its own; deleting a project withdraws its installations.
  • The API answers CORS preflights in full; a missing row is a 404, never an error report; a duplicate plan name is a field error on every surface, never a 500.

Interface and copy

  • The connector sign-in methods fold into one pane above the form; the register button reads "Create My Subscriby Account"; the marketing pages, comparison tables and legal pages speak the connector family; five home-page mocks rebuilt as larger animated scenes; the passes ticket restyled.

Under the hood

  • The runtime, the web framework and the billing, spreadsheet and payment libraries move to their current major versions; reminder ladders and sweeps stream per chunk; the reconcile sweep asks about each live grant once a day.
Versão 5.0.0

Subscriby 5.0.0 : Connectors

Overview

  • Subscriby is now connector-based. A project installs connectors; Telegram is the first official connector, and everything Subscriby does for a Telegram community today it does through that connector. Nothing changes for existing creators or members on upgrade: every project, bot, member, invite link, pass and wizard keeps working as before.

Highlights

  • Connectors Marketplace, on the website (/connectors) and inside the app: Available, Experimental, Under Development and Coming Soon lanes, official badges, New and Trending chips, a detail page per connector with Overview and Configuration tabs, and a Notify-me list on roadmap connectors. Discord is under development; Slack, WhatsApp, Microsoft Teams, Discourse, Ghost, Google Drive, GitHub, Reddit, Guilded and Zoom are on the roadmap.
  • A Connectors page per project: install, connect, verify, configure and disconnect a connector; switch its capabilities on or off per project (messaging, broadcasts, support relay, built-in payments, recovery); run the Connector Doctor for a verdict on every gated place; uninstall with an impact preview, and Restore Access after reinstalling.
  • Connector outages and Outage Compensation: when a platform refuses a project's bot, dependent plans go off sale everywhere and the creator is told; when the outage ends, the lost time is banked on every affected purchase and everyone hears about it. Growth projects are health-probed every 15 minutes and can fail over to a standby bot automatically.
  • Notifications Center: every creator alert kept in an inbox with a bell that moves, on the dashboard, REST and MCP.
  • Analytics by connector on both dashboards, REST and MCP; a ranked portfolio leaderboard on the overall dashboard.
  • Email-first creator accounts with linked connector accounts; per-class alert destinations; members' connected accounts on the portal with "Notify me here" per account.
  • Telegram Stars is a payment method the Telegram connector provides; a project can hold one native payment method per connected connector.

Reliability

  • A platform re-sending an update after a timeout is handled once.
  • An operator can pause a connector during an incident: its webhook answers "retry later", outgoing messages wait until it resumes, probes and reconciliation skip it, and the dashboard shows it as Paused. Nothing is lost.
  • Access grants are reconciled against every gated place every fifteen minutes.
  • Disconnecting a project's bot no longer removes the project's members, subscriptions or resources.
  • Relinking a bot to a new token keeps its installation, outage ledger and linked identities.
  • Webhooks now fire for projects that belong to no team. Before, payment and membership events on those projects reached no endpoint at all.

Dashboard and portal

  • Subscriptions show whether a member joined the places their purchase unlocks ("Joined", "1 of 3 joined"), cancelled renewals read "Access continues until …", and the subscriber's billing email is shown.
  • The Resources page offers one tab per kind the project's connectors gate; nothing can be added until a connector is connected; "Manual" perks read "Manual Perk".
  • The Disaster Recovery pages render once per installed connector, in that connector's words.
  • Member notices route by intent: access notices on the platform the access is on, support replies where the member wrote from, receipts and reminders on the member's preferred account, email only when nothing else reaches them.
  • The dashboard, emails and API refusals say "connected account" and "connector" where they used to name one platform, in all ten languages.
  • Sign-in and sign-up offer "Continue with …" per connector that signs creators in.

Integrations: breaking changes

  • The bot-shaped surface is removed. Existing webhook subscriptions and API tokens are migrated at deploy, so nothing goes silent; new Zaps and workflows must use the connector names. New Zapier, n8n and MCP majors ship with this release.
  • Removed: GET / DELETE /v1/projects/{p}/bot. Use instead: GET / DELETE /v1/projects/{p}/connectors/{key}/installation.
  • Removed: GET /v1/projects/{p}/distribution/bot-link. Use instead: GET /v1/projects/{p}/distribution/start-link?connector=.
  • Removed: bot_id on project create and update. Use instead: POST /v1/projects/{p}/connectors/{key}.
  • Removed: MCP get_bot_status, disconnect_bot. Use instead: get_connector_installation, disconnect_connector.
  • Removed: Webhooks project.bot.connected / disconnected / status_changed. Use instead: connector.connected / disconnected / status_changed.
  • Removed: Abilities bot:manage, platform-telegram:admin. Use instead: project-connector:*.
  • Removed: telegram_user_id on members. Use instead: identities[] (connector, external id, display name, username, preferred, notify).
  • Removed: Resource type, chat_id. Use instead: kind (manual or connector:kind, e.g. telegram:channel), connector, space {id, external_id, title}.
  • Removed: ?type= on the resource list. Use instead: ?kind=, ?connector=.
  • Removed: Health reasons telegram_api_*. Use instead: connector_api_unauthorized / not_found / rate_limited / error.
  • Removed: Payment method provider platformcurrency. Use instead: telegram:stars; payment methods carry connector.
  • New surfaces: GET /v1/connectors, GET /v1/projects/{p}/connectors, installation verify and uninstall preview, GET /v1/me, /v1/me/identities, /v1/me/alert-destinations, /v1/me/notifications, GET /v1/subscriptions/{s}/grants and grant reissue, creator tasks, the full Disaster Recovery family on REST and MCP, and the webhook events connector.*, recovery.*, member.identity_linked / identity_unlinked, member.resource_pending / resource_failed / access_extended, creator_task.*.

For developers

  • Connector SDK 1.0.0 (subscriby/connector-sdk): the manifest (connector.json), the ports, the Core API a connector calls back into, the conformance kit, and a Fake connector as the reference implementation.
  • Building Connectors docs: a full reference (manifest block by block, one page per port and per Core API contract, the conformance kit rule by rule, testing and publishing) and a ten-chapter tutorial.
  • Zapier and n8n docs are generated from the integrations themselves, and both builds fail when a Subscriby endpoint or event has no counterpart.

Fixes

  • Photos and files members send to the support inbox open again.
  • The Connector Doctor asks about a channel through the installation that administers it, so a healthy channel no longer reads "chat not found".
  • The Built-in payments switch is enforced; Account recovery reads Always On on a project installation.
  • A creator's project list keeps one order, so the bot's project picker stops shuffling.
  • A closing season date no longer races its own hand-off; invite links are scoped to their pass window.
  • Invoice events from the platform's billing provider are handled again and billing.invoice_paid is emitted once per invoice.
  • Every Paystack event after the first charge reaches its subscription; a webhook's signing method resolves once the parked checkout expires.
  • Places linked in the same second keep one fixed order in the Restore Access report, the uninstall preview and the resource list.
  • The portal sidebar no longer raises a deprecation for a project without a description.

Upgrade notes

  • Nothing for creators or members to do. The release ships as two deploys days apart: 5.0.0 adds the connector tables and runs a one-off backfill of every existing bot, chat, resource and invite link into them; 5.0.1 removes the old columns once the nightly verification has been green for the chosen number of nights.
Versão 4.1.0

Subscriby 4.1.0

Features

  • Season lounge resources with validation for linked rooms; cryptocurrency exchange rates, formatting and minimum prices improved; the plan editor's Resource Access section reorganised.

Fixes

  • Resource binding in the plan editor.
Versão 4.0.3

Subscriby 4.0.3

Features

  • Storefront order management for plans with a sales cap per plan; the series timetable in the bot; compact date ranges for pass windows; unknown commands handled and standby chats probed; bot health probed one job per bot; Telegram invoice titles fit their limits.

Fixes

  • Scripts embedded in pages are escaped safely; "Prevention is part of the Growth Plan" reads the same everywhere; the readmitted count on the home page; backlog queries handle many projects in one request.
Versão 4.0.2

Subscriby 4.0.2

Features

  • A platform metrics service aggregates and caches platform-wide figures.

Fixes

  • The live mirroring message reads the same in every language; home page colours for the flexibility and safety sections.
Versão 4.0.1

Subscriby 4.0.1

Fixes

  • PayPal acknowledges webhook events it takes no action on; dashboard rows without a creation timestamp render.
Versão 4.0.0

Subscriby 4.0.0 : The layered rebuild

Features

  • The REST API and the MCP server reach parity with every dashboard verb, and webhooks announce resource, payment method and support writes.
  • The support inbox relays through a Telegram group with topics end to end; webhook endpoints enforce allowed IPs and CIDR ranges at delivery; a rate-limited broadcast resumes after the last member reached.
  • Plans gain sales cutoff anchors before the last start or end; the plan row's composition is saved; stale subscription anchors roll forward and proration is exact in the switch modal.

Fixes

  • The bot asks for a plan's new price in the plan's own currency, keeps linked resources ticked after a save, attaches a channel shared through the request keyboard, and can enable Telegram Stars and access codes again; the project buttons stay off the project dashboard.

Under the hood

  • Every module is rebuilt on one layered architecture with a request-scoped tenant context bound per entry point: billing, payments, the portal, the support inbox, subscriptions, plans and passes, notifications, analytics, webhooks, teams, settings, sign-in, access codes and coupons.
  • The Telegram bot's handling is split into membership, payment and message pipelines over typed state, and every domain value crosses a boundary as a typed value.
  • A quality gate runs static analysis, formatting and architecture checks on every change.
Versão 3.6.6

Subscriby 3.6.6

Features

  • Broadcasts can target a plan; webhook payloads carry the plan id and the days until expiry; "Any Subscription Plan" wording; the sales cutoff anchor is stored per pass series.
Versão 3.6.5

Subscriby 3.6.5

Interface and copy

  • Payment prompts and plan translations updated; the compliance page uses flag components instead of emoji.
Versão 3.6.4

Subscriby 3.6.4

Features

  • Overlapping passes in a series are prevented; the series modal lists passes as a table; season completion and sales confirmation notices in every language; the support relay honours the member's locale.

Fixes

  • Trial days are capped at 365; hero spacing and creator card positions on the home page.
Versão 3.6.3

Subscriby 3.6.3

Features

  • Support backlog notifications for unanswered messages; overlap detection for passes; invite links filtered by pass window in the bot.

Fixes

  • Tenant scoping on webhook deliveries and activity logs closed a data leak; activity log descriptions cover more subject types; hero and layout responsiveness.
Versão 3.6.2

Subscriby 3.6.2

Features

  • Subscription management and member broadcasting over MCP.
Versão 3.6.1

Subscriby 3.6.1

Features

  • Team and group management over REST and MCP; token management endpoints and an updated ability catalogue; a plan kind replaces the legacy pass flag; season details on subscription views; a "Still growing" notice on the series portal.

Fixes

  • Plan kind resolves correctly for time-limited passes; rule-absorbed series windows no longer duplicate in selections; series rule watch dates widened to full days.
Versão 3.6.0

Subscriby 3.6.0 : Pass series

Features

  • Pass series: a plan sells a whole season of passes as one purchase, with seat claiming, entitlements per date, bulk inclusion rules, a presale for holders of a finished season, the option to start the next season, and series retirement and absorption.
  • Pass windows over REST and MCP; a calendar feed and a series timetable; countdowns for ongoing windows at checkout; ongoing purchase windows.
  • Creators are reminded of upcoming access windows; access is revoked when an open window is cancelled, with events and notifications; trial usage billing and Telegram Stars conversion rates.

Fixes

  • Series pass windows take the right timezone; plan names are escaped in announcements; the onboarding email and the Help link point at the right guide pages; bot conversations read stored ids consistently.
Versão 3.5.4

Subscriby 3.5.4

Features

  • Broadcast audiences can be pass segments; queue status and reminders for subscription holders; pass windows remember when they last reminded.
Versão 3.5.3

Subscriby 3.5.3

Fixes

  • Access code allotment retrieval meters consistently.

Under the hood

  • Testing best practices documented as rules.
Nossos Roadmaps