hq1

Allow custom parsers in configuration reader so `terms()` are not required

1. Publish/subscribe on `{config_reloaded}}` can (optionally) work within the whole cluster 2. Provider names could be stored as gproc keys instead of having to spawn registered processes

Need a better support for frequent K/V calls. ETS would be just enough.

- SSH key-based access - involve ranch (?)

Fix it

Deployment needs to be coordinated with WordPress plugin update. Reasoning: there's too much confusion coming from the use of the "API" terminology, leading to wrong keys being generated by users.

Fetch https://github.com/obsidianmd/obsidian-docs/ and build it properly, support whatever Obsidian supports.

Fix new tab links + shared links losing URL context

1

Another stab at #4276

Heads up: Plausible site verification tool

8

Hey, just wanted to notify you about a new feature we'll be soon introducing in Plausible - a site verification tool allowing you to verify the integration. It will employ...