I'm a Pocket Casts user, and see that it was one you tried.

Pocket Casts lets you select the episode order (as well as do things like group by season). I think it's pretty common to be able to add RSS feeds by putting them in the directory search field, and PC does this as well.

I've had absolutely zero problems using Pocket Casts to add custom Patreon feeds, and to listen to episodes in the other they came out.

That's what Android does. Desktop Linux should make this easier.

The problem is that the old owner still has a valid certificate for some period of time.

Except this is going the wrong way. We should be discouraging frequent domain ownership changes not making them easier. New owners getting visibility into traffic meant for the old owners is as much if not a bigger problem.

At the end of the article, they talk about how they've since updated to the latest major version of pnpm, which is the one with that change

I think they're agreeing with you

This approach can't inform you that someone in the feedback chain is causing a problem.

Yup - they touch on proxy relationships where you have a few trusted reporters to break the crowd into cohorts that you can mentally simplify but whenever you do this you need to accept that it won't be complete. You should expect and make room for occasional noise from the fifty people behind your one trusted reporter because the problem could always lie with the reporter themselves.

That's opting into immutability, the point of the experiment is having it by default. Plus, that's just the type system preventing you from adding a property. It won't stop you from trying to change the `immutable` field.

I'm genuinely curious, was this AI generated, or just a lack of understanding?

No, you're the one that's incorrect, typescript blocks mutations when you use Object.freeze too: "Cannot assign to 'immutable' because it is a read-only property. (2540)"

You can also use "as const" to get the same behavior without any runtime calls:

    const exploring = { immutable: true } as const
    exploring.immutable = false
              ^ Cannot assign to 'immutable' because it is a read-only property.(2540)

But yes, OP wasn't referring to the article, they were just pointing out the narrower fact that Typescript does in fact have compile-time errors for mutating Object.freeze's return values.

If you read their previous article about AWS (linked in this one), they specifically call out root cause analysis as a flawed approach.

It was Fitbit, but otherwise, yeah

I think Eric has more-or-less implied that they will probably make a Pebble Time Round successor (no doubt with worthwhile battery life this time, given how much more the Duo is)