Evan Rees
My feedback
2 results found
-
15 votes
An error occurred while saving the comment -
1 vote
An error occurred while saving the comment Looks interesting. Before shortlisting, please share a live demo and sandbox, full feature list, and pricing tiers. I need a recent security audit and pen test report, wallet policy (hot/cold, multisig or HSM, withdrawal approvals), supported chains, and custody model. Confirm KYC/AML vendors, Travel Rule support, sanctions screening, and logs for audits. Show matching-engine latency under load, rate limits, DDoS protections, failover, backups, and RTO/RPO. Clarify source code access and license, update path, and how you handle upgrades without downtime. Provide API docs, WebSocket feeds, and a test market. List fees you charge, hosting options (self vs managed), SLA, and support hours. Also confirm regulatory readiness for my country and what help you give during licensing. If you can share references or case studies, that would help.
This is a great suggestion. With Cloudflare now blocking most AI crawlers by default, it makes sense to offer a controlled way for site owners to explicitly *opt in* to AI bot access. Many of us actually want our content to be discoverable by reputable AI systems like ChatGPT, Gemini, and others — especially when they can drive visibility, recommendations, and traffic.
Right now, support has confirmed there’s no direct option or override available, which is limiting for businesses that depend on broader content reach.
An official mechanism — whether through a dashboard toggle, custom rule, or approved allowlist handled by support — would be extremely valuable. It would let site owners choose what’s best for their own content strategy while maintaining Cloudflare’s default protection for everyone else.
Thanks for considering this as a future enhancement. It would fill a meaningful gap for those of us who *want* AI accessibility rather than blocking it.