Notices by Ross McKay (webaware@fosstodon.org)

@chris hey look what just showed up in my feed: a blog post explaining DNS ⬆️

by @melroy

@chris for the bookshelf (physical or otherwise), @mwl has a couple that would help. His books are very readable, even entertaining.

Networking for System Administrators covers what it says in the title, including a brief section on DNS. It covers the basics but not in-depth.

DNSSEC Mastery gets into the gory details of, well, DNSSEC :)

https://www.tiltedwindmillpress.com/product-category/tech/

Networking for System Administrators, 2nd Edition is coming…

https://www.tiltedwindmillpress.com/product/n4sa2e-sponsor/

@dvk filters are your friends. Filters in Mastodon are pretty flexible, and I really like the ability to have a time period on some filters. Might save your sanity!

@liztai love this. A couple of weeks ago we did a week of duck, starting with simmered duck of which we ate legs and thighs, breast the next night, duck pilaf for two nights with the rest of the meat and some duck stock, and a vege soup with the remaining duck stock. Superb eating.

@liztai in a New Zealand born fam, my brother calls eldest sister The Big Cheese and I can't see any reason not to adopt this broadly.

If your website has unreadable text (poor typeface, small size, bad contrast, etc.) and I can't turn on Reader view, I'm closing the tab.

#CSS #WebDev #accessibility

@tim

Does OpenLiteSpeed honour the header "Vary: Accept"? From examples I've seen, it honours other Vary values. You should be able to get separate caches for each Accept value – not just text/html and application/activity+json but any others sent.

Try setting that header in the plugin, clear the OpenLightSpeed cache, and test.

header('Vary: Accept');

@pfefferle do you plan to add that to the plugin? It should automatically fix nginx, and any other caches that support Vary headers.

@futtta @pfefferle @javiercasares

How about: add header Vary: Accept

Also define DONOTCACHE for PHP caching plugins that won't support varying cached content.

@futtta

If your (host is) using typical nginx config like this one on WP docs:

https://wordpress.org/documentation/article/nginx/#nginx-fastcgi_cache

Then you should be able to break caching with this:

if ($http_accept = "application/json") {
set $no_cache 1;
}

But nginx will cache different content based on the Accept header if you tell it to, e.g. as long as #WordPress #ActivityPub sends this with its responses, cache will differ by Accept header:

header('Vary: Accept');

https://nginx.org/en/docs/http/ngx_http_fastcgi_module.html#fastcgi_cache_valid

@javiercasares @futtta

No so fast; that's not what I said in my post. I said that if you *wanted* to break cache for (that specific) Accept header, that's how you'd do it.

But please read the thread from this post and below, where @rmccue argues that we *should* be caching JSON requests, and when.

https://aus.social/@rmccue/110020902246277742

Also note that caching some JSON requests are highly desirable, like oembed requests for example.

https://snippets.webaware.com.au/snippets/caching-oembed-with-nginx/

@javiercasares @futtta

Also note that the ActivityPub plugin doesn't look for only that one exact header, it looks for four of them:

https://github.com/pfefferle/wordpress-activitypub/blob/master/includes/class-activitypub.php#L78-L81

@javiercasares @futtta @pfefferle I reckon setting that Vary header will do the trick, for nginx at minimum and possibly some others.