dgw

The vanilla solution to this is turning off unique URLs (allowing multiple keywords pointing to the same link) and you can track the performance of each different shortlink, rather than...

The description of #3355, which you referenced, seems to indicate that this behavior is intentional. Are you expecting a 200 Success status code for a request that did not in...

Maybe 409 (Conflict) would be a better response code for this case? > The request could not be completed due to a conflict with the current state of the resource....

@wgicio 30 seconds on google found https://community.n8n.io/t/http-node-error-400-not-handled/9739 It is possible to modify a workflow on n8n to handle HTTP 400.

I don't see how this could be considered a YOURLS problem. Any automation template provided by Make is their responsibility to maintain, and we (the YOURLS maintainers) have nothing to...

> The failure did not begin happening at a different time. I simply stated that I didn't check right after upgrading to 1.9.1 if that caused the failure. > I'm...

Another screenshot from @Yuuki2012 showing this also happens on stat pages (`/keyword+`):  Not making a separate issue, because whatever CSS change fixes the problem on the plugins page will...

Another reason to replace the dumb pattern-based parser is that it trips on etymologies that start with an infobox. For example, trying `.ety ferrule` on [the Wiktionary entry for _ferrule_...

Yet more reason to either use HTML parsing or switch to a library (e.g. [`wikiglot`](https://pypi.org/project/wikiglot/)): Some entries with multiple senses, such as [hoarding](https://en.wiktionary.org/wiki/hoarding), output incomplete definitions: ``` 11:33:06 .wt hoarding...

Noticed that https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/ had slipped by. Better to catch it now than having the analysis suddenly break in December.