Andrew Beaven

Awesome, thanks so much for your work on this. When might we expect this to be updated in the AppStore?

@turquoiseowl where are we at with this one? I'd be willing to put something towards sponsorship for this task if it meant it got things moving. @peters awesome! Would be...

Cancel that last point. An acceptable workaround for the anchor issue would be to specify the protocol: ``` 13 - link - works ```

Oops, sorry forgot to add that part :/ The examples I gave above were rendered on a page at http://localhost:8082/ru. I would expect all the generated URLs to include the...

Unless something has changed with how the URLs are generated, I think this would still be an issue. I'll check when I'm back near a computer next week.

Just confirmed that this is still an issue. To clarify, when on a localized URL (eg. `http://localhost/ru`) the following methods of generating URLs will not be localized correctly (ie. `http://localhost?test=a`...

I don't think you're experiencing this bug sorry. i18n doesn't indiscriminately localise every URL - check out [EarlyUrlLocalizer.cs](https://github.com/turquoiseowl/i18n/blob/286c9427c7860805043616723621c15e23c9f441/src/i18n/Concrete/EarlyUrlLocalizer.cs#L159). There might be a more efficient way, but you can use `LanguageTag.SetLangTagInUrlPath`...

It'd be nice if `EarlyUrlLocalizer.LocalizeUrl` had an _optional_ langtag parameter and when not supplied it uses the current request's language/default language.

+1 for stacking line charts

This feels like a pretty big security concern that should be patched? I'm experiencing the same behaviour where upon receiving a correlation failure due to the nonce timeout, issuing a...