Adswds Platform 3.5.0 release notes

29 July 2026 — Adswds Platform 3.5.0 is now available.

This release connects site inquiries to ops follow-up: Contact keeps Telegram as the primary channel and adds an email lead form; public APIs use AES and Turnstile; ops manage status and notes in the console. Leads stay outside the end-user product path. It also tightens landing / safe page ZIP uploads with static-page checks and industry-style guidance.

What’s new

Contact dual channels

• Telegram as the primary CTA
• Email form: name / email / optional company / message
• Privacy link and submit feedback

Public APIs

• GET /site/tools-config for Turnstile SiteKey and related config
• POST /site/leads to submit a lead
• AES + timestamp checks; server-side Turnstile verification
• IP rate limits; duplicate window for the same email + message

Submission enrichment

• GeoLite2: country / city / ASN / proxy flags
• UA: browser / OS / device
• Raw IP and UA retained

Ops console

• /control-hub/leads: list, detail, status notes, delete
• Sidebar entry for Site Leads

Landing / safe page uploads

• Frontend checks: root index.html; heuristic block for common Vue / React / Next / Nuxt SPA fingerprints
• Size tip: industry targets often ~1–2MB for fast mobile loads; keep ZIPs to a few MB; soft warn above ~3MB (80MB is the hard ceiling)
• AI tip: prompt for pure static HTML, not SPA / scaffold shells

Security and boundaries

• Turnstile Managed challenge
• /site/* is a dedicated prefix outside end-user sessions
• No outbound email in this release; ops follow up in the console
• SPA blocking on page upload is a frontend heuristic

How to use

1. Open Contact on the site: prefer Telegram, or use the email form
2. Complete Turnstile and submit
3. Ops review and update status under Site Leads
4. Upload landing / safe pages as static HTML packages and keep ZIP size lean

Try it now

• Free trial
• Admin demo
• Changelog
• Support