# CloudFront tracker on Write.as blogs

**URL:** <https://discuss.write.as/t/cloudfront-tracker-on-write-as-blogs/12867>\
**Category:** General\
**Created:** [August 21, 2024, 12:00pm UTC](https://discuss.write.as/t/cloudfront-tracker-on-write-as-blogs/12867 "2024-08-21T12:00:47Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![PaoloAmoroso](https://discuss.write.as/user_avatar/discuss.write.as/paoloamoroso/32/1659_2.png) [@PaoloAmoroso](https://discuss.write.as/u/PaoloAmoroso)\
**Post date:** [August 21, 2024, 12:00pm UTC](https://discuss.write.as/t/cloudfront-tracker-on-write-as-blogs/12867/1 "2024-08-21T12:00:47Z")

</div>

My blog [https://journal.paoloamoroso.com](https://journal.paoloamoroso.com) is hosted at Write.as but is linked to my custom domain `paoloamoroso.com`. When I visit the blog with Firefox on Linux uBlock Origin reports one tracker associated with `cloudfront.net` and `cdn.writeas.net`:

 ![cloudfront-tracker](https://discuss.write.as/uploads/default/original/2X/3/361b9f3c0a8a5e8ae99bd999e9a9bd998788f9c2.png)

What is the tracker for? Can it be removed?

---

<div class="post-metadata">

**Author:** ![angelo](https://discuss.write.as/user_avatar/discuss.write.as/angelo/32/884_2.png) [@angelo](https://discuss.write.as/u/angelo)\
**Post date:** [August 22, 2024, 9:02pm UTC](https://discuss.write.as/t/cloudfront-tracker-on-write-as-blogs/12867/2 "2024-08-22T21:02:02Z")

</div>

Hey @PaoloAmoroso, it looks like [cdn.writeas.net](http://cdn.writeas.net) serves assets like fonts, CSS, and JavaScript over Cloudfront’s content delivery network. @matt would know more, but is this something new that you’ve noticed?

---

<div class="post-metadata">

**Author:** ![PaoloAmoroso](https://discuss.write.as/user_avatar/discuss.write.as/paoloamoroso/32/1659_2.png) [@PaoloAmoroso](https://discuss.write.as/u/PaoloAmoroso)\
**Post date:** [August 23, 2024, 6:25am UTC](https://discuss.write.as/t/cloudfront-tracker-on-write-as-blogs/12867/3 "2024-08-23T06:25:56Z")

</div>

Thanks, yes, I know these servers are part of the Write.as infrastructure. But I wonder what that tracker is for, and whether it’s necessary for Write.as.

---

<div class="post-metadata">

**Author:** ![PaoloAmoroso](https://discuss.write.as/user_avatar/discuss.write.as/paoloamoroso/32/1659_2.png) [@PaoloAmoroso](https://discuss.write.as/u/PaoloAmoroso)\
**Post date:** [August 23, 2024, 6:31am UTC](https://discuss.write.as/t/cloudfront-tracker-on-write-as-blogs/12867/4 "2024-08-23T06:31:13Z")

</div>

I installed uBlock Origin only recently and noticed the report, hence my curiosity.

---

<div class="post-metadata">

**Author:** ![matt](https://discuss.write.as/user_avatar/discuss.write.as/matt/32/2760_2.png) [@matt](https://discuss.write.as/u/matt)\
**Post date:** [August 29, 2024, 8:24pm UTC](https://discuss.write.as/t/cloudfront-tracker-on-write-as-blogs/12867/5 "2024-08-29T20:24:06Z")

</div>

Hmm, it seems like uBlock Origin might be resolving the `cdn.writeas.net` domain and finding it points to Amazon’s CloudFront, and then blocking the whole thing on those grounds.

I’d say it’s a _little_ overzealous on uBlock’s part, and you can safely un-block `cdn.writeas.net`. As @angelo mentioned, we only serve static files on that domain – there’s no tracking involved (as always).

---

<div class="post-metadata">

**Author:** ![PaoloAmoroso](https://discuss.write.as/user_avatar/discuss.write.as/paoloamoroso/32/1659_2.png) [@PaoloAmoroso](https://discuss.write.as/u/PaoloAmoroso)\
**Post date:** [August 30, 2024, 6:42am UTC](https://discuss.write.as/t/cloudfront-tracker-on-write-as-blogs/12867/6 "2024-08-30T06:42:26Z")

</div>

Thanks for the insight Matt.

Personally, I actually wouldn’t mind such a tracker even if it was there. But my readers may care and reach out to me for information.