You don't like the new agreement? Pray I don't alter it further.

They were never yours, and zillions of people you don't know have access to them.

Using google search, will return roughly infinite recipe sites. The sites were generated to spam AI generated recipes surrounded by advertisements. None of them are really any good because they were generated by a script and not looked at by a human until I come along and click. The standard is for all recipes to have at least 10-15 screenfulls of vertical spam wrapped by ads for recipe pages. The internet, at least using Search, is now useless for food recipes. I would have better, faster luck driving to the public library and looking in a physical cookbook; at least those recipes were probably tested at least once by humans unlike the advertising spam sites. Nobody has 45 minutes to watch 44 minutes of filler material surrounded by ads on Youtube either. If you want to cook food, the internet is near dead at this time, unfortunately.

AI search will plagiarize the "Original Nestle Toll House" recipe from the back of every bag of chocolate chips ever made. Its a good recipe and I've baked them many times over the decades.

I wish the internet were more useful, but the people in charge of it don't want it to be useful; here have some ragebait and doomscroll while watching the ads.

1) I run my own systems in emulation and its always educational to see how other people handle configuration and sysadmin type problems. Much like programmers reading other programmer's code for educational purposes.

2) I have a genuine philosophical question which it appears I cannot answer by any means simpler than running it and trying it. Similar to the halting problem LOL. I wonder how the project handles operating systems like MVS/360 where there exists a perfectly good 1960s installation (which I have installed by hand from tape for the experience) however no one uses that IRL because the various MVS Turnkey projects provide seemingly infinite debugged and dependency organized patch sets. There's quite a difference between trying to white knuckle a homemade bare basic MVS/360 from the 1960s vs "MVS Turnkey 4" which basically just works out of the box.

Another example of #2 above is there's DEC PDP-8 OS-8 which technically boots... but the most common distro had a non-working but trivially fixable FORTRAN compiler (IIRC the runtime package filename was wrong or something similar). There's a lot of fun customization.

Another example of #2 above is I wonder how the author handles RSX-11M, distribute the ancient unpatched unmodified OS from DEC or ship something like the Billquist distro, or does the author ship the PiDP-11 RSX-11M (or is PiDP-11 shipping the Billquist RSX-11 distro now?)

I guess for people not into retrocomputing it would be like claiming some rando RedHat .iso from the 90s is "The" Linux operating system. Well, its "a" linux from one instant in time... Likewise there seems to be no "The" MVS/360 operating system there's a zillion possible local installs of all capability levels and eras, all very different and fun.

From the outside, the hard part of designing a chair is making a blueprint. At least making a blueprint looks hard to people who've never made one. According to outsiders, the next layer of the onion is perhaps inserting reasonable constraint dimensions for similar reasons.

From the inside, as a guy who's recreationally made furniture, the hard part is judgment about joint selection and design, experience with wood warping (all wood changes shape with the seasons, a good woodworker makes it look easy to work around and a bad one makes expensive firewood that rapidly falls apart). Another insider PoV is judgment about wood selection to get the correct balance of final finish durability and appearance. Finally working toward outer layers of the onion, its time to do parametric joint design decisions... What's the ideal number and size of dovetail joints for, perhaps, a drawer.

I've seen prints of chairs before I don't need a LLM to make one similar to the ones I've seen before and could probably make from memory (at least ones I built myself), the library has loanable books and woodworking magazines. I do see the attraction from the outside.

Consider something like a Windsor chair. The larger the wedge in the spindles the tighter and longer lasting the chair until you break something trying to force them in; there's a lot of judgment and experience in designing, selecting, and installing spindles, but none of it is written down so it'll be hard to train a LLM... Tighten it until it breaks then don't tighten it that much next time. Most super detailed plans for Windsors are for inferior machine produced replicas which are not necessarily useful for a fine woodworker and are not exactly what craftsmen would aspire to. People who want "a cheap chair" will buy a 4-pak of folding chairs from walmart anyway, not make a homemade Windsor-style chair.

Another somewhat more blunt example is for actual woodworkers the "problem" with hand cut dovetails isn't knowing what they look like or how to make a diagram of one, but gaining the experience behind a hammer and chisel to push your luck while cutting them as far as possible without going too far and turning the part into scrap. One unavoidable part of woodworking is I've turned quite a bit of wood into scrap on the last step; oh well make another. At least I can burn scrap wood to keep warm LOL.

Its kind of like from outside the programming fraternity the non-programmers think the only skills required to program are typing real fast and being very experienced at fizzbuzz during interviews. But that doesn't work IRL, from an inside-out perspective.....

The woodworking world is not exactly lacking for a library of "semi-decent" plans. An automated system to make enormous quantities of low quality unverified and untested plans would not really help the field, no.

The problem is people trying to get individual credit for merely running a script that spams a mailing list. Many of those people are likely not even C programmers or programmers at all.

Without the immense personal reward and recognition and job offers as a motivation, the problem will disappear.

The problem will also disappear with time as the people lauding and celebrating and hiring security researchers of the past will quickly abandon LLM generated spam as a positive signal; running a prompt that sends spam is, if anything, a strong negative indicator of infosec ability and skill.

LLMs are a tool. Like all tools, most people can't or won't use them responsibly or profitably although they are useful in the correct hands.

About 5M people, a fifth the population of Malawi, none the less are one of the top producers in the entire world for oats and barley. Not per capita... total. Wow. Note that only about 10% of the population farms which makes the ratio even crazier.

Finns as a whole somehow produce about 2x their entire countries body weight in barley per year which always freaks me out. The country is also one of the top 10, usually top 5, producers of oats in the entire world, and they're competing with giant countries like Canada and Russia. Giant Canada only produces about 3x as much oats as tiny Finland.

Finland climate isn't what you'd think of for tomatoes but they produce about three dozen tomatoes per capita every year, which is also weird to think about. Not just how do they grow that many tomatoes, but why? They like pasta sauce and pizza sauce that much?

However Finland is not massively wildly overpopulated with frequent famines like Malawi. Those conditions will annihilate a countries productivity, including ag productivity.

I rooted around in wikipedia and Malawi has FAR more people than the land can support. They have a top down demand they must grow maize although the land and climate are very unsuited for maize. Why? Unsurprisingly they have had severe recent famines unlike Rwanda. If they had capacity they could survive a minor shortfall in rain but they have more people than the land can support so the famines are very rough. They have about 3x the agricultural land as Rwanda but its not suited to maize but its demanded they grow maize. Maize will only grow with massive fertilizer imports which they cannot afford and occasionally politically/economically manage to totally screw up, alongside Maize is traditionally dependent on very reliable rainfall or post industrial era advanced irrigation which they don't have.

I would estimate the geography of Rwanda will support about 20M people, luckily they have about 14M. They can coast thru some rough agricultural times and they've developed enough industry and trade that they can import their way thru short term minor local problems.

On the other hand Malawi can only support maybe 15M people reliably, unfortunately they have about 22M. When the rains don't come or the politicians screw up the fertilizer imports, they die.

Its very difficult for them to "advance" beyond subsistence ag without enough to feed everyone and ag policies seemingly intended to be self destructive.

I don't know why they "have to" grow maize despite it resulting in starvation. Historically this type of thing is caused by someone making a huge profit or attempting to maintain control. Regardless of cause, until they can eat, they will not advance.

After eating dinner tonight they can dig a mine or build a factory. Oh wait there is no dinner tonight. Well then. And so they remain very poor, permanently.

The country, as a plot of land, is quite wealthy. $22B is a lot of money. If they had, say, 3M people as a population they'd be in position to become the next Taiwan. Taiwan's GDP per capita was about there in the mid 80s before they really took off. But they have over 20M people probably 30M soon, so they'll live in poverty, permanently.

In Rwanda an unusually good harvest means a new mine can be opened and they will "permanently" be richer. In Malawi an unusually good harvest means the people who would have starved to death this year now won't starve to death until next year. There will be no permanent improvement of anything in Malawi.

I would not be surprised to see double sided phone cases so we can carry our big brother phone with our real phone.

There is some prior art in people being forced to carry a "work phone" and a "personal phone" at the same time.

There will be strange product marketing effects. If you only carry one phone, you can currently talk people into spending over $1K on a high tier big brother phone. But if you only use a big brother phone for bank apps and only at home, a $1K phone from Apple or Samsung is a hard sell, I'd be more likely to spend $1K on a really nice anti big brother phone on ali express or whatever.

Start with

https://archive.org/details/cpm-primer-second-edition/mode/1...

Or this if you dare:

https://archive.org/details/TheCpmProgrammersHandbook/mode/1...

You can more or less only communicate with people agreeing with one specific tradeoff and the majority have spoken and they want slow long range texting, so you'll only be compatible with their mesh if you're compatible with that use case.

The software works fine if you set up super high bit rate, although you will not like the short range. There is no such thing as a free lunch and something like Y2K wifi speeds will have Y2K wifi ranges and battery use LOL. Also you will not mesh with other people's infrastructure if you intentionally use a modulation scheme they don't use. Its quite capable, really. But if most people want to max out their possible range and secondarily max out their battery life, it isn't going to be very fast...

This is my use case. There are no other options that don't demand something like cell phone coverage (LOL no) and cost $1K/node and maybe $50/month until you give up on the project. For hobbyists this is a total non-starter. Do you have a budget for satellite telemetry, LOL no.

With meshcore its more like $100/node and $0/month forever which is somewhat more affordable than the next cheapest possible competitor.

For a scientific-ish environmental sensor that generates a couple integer data points every hour or so, its vastly more than fast enough. My project is not far enough along to discuss beyond that and I may end up scrapping it for reasons totally unrelated to networking LOL. At least the networking side was beyond trivial to set up.

Very handwavy meshcore is meshtastic plus the lessons about digipeating etc that ham radio guys (like me) figured out the hard way back in the 80s/90s. So I have zero interest in reinventing the wheel with meshtastic and reliving the problems of the 80s in the 20s. I don't think meshtastic devs looked at prior art when they initially designed it, or they would have done things quite a bit more like meshcore.

There is approximately infinite interpersonal drama in both projects with all kinds of legal wrangling and much bike shedding apparently to prevent progress. I would not be surprised if TPTB are using funded LLM bots to disrupt those projects. Its pretty bad but as long as you stay away from the communities and socializing, both projects produce good code. I suppose for people that like that sort of thing, either project would be very attractive.

It takes some human effort to set up a slop generator. Have the slop generator make 100 buckets of slop, humans will work hard accepting or rejecting the buckets, somewhat less than 100 buckets will be approved, the payoff for the owner of the slop generator is now they have "verified FOSS developer contribution" on their resume which translates directly into job offers and salary. Its a profitable grift, profitable enough that the remaining humans are being flooded out. The ban makes successful submission to Redox even MORE valuable than before. They can expect infinite floods of PRs now that a successful PR "proves" that Redox thinks the human owner of the slop generator did the work and should therefore be offered more jobs, paid more, etc. Technically, they're hiring and paying based on ability to set up a slop generator which is not zero value, but not as valuable as being an Official Redox Contributor.

In the long run, this eliminates FOSS competency from the hiring process. Currently FOSS competency and coding experience indicates a certain amount, however minimal, of human skill and ability to work with others. Soon, it'll mean the person claiming to be a contributor has no problem violating orders and rules, such as the ones forbidding AI submissions, and it'll be a strong signal they actively work to subvert teams for their own financial reward and benefit. Which might actually be a hiring bullet point for corporate management in more dysfunctional orgs, but probably not help individual contributors get hired.

I could see some logic in not putting cams pointing forward because theoretically the pilot is looking where they're going and not putting one facing back because flight time to impact is so low they can't evade anyway, but a side attack is survivable if detected early enough... Also facing back they're going to be "seeing" their own exhaust most of the time.

The total non-reaction by the pilots in the public videos would indicate that if those planes even had -57s they were not working or not working well enough to matter or not working fast enough to matter.

I would agree some monster sized BVR missile will be easier to detect. In practice does it matter if the missile detector works at short range if the attacker would likely be in guns mode at short enough range anyway?

There's open source intel on google that Iran has SU-27s. Under combat conditions you have an instant to tell them apart. Clearly, its possible to misidentify them at least one time historically as the F-15s did get shot down.

I can assure you from having flown around a lot, if you are wildly outnumbered 3 SU-27 (err, F15) to your 1 F-18 you do not attempt a radar lock you do an IR only attack. The article mentions getting a radar lock first but that is unnecessary for IR guided weapons and in a 3-1 situation will just get you shot down.

Waiting for confirmation from the ground means 1 of the 3 will surely notice and you will be shot down.

Ironically if it were a flight of 4 F-18 they'd probably not have been as skittish at radar locking a mere 3 aircraft and the IFF (assuming its probably configured and working etc) would have informed them they're friendlies. IFF can only tell you if everything on both sides is working perfectly and powered up, if you don't get a friendly response all you know is it didn't work. Not unlike a network ping command. If ping works you know they're up and accepting pings from you, if ping doesn't work, you don't really know anything for sure.

Possibly the primary fault was the Kuwaiti lack of situational awareness. Somehow he's in shoot down range of three other A/C and he's got maybe 3 to 5 seconds to shoot them down or be shot down himself.

Somehow there is no discussion on what both A/C were doing. Usually a landing on an airfield would not look like a bombing run but possibly the F15s were doing something "weird" for which they could be blamed. The total censorship of what they were doing points to them being up to something dumb "lets buzz the airfield during active combat would could possibly go wrong" and they get shot down for looking like an attack run. Or a mix up where there's a published ahead of time safe altitude window around 15K but these guys for who knows why were 1000 feet off the ground doing who knows what. Maybe they had a good tactical reason to do it but its damning that nothing is being reported as an excuse.

Clearly any passive IR detector thats theorized to exist for years either doesn't exist or doesn't work very well. In theory, a smart enough IR camera should be able to notice something very warm indeed is getting rapidly brighter as it approaches you. In practice, these don't exist, or don't work. "Oh yeah they didn't have those when I was in, but they totally have them now" for the last 30 years. Apparently, not yet in 2026.

I find it unfortunate that people who do this for a living can't legally comment, people who do this for a hobby are not asked or actively ignored despite extensive practical experience, and people who mostly have a grift of looking authoritative for legacy media get automatic blind belief despite sometimes spouting total nonsense. This is the typical journalistic response in ALL disaster situations not just military aviation.

Typical markup in the USA is 100% from wholesaler to retail. Running brick and mortar is very expensive. So if Walgreens were selling this, the wholesale price would be $1.25. I think it reasonable to expect the Yakult Ladies are pulling in the same $1.25 per package that walgreens gets.

The key, I think, is "Most of them are self-employed". Its a gig economy idea. You have to eat. If you're walking home from the store anyway (or kids school or on the way home from work or whatever), you may as well deliver packages for $1.25 each on the way home. You're walking home anyway, you may as well make free money on the walk.

Note: FIPS181 was intended for passwords and I was using them as handy short human-readable record IDs as per your post. You probably shouldn't use FIPS181 for passwords in 2026 LOL.

Describing FIPS181 as pronounceable is optimistic. However its better than random text wrt human conversations. They start looking like mysterious assembly language mnemonics after awhile.

Basically, who runs golang?

The perfectionists are correct, UUIDs are awful and if there's a pile of standards that all have small problems the best thing you can do is make a totally new standard to add to the already too long list.

The in-the-trenches system software devs want this BAD. Check out https://en.wikipedia.org/wiki/Universally_unique_identifier#... They want a library that flawlessly interops with everything on that list, ideally. Something you can trust and will not deprecate a function you need for live code and it just works. I admit a certain affinity to this perspective.

The cryptobros want to wait, there is some temporary current turmoil in UUID land. Not like "drama" but things are in flux and it would be horrible for golang to be stuck permanently supporting forever some interim thing that officially gets dropped (or worse, under scrutiny has a security hole or something, but for reverse compatibility with older/present golang would need permanent-ish reverse compatibility) Can't we just wait until 2027 or so? This is not the ideal time to set UUID policy in concrete. Just wait a couple more months or a year or two? https://datatracker.ietf.org/doc/html/rfc9562

I think I covered the three groups that are fighting pretty accurately and at least semi fairly, I did make fun of the perfectionists a little but cut me a break everyone makes fun of those guys.

So, yeah, a "small technical bit" but its actually a super huge architectural / leadership / management decision.

I hope they get it correct, I love golang and have a side thing with tinygo. If you're doing something with microcontrollers that doesn't use networking and you're not locked in to a framework/rtos, just use tinygo its SO cool. Its just fun. I with tinygo had any or decent networking. Why would I need zephyr if I have go routines? Hmm.

I've been around the block a few times with UUID-alike situations and the worst thing they could decide is to swing to an extreme. They'll probably be OK this is not golangs first time around the block either.

It'll probably be OK. I hope.