Wow, watch out for your #themes, people. I thought that with statically-generated self-hosted #Hugo things should be great, right? But no, almost every theme pulled some asset (#fonts, #JavaScript, or #CSS) from a remote server. That's a leak right there.

Now I'm going to have to check my blog and see what #Wordpress is doing. I bet it's even worse..

Yikes. When did it become STANDARD to publish themes that expose visitor data to 3rd parties? @aral small web can be tricky!

Follow

@jgoerzen @aral lots of people still think it's faster to load resources like jQuery from some central CDN that other sites might use. For caching. 🤷 Not sure how long that ancient recommendation will stick around.

@finity @aral I know... but that people don't even think through the implications of that when making public themes. S I G H

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.