Odin Vex

The reason I've proposed this is because I'm getting weird results from some engines using the default user agent (results from *one* website (in the case of Bing) that has...

I think proposing another config variable as to whether to spoof useragents in requests would be easy to extend while providing complete backwards-compatibility. Eg., `CONFIG_SPOOF_USERAGENT=true` (the default, to use the...

I've found the documentation baffling about how to somehow link missing registries to the actual containers. I can create CUSTOM registries, but they don't "link" to the containers in a...

There's a glaring issue with the code, though. `127.0.0.1` is not the only IP address you should be blindly allow-listing. `127.0.0.0/8` and `::1/128` (aka `localhost` *usually*). Some Docker deployments are...

I'd normally be entirely in agreement about API endpoints, but I think integer/float parsing from string to int/float is rather common among API handling, in general, because it's rather common...

> referencing the upstream issue [huginn/huginn#2661](https://github.com/huginn/huginn/issues/2661) to help other users find the suggested fix (even though people reported it didnt but linking helps people find it faster 😅 ) I...

> Thanks for the context. I think one way we can potentially do this without hacks is allow priority to be specified on the URL even if the payload is...

Sounds like simple casting would be an easier solution that handles everything.

> I prefer a solution that adheres to design principles (JSON is type strict, query parameters are not), is more flexible and future proof, not necessarily the "simplest" amount of...

Is that something around the corner or...?