jplevine

We just announced something called the Workers Analytics Engine today: https://blog.cloudflare.com/workers-analytics-engine/

More coming soon!

Happy to chat more - jpl at cloudflare dot com

Yep, we use ClickHouse! And a lot of other software :)

Archived URL from the White House: https://trumpwhitehouse.archives.gov/briefings-statements/st...

Sorry to hear that - can you try again at this link? https://dash.cloudflare.com/?to=/:account/web-analytics

(We actually did have a replication issue where some folks in the EU had trouble accessing this page)

Sorry to hear that -- can you try again at this page? https://dash.cloudflare.com/?to=/:account/web-analytics

Would mind trying again here? It should work now!

(PM for Cloudflare Analytics here)

Thanks! If you do end up "orange clouding" and proxying your site through Cloudflare, we can show you lots of stats about your website, even from clients that don't support JS :)

(PM for Cloudflare analytics)

Sorry to hear that. We appear to have a client-side caching bug (ironic!)

Can you try refreshing on the 404 page and see if you have access now?

(PM for Cloudflare Analytics here.)

At launch, we just support one token per account. We are already working on supporting multiple analytics tokens in one account though!

(PM for Cloudflare Analytics here)

FWIW, this isn't an issue for server-side (or in our case, "edge-side") analytics.

(PM for Cloudflare Analytics here)

> But in their case it seems they are not even trying to filter bots

We try very hard in fact :) We just have some work ahead to surface this better in our analytics UI.

For more detail: we actually assign a "bot score" to each request. Customers customers of our Bot Management product can use this information to block bots at the edge. We are working right now to show the distribution of Bot traffic in the UI so that anyone can see how we are classifying traffic.

Hi, I'm the product manager for Cloudflare Analytics. Thanks for this thorough and thoughtful review.

We are totally serious about building a world-class, privacy-first, free analytics product. At risk of HN cliche, this is our "early work". We are actively working to fix many of the rough edges mentioned here; if we had waited to fix all of them before shipping, we never would have shipped!

For folks who haven't seen it, I suggest checking out our launch blog post[0] which gives some more context around edge vs browser analytics (spoiler: we do both!), why we count visits the way we do, and how we handle bot traffic.

We know we have work to do on the "jagged lines" problem. For some low-traffic websites, we might show noisier, low-resolution data than is ideal. (We've artificially constrained our analytics to query a maximum of 7 days at a time because this problem is exacerbated with longer time ranges.)

My colleague Jamie wrote a nice blog post about how and why we sample data [1]. In short: we have an existing customer base of 25 million+ Internet priorities, whose traffic volume spans 9 orders of magnitude! Sampling data is an elegant approach that allows us to serve fast, flexible analytics for all our customers. Sampling shouldn't be feared, but we know we can do better in some cases. We've recently merged some deep-in-the-weeds improvements to ClickHouse [2] that should result in improved resolution. And we're currently working to store full-resolution data for the smallest websites.

Happy to address any other specific points that folks have questions about.

[0] https://blog.cloudflare.com/free-privacy-first-analytics-for... [1] https://blog.cloudflare.com/explaining-cloudflares-abr-analy... [2] https://github.com/ClickHouse/ClickHouse/pull/14221

Hi Luke, late to the show here, but agreed this should never happen. Can you reach out to me directly with the domain name you used? You can DM me at twitter.com/jplevine

Not automatically included :) I came across the Sega Saturn video a couple weeks ago from this thread: https://news.ycombinator.com/item?id=12074096

Yes: https://firstlook.org/theintercept/2014/08/15/cat-video-hack...

As mentioned in another comment, we recommend using schema-less embeds, e.g. "//www.youtube.com/embed/...". Regardless, these embeds should still work when embedded over HTTP.

Hi spindritf -- I work for YouTube and have been looking into some mixed content issues with embeds. Mind if I email you and ask for some details about this scenario?