Not only that, but iOS 18.7.8 actually seems to be available to devices capable of running iOS 26 without any workarounds, unlike 18.7.3 through .6. It makes me wonder if those intermediate releases really were supposed to be available but weren't due to some issue on the distribution side that no one bothered to fix.
Very serious vulns were being exploited in the wild, I think that's what forced their hand. I don't think Apple ever had a discrepancy like the one with iOS 18.7.3 through .6 being held back.
For those on iOS 18, beware that the update to iOS 18.7.8 will toggle Automatic Updates back on. Make sure to switch it back off so you don't wake up to a nasty surprise when iOS 26 is non-consensually forced onto your iPhone.
I think that was another attempt by Apple to push users to iOS 26, but after seeing how many people with compatible devices refuse to upgrade, they finally caved in and provided an update.
They caved, but they're still pulling out new tactics to trick users into installing iOS 26.
The new iOS 18 update will _also_ toggle Automatic Updates back on. I had it happen just now on my 13 Mini against my will. I had to go back into settings and very carefully navigate to disable automatic updates.
Interesting. Judging by the time of your post I assume that you're American. I'm in Europe and automatic updates stay disabled for me. I just upgraded 3 devices without any problems.
There seems to have been a change of mind, maybe also due to the severity of the exploits. The non-availability of security updates for models that are upgradable to a newer major version has been Apple's practice for many years now.
The way major upgrades are presented in the Settings UI makes it clear that users installing these security updates while not upgrading to a newer major version do so very intentionally. So Apple is now supporting these users deliberately.
> one of two goats that was chosen by lot to be sent alive into the wilderness, the sins of the people having been symbolically laid upon it, while the other was appointed to be sacrificed
Let me get this straight: in the Bible, the scapegoat does survive, while the "pure" goat that did nothing wrong gets killed? That's... messed up, even for a tribal rite.
Honestly, this is HN and founders should pay attention to this. People don't want to host their own shit, they want a one-click easy switch. All of these alternatives have baggage.
This is your chance to start Bluesky for discord. A competently built, VC backed competitor to exploit a misstep only caused by government overreach due to their colossal market share. 26 million daily active users is a nice guaranteed market to start whittling away at, with an effective marketing campaign to drive a wedge between "little gamers, and big corporate enshittification."
How would you avoid the same problem that discord ran into that made them require ID verification? I doubt they're doing this for fun. Incorporate in the Bahamas?
the largest block of discord users are from the US which hasn't got id verification laws regarding age for social media. The 2nd largest is brazil, which does, and the 3rd is India, which doesn't.
So they are forcing users from countries that haven't passed these laws to abide by them. They don't have to do this, they could just require brazilians use face-id.
I don't think I would need VC to get off the ground.
I keep coming back to the gigantic headache of content moderation, and it gives me pause not to do it. There are some truly terrible people who will try to tear the platform apart.
I think automatic moderation is one of those golden use cases for LLMs. You can use cheaper inference models, and maybe some clever sampling techniques to limit the token expense.
Thinking out loud, I'd be surprised if this isn't a startup already.
What successful mass market service is self hosted[0]? We're in an endless cycle of cool new service suffers enshittification and abandoned. I'd love to break the cycle, but self hosted hasn't had a lot of success.
[0] Self answer: Maybe crypto and email would be the best examples, and neither of them are fantastic examples.
> Honestly, this is HN and founders should pay attention to this. People don't want to host their own shit, they want a one-click easy switch. All of these alternatives have baggage.
I mean, come on, this is, what, a couple hours of vibe coding, max?
Let's go AI bros on HN. Chop. Chop. ... Wait, why am I hearing crickets?
For those who don't get it, yes, I'm being sarcastic. It isn't that easy to code this, but the problem isn't coding or even deploying.
The problem is your manual service. Logins are a pain in the ass and chew up sooooo much of your customer service time. Then there are the griefers. Then there are the spammers. Then there is law enforcement compliance (in spite of what HN says, you DO have to comply with local laws). etc.
All that costs time which equates to money.
I was once talking to someone who made a point that Discord specifically tries to hide IPs so that people playing a game can't DDoS their opponents. o_O! At that moment, I realized that I simply can't imagine all the malevolent behavior that Discord withstands.
The improvements are solid! I think 5x6 was the right call...it's a good balance of being able to reuse strategies from 5x5 but also having to develop some new strategies.
Just note that listing is for an item from a third-party seller. Walmart's website includes listings from their third-party marketplace unless you explicitly filter them out.
> I've seen codebases that enforce these commit prefixes such as "chore", "feat", "bugfix" etc. Is there any real value to that?
It's a choice some teams make, presumably because _they_ see value in it (or at least think they will). The team I'm on has particular practices which I'm sure would not work on other teams, and might cause you to look at them with the same incredulity, but they work for us.
For what it's worth, the prefixes you use as examples do arise from a convention with an actual spec:
Just because someone put up a fancy website and named it "conventional" doesn't mean it's a convention or that it's a good idea.
The main reason this exists is because Angular was doing it to generate their changelogs from it. Which makes sense, but outside of that context it doesn't feel fully baked.
I usually see junior devs make such commits, but at the same time they leave the actual commit message body completely empty and don't even include a reference to the ticket they're working on.
> Or otherwise you can enable the app exposé feature to swipe down with three fingers and it will show you only windows of the same app.
If you have an Apple keyboard, CTRL-F3 (without the Fn modifier) will do the same. Not sure if there are third-party keyboards that support Mac media keys, but I'm guessing there are some at least...
Welp, now that there is confirmation that lawyers are involved, the chances there will be any of sort of open and transparent reconciliation process have plummeted.
Er...FYI, your [2] link is to a discussion about an article written by the person to whom you are responding.
Personally, I think the reason this post about gem.coop has been flagged is that we've reached the point at which new HN threads about things related to the recent RubyGems shake-up quickly devolve into people rehashing the DHH "aspect" of it all. So it has become less about flagging the actual target of the post and more about flagging the parts of the discussion that seem to go nowhere.
That's fair enough, I didn't actually notice. Regardless, I was offering the information for other readers, which may or may not include the person I'm replying to.
Edit:
> flagging the parts of the discussion that seem to go nowhere
This is and isn't what actually happens, though. People do flag the parts of the discussion that don't go anywhere but then people also flag the post itself because they think there's no reason to discuss it at all for the fact there's a vocal part (minority or majority doesn't really matter) that wants to discuss a topic that's not going anywhere.
People shouldn't flag the post itself just because it's likely to gather or even has gathered a crowd that will discuss such directionless topics when there are better topics to discuss, even (especially?) if they're not currently being discussed.
reply