Glyptodon

But it would be too inefficient for you to compute with it locally. Thinks of all the AI companies that will be harmed by your vehicle's RAM usage! /s

Not only were taxi drivers not popular but it also wasn't and isn't obvious to most people exactly how or why they were regulated. Especially to people outside of major urban areas.

I do not think this will hold with nursing.

Normal VS code doesn't even use Cursor Marketplace, right? The way this is reported lacks clarity. Do people using plain CS Code even use the Cursor Marketplace? Or am I missing something?

I think the timing is unlucky - the E Holmes movie really ate the pie it might have otherwise had.

I think the data center hate is widespread, popular, and rather uniquely non-partisan.

I don't 100% understand it, but it seems to be driven partially by AI hate, and partially by bad experiences and stories making the rounds, like backup generator exhaust and noise making people nearby angry.

BI tools have always been borderline easy to replace IMO. So long as you have a decent data layer.

Eh, there are a lot of anti-Trump and "liberal" gun owners, but I think nearly all of them know that if they go all violent and rogue against this admin it's only going to be used to justify much worse.

I'm kind of curious if New Yorkers will try and do a tea party impression with the Russian diesel ship though.

Admin, maybe merge with submission: https://news.ycombinator.com/item?id=50187248

So does this mean sicking refrigeration islands in key locations will be the way to stop permanent coral bleaching?

Some of them support multiple passkeys and somehow I've now got three different ones for the same site in my password manager...

Wealth gaps and parental behaviors with respect to regulating screen time.

There's something going wrong in the US at least with elementary age kids that makes me pretty dubious about this unless your expectation is that everything splits into an underclass and an over class with the underclass eventually being replaced by robots and AI before dying out or something. And I really hope that's not what you mean.

To be honest this reminds me of interview leetcode. Like I remember one where you could get constant time if you made nested hashtables covering character sequences that might have made sense in USCII but probably would be impossible to maintain in UTF. In general leetcode problems love goading you to treat the ASCII character space as constant time to deal with and it's stupid. And it seems very similar to this.

I think this is exacerbated by how inconsistent exercising the capabilities can be.

If chargebacks were guaranteed, I might agree. But if you clickjacked with an instant checkout button, be ready for some scumbag to refuse to cancel your order, try to get you to agree to restocking fees, your card company to make you send them the same emails and complaints multiple times, and multiple phone calls...

I actually think this is an example of where government should be more involved - like often times if I file a chargeback, there's a solid likelihood that there should a real world repercussion to the other party because it's probably related to fraudulent or abusive behavior.

How do countries like India and Brazil do it then if it's so hard and challenging that it couldn't possibly be a public service?

I mean there are options. It's not like people in Brazil or Europe can't make electronic payments. That said, I do think the US is very prone to public services being made worse and poison-pilled on purpose.

I do think we're getting to the point that middlemen don't have much value add. Economics even suggests they don't add value I think. Possibly neutral markets, payments, and logistics should just be a public service.

So close but so far... The subdomain aliasing is neat, but it looks like you still have to create folders manually and also manually configure anything you use as a sending address at the point that you need it.

I've long wanted a service where every address is routed as a virtual folder as part of one shared domain level inbox for my personal domain. So I don't have to +alias so much or put up with the blocks some sites have on +aliases. E.g. if I shop at Safeway, I can give them <[email protected]>, if I log in with Google, I can make the Google account <[email protected]>, etc. Then I want the ability to create labels for actively used inboxes, for example if I have a Costco account, <[email protected]>, I could give it ans the Safeway email a shopping tag and have that is a secondary inbox, i.e. a hierarchy like <all mail>, then grouped boxes like <shopping>, then select individual inboxes, and finally a catchall inbox for any other inboxes.

I kind of have Google setup this way, but it's a friggin pain (and not really advised) to keep adding address aliases, or having to fight to +alias stuff. So it doesn't quite work.

Yep. They could be creating sandbox environments and training systems that make the operational actions being exhibited impossible, disincentivized, and more. But I guess that would be too much trouble and not give them as many marketing opportunities. Either way, liability should be on the company. And scaled against what individual perpetrators would be punished with.

I always assumed the fingernail edge thing had to come from a popular library or something.

People want this to be a "just one thing explains it all" situation. But it's like the unholy intersection of multiple things.

Parents are getting worse at being parents, or don't have the time for it. Technology and social media don't help. People have less stable lives. And less support systems. Schools have more complicated trust and financial situations. And more.

I don't know about "cured" but I've been cancer free for something like ~27 years. With childhood cancers some of them have very high rates of "cure," but it is true that the impact of the treatments (at that time at least) follows you for life in various ways. The more modern immunotherapies and such seem potentially much better than chemo if they can be turned into successful and consistent approaches.

I think there's a nuance gap here. Many of us, if offered, would be happy to live for a a millennium or two if we'd stay at worst middle-aged. But there's a giant gap between being willing to take that offer if given, and a desire for it being a big personal motivating factor.

I think there's at least one thing that MCPs get right, and it's that they make it easier to establish permission boundaries when agents are working with third part services and applications. Even with Claude from the terminal, MCP makes it easier for folks to standardize separate permissions and operations for general agent use than making people have to have multiple complicated API keys. Do I think it's the best solution for that? Not really, but I think it's probably better and on average safer than giving agents unfettered access to credentials to do anything, which seems like it'd be the default without MCP. That said, I can see MCP being replace with some sort of permission and sandbox system that's more generalized.

I think my gripe is less that it exists and more so that it's not a negotiated agreement. I think it should only be allowed if the contract was negotiated between two parties with full authority to offer any terms in the negotiation. If it's a standardized, take it or leave it, contract where one party has no opportunity to offer alternative terms that get proper and full consideration by the other party, it shouldn't be allowed. In most of the examples you give, they are contracts that have been clearly negotiated between parties, not click-wrapped take it or leave it, my way or the highway, terms.

So should guilty pleas, nondisclosure agreements, and trials where juries can't decide on degree rather than prosecutors.