Louis Ingenthron @LouisIngenthron@social.cleverlibre.org

@kidkilatis@mas.to Would be pretty easy since it's not actually an upwards shadow. It's a near-horizontal shadow from the top of the mountain, which is above the clouds.

So, that's consistent with the long shadows we already see at sunset. Which aren't contradictory with the flat-earthers' nonsense.

@AriCohn I'll second this one. They're a bit pricey, but they're absolutely delicious!

@freemo *suddenly the alt-center army turns against itself, as former comrades draw hard lines against each other for having hard lines*

@freemo Wtf is "alt-center"?

"Oh, we want to demonize and restrict the rights of someone, but we just can't make up our minds about who to do it to..."
😆

@mmasnick @JLab8 Pretty sure all CL emails go through their servers for spam checking. So, you'd never have seen it if it didn't have this text to avoid the filter.

Same reason they want you to email a different address.

@_dm @WalterShaub@journa.host Interesting. By applying it only to IP-based providers, they can cut the implementation time down significantly. That sounds like a great call by the FCC.

@WalterShaub@journa.host That's not really true. They built the product in the 1800s, long before anyone even thought of caller ID. The protocols were built and expanded with backwards-compatibility in mind to prevent old phones from becoming obsolete. It was actually done with the customer in mind! And, if I recall correctly (I could be wrong about this one) that old protocol is essentially mandated by law to allow for interoperability, which means upgrading is also a government battle.

The problem is that modern phones have outgrown that system, but changing it would still make any phone that can't get an instant update (including smartphones that are no longer considered "supported" anymore) obsolete again.

Not to mention that it could involve setting up billions of dollars of physical infrastructure to have each line identify itself at the source.

Then you have to consider how that plays with international phones that don't follow the same rule.

I honestly don't think there was any malice here. It's just the age-old battle between something new and better vs supporting folks' old sunk costs.

@WalterShaub@journa.host *They* aren't inflicting these consequences, though. Third parties are.

Ultimately, it's a flaw in the protocol itself. The "calling from" number is self-supplied, not automatically detected like it should be.

Any attempt by the phone companies to correct this would result in a wide array of false positives, preventing (for example) grandma from getting her robocall that her prescriptions are ready.

Unfortunately, this is just one of those problems that would require a major underlying infrastructure change that nobody wants to pay for.

@saint11 Sure. The UI layout systems take some getting used to, but especially in the new 4.0 beta, they're pretty flexible and extensible.
Godot's style prefab system also makes iterating UI styles extremely easy.
Moreover, Godot's scene prefab system allows you to drill into UI elements and work on them individually, then go back out and see your changes on the whole. It works great for entire menus and windows as well as individual controls.
The biggest downside to Godot so far is the inability to link Node parameters in the editor. References to child elements need to be defined in the code, by hierarchy name, rather than set in the editor itself.

But most importantly, I've found it's incredibly easy with Godot to just get things to work very quickly so you can start testing out the meat of your concept. For UI/narrative heavy titles, that should be a godsend.