Social
Our posts, without the tracking widgets.
Embedded social widgets load third-party scripts and set cookies before a visitor has done anything. We keep a copy of our posts here instead.
Recent posts
What we have been saying.
Maintained by hand from the accounts listed below. Following a link takes you to the platform, where that platform's own terms and tracking apply.
Loading posts…
Why it works this way
A deliberate technical decision.
A standard social embed is a third-party script with full access to the page it is placed on. It typically sets identifiers before the visitor has interacted with anything, which means a cookie banner becomes necessary purely to display a feed of posts you have already published.
Copying the posts into a small JSON file removes the script, removes the cookie, removes the banner and removes the performance cost. The trade-off is that somebody has to maintain the file. On a corporate website with a handful of posts a month, that is a reasonable exchange.
If the volume ever justifies automation, the correct route is a scheduled server-side job that fetches from the platform API and writes the same JSON file. The browser still loads nothing from a third party. That path is described in the news and social guide in the repository documentation.
Would rather just email?
So would we, most of the time.