If you're curious: An API is more or less just the communication boundary between two pieces of software.
A common sign of a bad API (including this one) is when it presents data in an overly human-centric way rather than something more computer-friendly.
For a human it's really easy to see "Regents Park" and "Regent's Park" are very very likely referring to the same station, but a computer can't know that unless a human goes out of their way to tell it that.
You could argue the TfL API is perfectly fine for its intended use-case of updating the arrival screens (which are meant for humans), but it's generally better to design APIs to grow for future use-cases you haven't thought of yet. Changing an API tends to be hard once it's being used in the real world.
For example: The older TfL stations have LED matrix displays for displaying information, which are very limited in how much text they can display at once. The newer stations have big TV screens instead, which can show a lot of information. It wouldn't surprise me if this is the underlying reason behind some of the inconsistencies, especially ones like "Kings Cross" vs "King's Cross St. Pancras". I'd bet the longer names with punctuation correspond to arrival displays in the newer stations.
If the GitHub Actions temporary token does not have workflow-defined permissions scope, it defaults either to a permissive or restricted default scope based on the repository's setting. This setting can also be configured at the organization level to restrict all repos owned by the org.
Historically the only choice was permissive by default, so this is unfortunately the setting used by older organizations and repos.
When a new repo is created, the default is inherited from the parent organization, so this insecure default tends to stick around if nobody bothers to change it. (There is no user-wide setting, so new repos owned by a user will use the restricted default. I believe newly created orgs use the better default.)
It won't be plug and play since you'd have to pull out the shaders and make them work in your app, but the implementation supports quite a few material variants. The PBR shader implementation starts in source/Renderer/shaders/pbr.frag
The context menu item for duplicating tabs might be new, but you've been able to middle-click the refresh button to duplicate the current tab for quite some time now.
It's basically an ongoing large-scale research project working to quantify the way people experience city spaces from a neuroscience perspective (or at least that's my understanding -- I work with some of the people who are working on it.) Maybe the work they're doing could be relevant to what you all are doing?
It doesn't change the output encoding by default, but if you manually set it to UTF8 it works. (IE: Console.OutputEncoding = System.Text.Encoding.UTF8;)
That might be all you need to fix the F# REPL too.
Yup, the "test for feature availability" attitude doesn't properly account for features which are available yet buggy.
I recently ran into an issue where a media-heavy blog post of mine would sporadically crash iOS Safari. I ended up narrowing it down to my use of ImageBitmap to accelerate rendering images into 2D canvases on the page.
My fix ended up being to modify my ImageBitmap feature check to pretend it wasn't supported on Safari.