Huy's Wiki

greg-isenberg-fable5-banned-takeaway

2 min read

Greg Isenberg — The Takeaway from Fable 5 Being Banned

  • Author: Greg Isenberg (@gisenberg)
  • Source: LinkedIn Post
  • Tags: greg-isenberg, claude-fable-5, local-models, regulation

The post

The takeaway from Fable 5 being BANNED by the government: GET GOOD AT LOCAL MODELS SO YOU HAVE 100% CONTROL.

My entire weekend was going to be building my craziest ideas with Fable 5. That’s now cancelled. So instead, I’ve decided I’ll go deep on local models.

The lesson from this ban is basically: don’t build your entire workflow on something that can disappear with a single letter. Own part of your stack. Local models are insurance.

It reminds me of when people realized they don’t own their social media accounts.

Greg also teased a related episode on The Startup Ideas Podcast.

Discussion

The 176 comments were split between agreement and skepticism about local models being practical:

  • Alec Kremins: “Every time I build a workflow on an API, I feel like it’s just a timer until an access key gets yanked. Local models are a headache but at least they can’t repo your compute at 3am.” Adds: the control that matters is being able to swap any model out without breaking your stack — route across a few depending on the job.
  • Tom Lybeert (skeptic): “The economics for local models is total crap. Opus 4.8-level — forget it, there’s no open-source model at that level… you’d need 8× H200 for memory requirements.”
  • Another skeptic: It costs six figures of server architecture to even approach Opus/frontier quality at small scale; calls the take “clickbait” but concedes smaller models are useful for simple tasks.
  • Patrick Mork: Took a different angle — the deeper shock was how easily a government can restrict a tool immigrants/businesses depend on.

0 items under this folder.