Pathogen-David

Ahh, that's the worst. Hopefully you realized your mistake sooner rather than later.

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.)

[0] https://docs.github.com/en/actions/security-for-github-actio...

You might find value in the glTF sample renderer https://github.com/KhronosGroup/glTF-Sample-Renderer

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

I just checked and the curl.exe on my system does not export any symbols, so not in this case.

It is possible to do that in the general sense though.

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.

Have you heard of eMOTIONAL Cities by any chance? https://emotionalcities-h2020.eu/

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?

Doesn't seem like they do. They attempted to acquire them back in 2009 but it didn't work out.

but since an indeterminate amount of time ago, it just stopped working for me.

Updating both Git and Git Extensions has seemingly fixed it for me, but the issues I was having were sporadic so maybe I've just been lucky

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.

I recently learned that some Google TVs have a “Basic Mode” that removes all the smart crud. https://www.androidcentral.com/new-google-tv-feature-will-le...

I haven’t had a chance to look into it further so I don’t know if it’s any good, but it might be worth looking into. (I’m also curious if anyone here has experience with it)

It looks like the audio samples have disappeared since 2017, but they're available on the Wayback Machine for those who want to listen: https://web.archive.org/web/20170831162900/https://www.vinci...

Yeah, according to https://book.mixu.net/ this was written in 2015, at nine years old I'd be worried about this not being super useful for modern CSS.

Here's a separate press release from PlayStation Studios has more details: https://sonyinteractive.com/en/news/blog/an-important-update...

In particular it lists some other studios not mentioned in this one:

    The US based studios and groups impacted by a reduction in workforce are:
    * Insomniac Games, Naughty Dog, as well as our Technology, Creative, and Support teams
    
    In UK and European based studios, it is proposed:
    * That PlayStation Studios’ London Studio will close in its entirety;
    * That there will be reductions in Guerrilla and Firesprite

Love the concept! It'd be cool if it was self-hostable, it'd be nice for monitoring certs in my homelab.

If an app or website exclusively uses third-party logins I generally won’t even use it. In general I don’t appreciate anything that tries to get cute about account creation.

(However I agree with the other comment about HN not being representative of typical users.)

I counted 14 out of 30 links on the front page back then still work and appear to refer to the same article / something relevant to the original submission.

Link rot is always disappointing, but I actually expected it to be far worse for links from 17 years ago.

If anyone wants to learn more about the older OM-84 model mentioned multiple times on this page, David Hilowitz has a fantastic video about it and its history: https://www.youtube.com/watch?v=pAIar0O-yvg

Up and Atom recently made a great video explaining this class of problems and some of the algorithms for solving it: https://youtu.be/fvM8ow6zNw4

Certain parts of Microsoft Learn are permissive, most .NET/C# documentation is Creative Commons Attribution:

* Conceptual docs: https://github.com/dotnet/docs

* BCL: https://github.com/dotnet/dotnet-api-docs

* ASP.NET Core: https://github.com/dotnet/AspNetCore.Docs

* WinForms/WPF: https://github.com/dotnet/docs-desktop

The C# language specification is unfortunately a bit fuzzier, but the conceptual docs above include what most people want: https://github.com/dotnet/csharplang/discussions/4855

The updated unified C# language specification is CC, but it's still catching up to modern C#: https://github.com/dotnet/csharpstandard

This rant could've easily been written by me. I have a very strong mental model of what should happen when I press keys on the keyboard, and when that diverges from what's visible on the screen everything in my brain grinds to a halt because my "you made a typo" alarms go off.

I can't comfortably use JetBrains products because they're really bad about letting you actually disable these things. VSCode extensions also love to add their own little settings that don't respect the higher level ones. Visual Studio previews somewhat frequently ship new "helpers" like this without a way to disable them (to their credit though, they do quickly add one once you point it out.)

I too wish more apps offered a top-level "disable everything unless I explicitly enable it" setting. Figuring out where the individual settings are buried only exasperates the frustration.

You can generate them using Graphviz's circo layout engine. https://graphviz.org/docs/layouts/circo/

According to them/Wikipedia, the layout's name is simply "circular layout". https://en.wikipedia.org/wiki/Circular_layout

Unfortunately even ordering the book on its own isn't a sure-fire way to get it well-packaged. The last several books I've bought were shipped in a thin paper bag (or a bubble mailer if I was lucky.)

As someone who takes care of their stuff, it's pretty annoying to get my books pre-worn.

If you want to stick to more natural Markdown syntax, I believe you should be able to use a Hugo render hook[0] to change how normal Markdown links are rendered instead of using a custom shortcode.

[0] https://gohugo.io/templates/render-hooks/

Ooh, thank you for sharing! This has given me a few things I should look into improving with my setup.

Many Laptop screens are in fact 6-bit panels performing dithering to fake an 8-bit output. This includes even high-priced workstations replacements, like the HP Zbook Fury 15 G7 and its 6-bit LCD panel, that I sit in front of right now.

This made me double-check the date of the article (it's from 2023.)

The author's laptop appears to have launched in 2020. I'm astounded any manufacturer would think this is even remotely acceptable this day and age, much less on such a high-end device. (Going off the current generation, these laptops start around $3k.)

Is this actually that common or did the author just get unlucky?

Another useful tool is https://www.learndmarc.com/ -- I found the presentation very helpful when I was finally getting on the DMARC train a while back.

I think a lot of people here are missing an important point here that Apple has always been fairly ambiguous about what their level of support is for older devices beyond major feature updates.

If it weren't for a friend giving me his old iPhone XS as thanks for a favor, I'd probably still be using my old iPhone 6s--and I would not have worried about it from a security perspective purely because (as the article notes) Apple is still releasing security fixes for iOS 15. I'd feel differently if Apple had publicly stated that all iOS 15 security fixes from now on will be on a minimum effort basis only.

I'm wanting to put serious effort into getting better at illustration, specifically figure illustration. I'm also planning to continue getting better at piano.

For your second goal, if you're referring to implementing your own ray tracer I highly recommend the Ray Tracing in One Weekend series: https://raytracing.github.io/

Thanks!