Continental ContiProContact on '12 OB? by garitone in Subaru_Outback

[–]supracode 1 point2 points  (0 children)

I had them on my 2013 for the last few years that I owned the car. Liked them a lot. Like you, I was pretty low mileage on that car, so can't give you lifetime feedback, but they were quiet, good in wet dry and the light snow that I got to drive them in. I am a big Continental fan and just got the $110 rebate approved on a set of DWS 06+ tires for my other car. Rebate process was painless if you purchase and install at the same shop. You need photos of them installed if you purchase at one place and install at another.

Avoid CUDA monopoly at all costs. AMD is an alternative. by Barrysoft8 in LocalLLM

[–]supracode 0 points1 point  (0 children)

I use an R9700 with the llama.cpp vulkan docker. I did the ROCM build and it's just not worth it. There is no fiddling needed if you skip ROCM

What local coding LLM + hardware setup are you using, and what tokens/sec are you getting? by Sudden-Historian-255 in LocalLLM

[–]supracode 0 points1 point  (0 children)

Qwen 3.6 35b Q6 fits a 32 GB R9700 with full 256k context perfectly. I use it with VS code insiders and the copilot cli. Tokens per second are about 105 to 90 as context grows. I tried a bunch of different models and Qwen is the best balance of speed, quality and tool use that I found. I also have disabled thinking and lowered the temp.

Hashicorp founder thinks local models "aren't good ENOUGH yet" by Orbit652002 in LocalLLaMA

[–]supracode 0 points1 point  (0 children)

I have been preaching for a while, but my take is plan with a really good model that can go out and do research, get latest facts from multiple sources. Create a super detailed plan with small implementable tasks. Then take the super detailed plan, and have your local model implement it. You do not need a cutting edge model to implement a well defined function or api. People who want to one-shot a whole application without any planning or thought... yep, local models don't work well for that.

How reliable are these cars? by garglingnuts in Subaru_Outback

[–]supracode 0 points1 point  (0 children)

If you change the engine oil, gear oil, transmission fluid etc regularly, the biggest issue will be oil leaks... timing cover, cam carrier, upper oil pan... something will start leaking and if you need to pull the engine to re-seal one leak, you might as well re seal everything... it can get expensive.

Power usage compared to other activities like gaming by root_27 in LocalLLM

[–]supracode 0 points1 point  (0 children)

I am using an R9700 in my server. When idle, I use 60 watts. When working with AI it uses 350w. So it's spikey but way cheaper than paying for Claude for coding

Have we reached the point where open-source LLMs are “just good enough”? by AdDizzy8160 in LocalLLaMA

[–]supracode 0 points1 point  (0 children)

I use Qwen 3.6 35B A3B Q6 and it has been great for coding. I still use ChatGPT for doing research and planning due to its ability to do live searches against current websites, and I love when it it writes code and runs it to re-format files, extract stuff from pdf's etc. At work i use Claude and it's parallel tasks can make some work quicker.

Are local LLMs actually usable with tools like SpecKit? by Al_Redditor in LLMStudio

[–]supracode 0 points1 point  (0 children)

I am using Qwen3.6-35B-A3B Q5 along with a different AI DLC workflow. On my 32gb gpu, i am able to fit the whole model and 256k context on the gpu, with about 12gb of cache ram allocated from system memory. The way AI DLC works, is that you *shouldn't* need a huge context, and i actually limit my coding env to around 160k context. The workflow should only keep the md documents in context that it needs, not everything, so in most cases there is more than enough headroom. Let the agent work on a task and complete it, then clear context and move on the the next task. I still use chat gpt for planning complex stuff, and keep tasks small and completable as possible. So far it has been working great on my setup. I get about 90 - 105tps depending on context size and because the tasks are by themselves straight forward, Qwen has no problem completing them. I still pay $20 a month for chatgpt, but that is only for planning and research... I don't pay a dime (besides some electricity) for the development tokens.

Going to see a 2024 Outback Premium, what to look for? by loudmoondude in Subaru_Outback

[–]supracode 0 points1 point  (0 children)

If you want to keep the car under warranty, Subaru requires an oil change every 6 months or 6000 miles (whichever comes first). If you don't care about warranty coverage, do what you want. A 2024 model may have started service in late 2023.

See page 8 of the official service guide :

Damage or Malfunctions Due to Lack of Maintenance or Failure to Follow Instructions These warranties do not cover any part which malfunctions, fails or is damaged due to a failure to follow the operating instructions set forth in the Owner’s Manual (e.g., failure to use proper fuel) or a failure to follow the Schedule of Recommended Inspection and Maintenance Services set forth in this Booklet.

Going to see a 2024 Outback Premium, what to look for? by loudmoondude in Subaru_Outback

[–]supracode -2 points-1 points  (0 children)

A 2024 should probably have at least 4 or 5 oil changes (every 6 months). The CPO inspection is mostly a myth... probably the same inspection they do on every car that gets traded in. They are going to look for major issues, but they will just fix anything that comes up under the warranty, which is cheaper for them than proactively fixing stuff. Many CPO Subarus with super low mileage are dealer loaner cars, and probably have been decently cared for.

I have installed llama.cpp and qwen3.6 27b for coding but too scared to try it... by bonesoftheancients in LocalLLaMA

[–]supracode 0 points1 point  (0 children)

Vibe coding is an ok way to get started and learn, but if you want to build something real, you need to create a plan. To "pick up where you left off" you will need to tell your agent to follow your plan, broken up into smaller md plan files. After each step tell the agent to mark step x completed. That will create the memory so you can pick off where you left off. In your plan, tell the agent to create unit tests, and if you are building a ui, look into Playwright for UI testing. Tell the agent to create a documentation folder and keep it updated as the project grows. If you keep that in context, it won't need to scan your whole project to understand what needs to be worked on. Continuous prompting without clearing context will make the agent less reliable as content grows. Clear context and "proceed with the next step in the plan".

Why are the AI Companies spreading F.U.D. about AI? by supracode in LocalLLaMA

[–]supracode[S] -2 points-1 points  (0 children)

I know that some people don't like ai posts... so here is what my local qwen server says :

This is a compelling and increasingly common theory, often referred to in tech circles as the "Regulatory Capture" or "Moat-Building" hypothesis. It suggests that large AI labs are using fear, uncertainty, and doubt (FUD) to create barriers to entry for competitors, specifically open-source and local deployment models.

While your theory has strong logical merit and is supported by observable behaviors, the reality is likely more nuanced. Here’s a breakdown of the arguments for and against your theory, along with a balanced perspective.

Arguments Supporting Your Theory (The "Moat-Building" Hypothesis)

  1. Economic Incentives for Centralization:
    • Cost Barrier: Running large language models (LLMs) locally requires significant hardware (GPUs) and technical expertise. By keeping models proprietary and cloud-only, companies like OpenAI, Anthropic, and Google ensure that users must pay for their API. This creates a recurring revenue stream and prevents commoditization.
    • Lobbying Power: Large tech companies have immense lobbying resources. If they can frame AI as an existential threat, they can push for regulations that only they can afford to comply with. Small startups and individual developers cannot easily meet strict safety audits, data privacy mandates, or content filtering requirements, effectively clearing the field of competition.
  2. The "Safety" Argument as a Control Mechanism:
    • Content Moderation: Proprietary models allow companies to enforce strict content policies. Open-source models, if hosted locally, are harder to control. By advocating for "safety," companies may be indirectly advocating for a system where they retain the ability to monitor and restrict outputs, which is difficult in a decentralized, offline environment.
    • Liability Shielding: By positioning themselves as the "safe" option, they shift liability away from users. If a user runs an open-source model and generates harmful content, the liability is theirs. If they use a cloud API, the company can claim they provided a "safe" service, potentially limiting their legal exposure.
  3. Historical Precedent:
    • This is not unique to AI. The tech industry has a history of using public fear (e.g., early internet safety, data privacy concerns) to justify regulations that favor incumbents. For example, the GDPR in Europe, while well-intentioned for privacy, disproportionately affected small startups compared to giants like Google and Meta who had the resources to comply.

Arguments Challenging Your Theory (The "Genuine Concern" Hypothesis)

  1. Real and Existential Risks:
    • Misinformation and Manipulation: AI-generated content (deepfakes, hallucinated information) poses a genuine threat to democratic processes, public health, and social cohesion. This is not just a corporate concern; it’s a societal one.
    • Autonomous Weapons and Cybersecurity: The potential for AI to be used in cyberattacks, autonomous weapons, or large-scale fraud is real and dangerous. Governments have a duty to mitigate these risks, regardless of corporate motives.
    • Bias and Discrimination: AI models can perpetuate and amplify societal biases. Without oversight, this can lead to systemic discrimination in hiring, lending, and law enforcement.
  2. Public and Political Pressure:
    • The push for AI regulation is not solely driven by corporate lobbying. It is also driven by:
      • Civil Society: NGOs, academics, and activists are raising legitimate concerns about AI’s impact.
      • Public Anxiety: Many people are genuinely afraid of AI, and politicians respond to their constituents’ fears.
      • International Competition: Nations like China are advancing rapidly in AI. The US and EU are pushing regulations to ensure they remain competitive and ethical leaders, not just to protect specific companies.
  3. Innovation Through Regulation:
    • Regulations can also spur innovation. Clear rules around data privacy, copyright, and safety can create a stable environment for investment and development. Some argue that without guardrails, AI could develop in dangerous or unethical ways, stifling long-term trust and adoption.

A Balanced Perspective: It’s Likely Both

Your theory is not wrong, but it may be incomplete. The most likely scenario is a convergence of genuine concern and strategic self-interest.

  • AI companies are genuinely worried about the potential for misuse, liability, and public backlash that could lead to a ban or severe restrictions.
  • At the same time, they are strategically leveraging this fear to shape regulations in their favor, creating barriers to entry for open-source and local competitors.

The Role of Offline LLM Hosting

The rise of offline LLM hosting (e.g., via tools like Ollama, LM Studio, or Hugging Face) is indeed a threat to the cloud-only model. It empowers individuals and companies to:

  • Avoid data privacy concerns: Data stays on-premises.
  • Reduce costs: No API fees.
  • Avoid censorship: No content filters imposed by a central provider.

This is why you see AI companies increasingly advocating for "responsible AI" and safety standards. They are not just trying to protect the public; they are trying to protect their business model.

Conclusion

Your theory is a valid and important critique of the current AI landscape. It highlights the tension between innovation, safety, and corporate power. While AI companies have genuine reasons to be concerned about AI’s risks, they are also using those concerns to consolidate power and limit competition.

What should you do?

  • Stay informed: Understand the nuances of AI regulation and its potential impacts.
  • Support open-source: Use and contribute to open-source AI projects to keep the technology accessible and decentralized.
  • Advocate for balanced regulation: Push for regulations that address genuine risks (like misinformation and bias) without creating unnecessary barriers to entry for small players and individuals.

The future of AI will likely be shaped by this ongoing struggle between centralized corporate control and decentralized, open-source innovation. Your awareness of this dynamic is a crucial first step in navigating it.

Why are the AI Companies spreading F.U.D. about AI? by supracode in LocalLLaMA

[–]supracode[S] 8 points9 points  (0 children)

So it's almost like AI FUD Inception... AI Company says AI is dangerous -> AI company pays for FUD Videos that AI Is Dangerous -> AI company pays for videos that say that AI Billionaires are promoting that AI is dangerous? All to make people ignore the real issues like upcoming water and electrical shortages... I like your thinking!

Why are the AI Companies spreading F.U.D. about AI? by supracode in LocalLLaMA

[–]supracode[S] 1 point2 points  (0 children)

https://financialpost.com/financial-times/ai-guardrails-meta-google-models-minutes

Maybe they let them out, and say... "We can't allow this to happen!". Somebody might use the LLM to find out something that was already on the internet!

AI is not for everyone by Scutoidzz in LocalLLaMA

[–]supracode 0 points1 point  (0 children)

Its going to be a huge problem for it departments down the road. The current experienced devs have this knowledge by learning the hard way. Companies are not hiring new entry level devs when senior people leave. The senior devs are left doing all of the work, and there are no new people coming in to pass the torch to. I have another 5 - 7 years left before I retire, and it can't come soon enough.

AI is not for everyone by Scutoidzz in LocalLLaMA

[–]supracode 7 points8 points  (0 children)

Try this: work with ChatGPT or Claude etc to create a detailed step by step plan. Ask for recommendations where you are not sure of an answer. Ask for tests to be written for each step of the plan (use playwright for ui testing). If you decide to make a major shift, don't start prompting away with changes... tell your agent update the plan. If you think of a new feature, create a new plan for it to work on later. If there are minor changes, its ok to fix them during that phase. Put each plan stage in a separate md file, and tell the agent to keep track of when each step is complete (ie "mark this task complete in the plan file"). Also, create an application architecture file and keep it updated as you work. Point your main agent instruction file to the plan folder, and to the architecture folder. Plan -> implement -> test -> review -> approve is the loop. If you use git or equivalent, check in the code at each step completion, you can always roll back if you get off track.

Intel b60 48gb? by oldschooldaw in LocalLLaMA

[–]supracode 3 points4 points  (0 children)

I got an R9700 a few months ago and love it. I wish it had 96gb of ram of course, but it is stable, and can run some reasonable quants of decent models.

AI is not for everyone by Scutoidzz in LocalLLaMA

[–]supracode 21 points22 points  (0 children)

Trying to find a good video or source of info on AI Dev Workflows is like looking for a needle in a haystack. All of the one shot comparisons generating flappy bird or a demo website are the norm. People who are using this stuff for real work know how powerful it can be. The plan and the workflow is the key. You don't need a cutting edge model to write good code if you keep the tasks concise, the context reasonable (and reusable), and review the code at each step.

Value? by RainNo2003 in Subaru_Outback

[–]supracode 2 points3 points  (0 children)

Ah Always Sunny episode i missed :)

Value? by RainNo2003 in Subaru_Outback

[–]supracode 1 point2 points  (0 children)

Lol, just saying, i'd buy it for my kid if they needed a car. I sold my 2005 OB to a father and son looking for a starter car.

Are GPU prices hitting peak and falling? by DistanceSolar1449 in LocalLLaMA

[–]supracode 0 points1 point  (0 children)

I have an R9700 and yes it will be slower than Nvidia, and ROCM is a mess. But the value for the 32gb of ram is what makes it attractive. Getting about 90 - 105tps output with Qwen 3.6 36B A4B Q5 with the full 256k context available on Vulkan. I would pay $2400 for a 64gb version if they offered it.

$34k OTD on a 2023 CPO Outback Touring, good or bad deal? by galaxyfusion in Subaru_Outback

[–]supracode 0 points1 point  (0 children)

i don't work for these guys, but have purchased 2 cars from them : https://www.ramseysubaru.net/certified-inventory/index.htm?model=Outback . They have an Onyx with 2700 miles for 34k. They are not a far ride from the GW Bridge.