<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Llm on FTRCRP</title><link>https://ftrcrp.org/tags/llm/</link><description>Recent content in Llm on FTRCRP</description><generator>Hugo</generator><language>nb-NO</language><copyright>2026 FTRCRP</copyright><lastBuildDate>Sat, 25 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ftrcrp.org/tags/llm/index.xml" rel="self" type="application/rss+xml"/><item><title>The Fallback Stack: Running Local AI So You Can Lose the Frontier and Keep Working</title><link>https://ftrcrp.org/guides/local-llm-fallback-stack/</link><pubDate>Sat, 25 Jul 2026 00:00:00 +0000</pubDate><guid>https://ftrcrp.org/guides/local-llm-fallback-stack/</guid><description>&lt;p>The frontier models are extraordinary and I use them daily. That is exactly why this guide exists.&lt;/p>
&lt;p>Everything that makes them useful also makes them fragile as a dependency. They are a handful of companies, reachable over someone else&amp;rsquo;s network, priced at someone else&amp;rsquo;s discretion, governed by terms that change without your consent, and subject to outages, rate limits, deprecations, sanctions, and the ordinary politics of a volatile decade. A model you rely on can be retired with a month&amp;rsquo;s notice. An account can be suspended by an automated system on a Sunday. A cable can be cut. None of this is paranoia, it is just infrastructure behaving the way infrastructure behaves.&lt;/p></description></item></channel></rss>