mcpeepants

circumventing? that's regulatory agility, baby!

The app ecosystem argument is totally valid, yeah. Paying to get access to that makes sense if you and the people you are sharing with benefit from that.

I guess I view the server-side as mostly fungible, because me and all the people I share with are more technical, have a separate media player (Apple TV etc), and are either light users content with the Jellyfin app, or use a third-party app like Infuse on iOS. I look at the media server software as more like a "media fileshare with metadata and easy user management", but I get why that's not the case for everyone.

Honest question, I haven't looked in a while - what does Plex offer over Jellyfin that would make it worth a monthly payment, or even $250-$750 one-time? When I ran the calculus a few years ago I came up empty.

I just replaced a T530 with a T14 gen 1 (R7 pro), and…yes. Super happy with the upgrade, for less than $300 mind you, even though I still love the old thickpad. It will live out its years in the rack, taking up an impressive amount of 1U.

Exactly this! After ~3 years I rarely receive an email with the Gmail tag now that all contacts/services have been switched over (or unsubscribed). Fastmail is easily my most valued paid service, and yet I never have to think about it. Just works very well.

why assume the billing model is being imposed by the customer rather than the service provider?

> hyper-malleable control surface [...] (the stream deck is popular for a reason!).

I agree with the sentiment - making a control surface that adapts to the user's current task makes total sense to me, and is a compelling feature in theory.

The execution (and how the touchbar differs from the Stream Deck) is where I think the argument falls apart. There is effectively zero ability to navigate the touchbar without using your eyes and taking your focus off the display, and your work. The Stream Deck can easily be used without looking. A static grid of real buttons whose function changes within context is a more useful implementation in the real world, even though it is technically _less_ capable.

IMO the touchbar concept is flawed in exactly in the same way as the modern car user interface.

could it be that game mode is attempting to run the game in compat mode even though you are running the native build?

This works:

  $ZAI_ANTHROPIC_BASE_URL=xxx
  $ZAI_ANTHROPIC_AUTH_TOKEN=xxx

  alias "claude-zai"="ANTHROPIC_BASE_URL=$ZAI_ANTHROPIC_BASE_URL ANTHROPIC_AUTH_TOKEN=$ZAI_ANTHROPIC_AUTH_TOKEN claude"

Then you can run `claude`, hit your limit, exit the session and `claude-zai -c` to continue (with context reset, of course).

they put a special coating on the model to discourage this behavior

> Most frameworks also by default block ALL environment variables on the client side

I’ve been out of full stack dev for ~5 years now, and this statement is breaking my brain

The incentive seems very thin/weak. Pay extra now to push DP adoption and hope that in ~10-15 years you can drop the HDMI port? Meanwhile you still pay the cartel, and they invest your money directly against your interests. And it all hinges on predicting consumer adoption which is nearly impossible. I honestly don’t see how they could justify making such a step in that direction let alone a significant one.

wireless charging at the expense of size/bulk

why would the tool minify the script it generated?

or just keenly aware of their own strengths, weaknesses, and time budget for this? the leap to “over scoping” is wild.