The flight distance is 2,520 miles, Google puts road distance at 3,179 mi = 1.26x, 29,905 mi is 11.87x. Road miles are not even close to accounting for it, it’s just a bug.
Being a little bit clever can lead you to make some pretty bad mistakes.
Yes, the distance according to roads can be different from the distance as the crow flies. No, it cannot realistically be 10x the distance when the crow's distance is 2500 miles.
You would have to take an implausible number of wrong turns to have a chance of making it anywhere near that long a drive. For an example of a shorter but still entirely unreasonable path: Head straight north all the way to the pole, continue south to the pole, continue north to the latitude of the destination, then head due east until arrival.
> There's no reason that an LLM couldn't (or isn't) being trained on commit messages.
You are arguing that it could. Hypotheticals.
But getting back to reality, today no coding assistant supports building system prompts from commit history. This means it doesn't. This is a statement of fact, not an hypothetical.
If you post context in commit messages, it is not used. If you dump a markdown file in the repo, it is used automaticaly.
What part are you having a hard time understanding?
You seem to be confusing the construction of system prompts with "training". Prompts do not change a model's weights or train them in any way. Yes they influence output, but only in the same way different questions to LLMs (user prompts) influence output. Just because it's not available in current user interfaces to use commit messages as a prompt does not mean the model wasn't trained with them. It would be a huge failure for training from version controlled source code to not include the commit messages as part of the context. As that is a natural human language description of what a particular set of changes encompasses (given quality commits, but quality is a different issue).
> But getting back to reality, today no coding assistant supports building system prompts from commit history. This means it doesn't. This is a statement of fact, not an hypothetical.
This is a non-sequiteur. Just because coding assistants don't support building system prompts from commit history doesn't mean LLMs and coding assistants aren't trained on commit messages as part of the massive number repositories they're trained on.
> As a side note, it's becoming increasingly important to write down this info in places where LLMs can access it with the right context. Unfortunately commit history is not one of those spots.
This is the comment that spawned this tragedy of miscommunication.
My interpretation of this comment is that no current programming agents/llm tooling utilize commit history as part of their procedure for building context of a codebase for programming.
It is not stating that it Cannot, nor is it making any assertion on whether these assistants can or cannot be Trained on commit history, nor any assertion about whether commit history is included in training datasets.
All its saying is that these agents currently do not automatically _use_ commit history when finding/building context for accomplishing a task.
There are MCP Servers that give access to git repo information to any LLM supporting MCP Servers.
For example:
>The GitHub MCP Server connects AI tools directly to GitHub's platform. This gives AI agents, assistants, and chatbots the ability to read repositories and code files, manage issues and PRs, analyze code, and automate workflows. All through natural language interactions.
This is hair-splitting, because it's technically not a part of _system prompt_, but Claude Code can and does run `git log` even without being explicitly instructed to do so, today.
I have the impression that it is indeed broken, but even if there was a worldwide generational effort to fix it, USA would stubbornly remain in their old ways as a matter of national pride.
Yes, much more severe. Covid alone had a higher fatality rate than Spanish flu. 2012 MERS had a 30% fatality rate. Ebola strains in Zaire and Sudan have had fatality rates over 50%.
As for those other diseases there is zero evidence that climate change has made them more severe. It's not impossible but we simply have no reliable evidence of a causal relationship one way or the other.
Forking ACF is not the issue, automatic is perfectly within their rights to do that. Hijacking the ACF WordPress.org page and having everyone who uses WordPress.org for plugin updates to auto update to the fork is the problem.
is it a hijacking, if they own that page in the first place? The community placed trust on that owner of the page to be impartial, which was shown to be false here of course.
This means that this community page/list should no longer be trusted, and an alternative be sought out.
IANAL, but the only expressly illegal thing that they seem to have done is maintain the "acf" tag, and used the "advanced-custom-fields" URL, which could be trademark violations.
I'm sure there are other laws that are relevant here related to deception and misuse of the subscription to the plugin updates by the 2 million users involved.
Legal issues aside, this is an extreme erosion in trust for any user of the WordPress.org platform. They can no longer have confidence that their commerical (or non-commerical) plugin won't be chopped up and have its users stolen at any moment.
> Legal issues aside, this is an extreme erosion in trust for any user of the WordPress.org platform. They can no longer have confidence that their commerical (or non-commerical) plugin won't be chopped up and have its users stolen at any moment.
Not just the plug-in creators, but those (“stolen”) plug-in users, too. There is an example in TFA, the guy who had to update many (150, IIRC?) of his customers’ sites after the plug-in was switched out from under him.
> is it a hijacking, if they own that page in the first place? The community placed trust on that owner of the page to be impartial
I would say yes, it is hijacking. It is very very similar to any MITM attack ever, like anyone in the looong chain of trust deciding that they will do something with the trust they have. Like, can your ISP redirect google.com to their own google.com? They surely can, and it probably wouldn't even break their contract with you. It would be a trademark infringement, probably GDPR violation, but not much else.
Since WordPress.org acts as a traditional package repository, they can: serve you the package, or don't serve you the package for various reasons. Everything else is hijacking or worse, especially if the intent is just to turn you their user, and the result is to break your website. Even if you don't have a contract with them that they will serve WP Engine's unmodified plugin to you.
I still use the alarm clock that I was given when I was 11. The iPhone alarm will sometimes just go off silently (I've watched it happen), which is my most hated "feature".
When I moved to Sweden in 1998, I bought an radio alarm clock with a wire to plug it in and big red numbers. Big softly glowing red numbers. Easy on the eyes. I got a little discount because the cover for the battery was missing and I was a poor student at the time. But because it was going to be plugged in, I did not care about having a battery. I've since moved country four times but this thing is still next to my bed. I love being able to glance at it at night with a half open eye and know what time it is. That's it's only function. I don't use the alarm very often and if I do, I use my phone for that. And I haven't listened to the radio in well over ten years. It's the clock that is important to me.
> iPhone alarm will sometimes just go off silently
Oh man, as a recent android to iOS convert I thought I was just doing it wrong. The alarm feature of this phone is utterly useless it’s so unreliable. It just decides randomly (from what I can tell) to silence itself with no user interaction. Luckily it hasn’t resulted in major life consequences yet, but I’ve learned to not even bother with it.
Thanks for returning a tiny bit of my sanity!
Whichever programmer or team was responsible for this “feature” that decides you know better than me, why?!?
My current conspiracy theory is it’s the wearables team since then only way to be certain you will at least get some physical/audible feedback it’s time to wake up is by wearing your Apple Watch to bed. Then you get to deal with frantic charging it before your flight or whatnot, fun times!
After my wife stole (back) her high school alarm clock I wasn't satisfied with the replacements. But I picked up an old one for $0.25 at a market festival recently and am pretty happy with it.
I recently had my alarm clock I was given when I was a teenager fail on me, 30 years later. Even when plugged in, it occasionally turns off. Got a few good decades out of it, though.
Always these pesky capacitors (I had like 3 LCD monitors with a faulty capacitor from prolonged use, it is somewhat of an easy fix, no need to throw away the whole monitor).
I've been an iPhone user since 2016, Android before that. After the first few times I encountered the silent alarm problem, I would make sure to unmute the phone before bed, and also max out both the alert volume control and media volume control, simply tanking the sound of the alerts during the night hoping that the alarm would work. Even doing this, I would still watch the alarm go off silently.
I'm convinced that this was one of the reasons that the sleep schedule app was created, because they wanted to see if a different team wouldn't introduce the same bug.
Nerd sites were screaming about it, extensions existed to remove them, for the reasons you say. The web devs generally knew this was an issue but the clicks were more important. I don't pity them.
Ignorance is no excuse. Don't dump loads of third-party JS onto your site without understanding what it does. That's negligence.
If Facebook misrepresented what the code (or whatever) Patreon included was going to do, sure, ok, fair. But then in that case Facebook should be the target of the suit. (Unclear who should sue whom, though... users sue Patreon and Patreon sues Facebook? Users sue Facebook directly?)
> JS onto your site without understanding what it does. That's negligence
Everybody understood what it did. It was legal at the time. Then it was made illegal. The lawsuit literally retroactively includes the period in which it was legal.
If you put all of your blood vessels end to end they would go to the moon and back.