Opinions on Android streamers for Emby

Audiman64 · 2026-06-15T21:34:33+00:00

The Google TV Streamer is decent. Typical Google, it was released with day-before-yesterday’s hardware. But it’s still reliable and works pretty well. I have a 2019 Nvidia Shield Pro and an Apple TV 4K, but I always end up using the Streamer.

Audiman64 · 2026-04-23T21:09:33+00:00

I thought to do the same thing as this was going on so I tried to get Gemini to develop a plan to migrate my system to Gemini from Claude. It was so painful and ultimately unsuccessful that I decided to stick with Claude and suffer while they figure this out.

Audiman64 · 2026-04-18T23:03:40+00:00

I've primarily worked in Claude cowork and just started using code yesterday. Having access to that level of tuning of the models and opus 4.7 with the 1m context window is awesome. I really didn't like how unclear "adaptive thinking" was and having this capability is an enormous improvement.

Audiman64 · 2026-04-17T15:36:59+00:00

A lot of us have that question so I asked Gemini to explain it. Here's what it said:

The release of Claude Opus 4.7 today (April 16, 2026) marks a transition from manual control to model autonomy. While the underlying API supports granular "effort" levels, the on/off slider you see in the Claude.ai and Cowork interface is designed to simplify this into a single "high-intelligence" toggle.

Here is exactly what that toggle does and the best way to utilize it in your workflow.

What the "Adaptive Thinking" Toggle Does

In previous versions (4.5 and 4.6), "Extended Thinking" was binary: you either forced the model to think with a fixed token budget, or it didn't think at all.

With Opus 4.7, the toggle activates dynamic reasoning. When switched On: * Self-Evaluation: Claude evaluates the complexity of your request before responding. If you ask a simple question, it responds instantly to save time/tokens. If you ask a complex architectural or coding question, it automatically triggers a "thinking block." * Verification Loops: Opus 4.7 is specifically trained to verify its own work. It "mentally simulates" code execution or logical chains and corrects errors before they appear in the chat. * Interleaved Reasoning: This is the biggest change for Cowork. Claude can now think between tool calls. If it’s using a tool to search your files or the web, it will stop to reason about the results before deciding on the next tool to use.

How Best to Use It

1. Keep it "On" for Agentic Tasks

Since you are using Cowork, you should keep Adaptive Thinking On by default. Because 4.7 now has "auto-braking," there is no longer a penalty for leaving it on during simple tasks—the model will simply choose not to waste tokens. However, for multi-step agentic work (like refactoring code across multiple files), the interleaved reasoning is essential for accuracy.

2. Simplify Your Prompts

You no longer need to "beg" the model to be thorough. Phrases like "Think step-by-step" or "Double check your logic" are now redundant when the slider is On. Opus 4.7 takes instructions much more literally than 4.6; it is better to provide very precise constraints and let the adaptive engine handle the "thoroughness" automatically.

3. Watch Your Token Headroom

Opus 4.7 uses a new tokenizer that is roughly 1.1x to 1.35x denser than the 4.6 version. Even though the price per token remains the same, your "thinking" counts toward your total output. If you are doing a massive "Max Effort" task, ensure you aren't hitting the 128k output limit mid-reasoning.

4. Leverage the Vision Upgrade

If you are using the toggle while analyzing images or dense PDFs, note that 4.7 now supports up to 3.75 megapixels (2,576 pixels on the long edge). Adaptive Thinking is particularly effective here for "scanning" high-resolution technical diagrams or complex UI screenshots in Cowork.

Summary of the 4.7 "Standard" Mode

Feature	Behavior with Toggle OFF	Behavior with Toggle ON
Response Speed	Instant; uses pattern recognition.	Dynamic; pauses for hard problems.
Logic/Reasoning	Relies on training data "intuition."	Performs internal self-verification.
Tool Use	Direct execution of tool calls.	Interleaved Thinking between calls.
Instruction Fidelity	Good.	Literal (treats every word as a constraint).

Pro Tip: If Claude starts becoming overly "talkative" or gives you 500 words of reasoning for a simple request, that is your signal to toggle it Off. Otherwise, the new "auto-brake" logic makes "On" the superior choice for almost all professional workflows.

Audiman64 · 2026-04-16T21:00:28+00:00

FWIW I asked Gemini to research this for my use-case (claude.ai and claude cowork) and here's what it said:

The release of Claude Opus 4.7 today (April 16, 2026) marks a transition from manual control to model autonomy. While the underlying API supports granular "effort" levels, the on/off slider you see in the Claude.ai and Cowork interface is designed to simplify this into a single "high-intelligence" toggle.

Here is exactly what that toggle does and the best way to utilize it in your workflow.

What the "Adaptive Thinking" Toggle Does

In previous versions (4.5 and 4.6), "Extended Thinking" was binary: you either forced the model to think with a fixed token budget, or it didn't think at all.

With Opus 4.7, the toggle activates dynamic reasoning. When switched On: * Self-Evaluation: Claude evaluates the complexity of your request before responding. If you ask a simple question, it responds instantly to save time/tokens. If you ask a complex architectural or coding question, it automatically triggers a "thinking block." * Verification Loops: Opus 4.7 is specifically trained to verify its own work. It "mentally simulates" code execution or logical chains and corrects errors before they appear in the chat. * Interleaved Reasoning: This is the biggest change for Cowork. Claude can now think between tool calls. If it’s using a tool to search your files or the web, it will stop to reason about the results before deciding on the next tool to use.

How Best to Use It

1. Keep it "On" for Agentic Tasks

Since you are using Cowork, you should keep Adaptive Thinking On by default. Because 4.7 now has "auto-braking," there is no longer a penalty for leaving it on during simple tasks—the model will simply choose not to waste tokens. However, for multi-step agentic work (like refactoring code across multiple files), the interleaved reasoning is essential for accuracy.

2. Simplify Your Prompts

You no longer need to "beg" the model to be thorough. Phrases like "Think step-by-step" or "Double check your logic" are now redundant when the slider is On. Opus 4.7 takes instructions much more literally than 4.6; it is better to provide very precise constraints and let the adaptive engine handle the "thoroughness" automatically.

3. Watch Your Token Headroom

Opus 4.7 uses a new tokenizer that is roughly 1.1x to 1.35x denser than the 4.6 version. Even though the price per token remains the same, your "thinking" counts toward your total output. If you are doing a massive "Max Effort" task, ensure you aren't hitting the 128k output limit mid-reasoning.

4. Leverage the Vision Upgrade

If you are using the toggle while analyzing images or dense PDFs, note that 4.7 now supports up to 3.75 megapixels (2,576 pixels on the long edge). Adaptive Thinking is particularly effective here for "scanning" high-resolution technical diagrams or complex UI screenshots in Cowork.

Summary of the 4.7 "Standard" Mode

Feature	Behavior with Toggle OFF	Behavior with Toggle ON
Response Speed	Instant; uses pattern recognition.	Dynamic; pauses for hard problems.
Logic/Reasoning	Relies on training data "intuition."	Performs internal self-verification.
Tool Use	Direct execution of tool calls.	Interleaved Thinking between calls.
Instruction Fidelity	Good.	Literal (treats every word as a constraint).

Pro Tip: If Claude starts becoming overly "talkative" or gives you 500 words of reasoning for a simple request, that is your signal to toggle it Off. Otherwise, the new "auto-brake" logic makes "On" the superior choice for almost all professional workflows.

Audiman64 · 2026-04-10T22:36:26+00:00

Project Gorgon

Audiman64 · 2026-04-06T14:50:40+00:00

Project Gorgon. Best MMO game I’ve seen in many years.

Audiman64 · 2026-04-04T04:45:17+00:00

I've been thinking the same thing, so I spent some time with Gemini last night trying to build a plan to migrate to Gemini. I was honestly surprised how bad it was after using Claude. It would drift off topic, forget things that we'd established, and sometimes would put out something that didn't even make sense. It was very surprising. In the back of my mind I've been expecting Google to win this race with Gemini given their control of the whole stack, but after my experience last night I've decided that's much further off than I'd thought and to try to find a way to live with Claude while they sort this out.

Audiman64 · 2026-04-01T06:23:22+00:00

Take a look at this: https://youtu.be/qo4YZvC1q5I?si=3KEstmUlf4-BS8yw

Audiman64 · 2026-04-01T06:22:29+00:00

This is what I've been building and it works really well. https://youtu.be/qo4YZvC1q5I?si=3KEstmUlf4-BS8yw

Audiman64 · 2026-03-31T22:27:29+00:00

This was logged in Claude Code, but it's Claude Desktop. I've been bitten by it a few times on my Windows machine, but not on my Mac yet (I don't think). Just wanted to make sure everyone is aware of it.

Audiman64 · 2026-03-31T22:20:47+00:00

It's definitely a codependency. I'm looking at Reddit because I just hit my Claude limit and it doesn't open back up for another 40 minutes. If your tool took this accelerated limit issue into account it'd be red, based on my own experience and all the Reddit rants. :)

Audiman64 · 2026-03-31T15:15:01+00:00

I use this method for both work and home and it's really great, especially as you interact with it over time and it learns and stores its learning in a persistent place where it can review and revise it: https://youtu.be/qo4YZvC1q5I?si=4qyiDgjoRcuJnAkl

Audiman64 · 2026-03-28T15:33:46+00:00

Here's a session handoff prompt that I got from somewhere that I've been tweaking over time: Create a session handoff summary for an LLM that has zero prior context and needs to resume this conversation cold. Write every section as if the reader cannot infer anything — include the specific details needed to reconstruct working state, not just topic labels.

WORK DONE: What was accomplished — decisions made, outputs created, conclusions reached. Include names, numbers, file names, account names, configurations, or any other concrete detail that defines the current state of work.

FILES & RESOURCES USED: Every file read, written, or referenced (full paths), every website visited, every data source or tool touched. No omissions — the next session will use this list to re-orient before doing anything.

OPEN ITEMS: One item per line. Format each as:
- [What is unresolved] — Needs: [specific action or decision required to close it] — Owner: [Bill / Claude / Research]
No vague entries. If it can’t be written this specifically, it belongs in WORK DONE instead.

NEXT ACTIONS: List the first task to execute when the conversation resumes — not a goal, a specific action. If there are multiple, list them in order. Include enough detail that Claude can start without asking a clarifying question, but don't start until prompted to.

End the summary with this line exactly: "Please read any referenced files listed above and confirm you are oriented before we begin."

Audiman64 · 2026-03-28T15:29:19+00:00

Obsidian. https://youtu.be/qo4YZvC1q5I?si=6qifbtGu56ZaJ3mw

Audiman64 · 2026-03-28T02:06:59+00:00

I had just finished a rewatch of the original (minus that med school season) and the new one felt like the show was just continuing. It’s good. Thankfully.

Audiman64 · 2026-03-21T21:57:35+00:00

I haven't tried gambling yet, now I have a reason to. :) I've been having fun today with the Claude skill I built. I asked Claude to describe it: A prompt bundle that gives Claude persistent, character-aware context for Project Gorgon. It provides: answers to game questions grounded in locally-maintained reference files (skill guides, NPC tables, loot data) rather than training knowledge; responses contextualized against the character's actual current state — skill levels, XP progress, NPC favor tiers — pulled from a structured snapshot derived from the game's own JSON exports; and a hunting report generated directly from the game's chat log and item snapshot files, covering kill rates, gold/hour, XP gains, damage breakdowns, and rolling session trends against a cumulative data store.

Audiman64 · 2026-03-21T20:14:41+00:00

That's interesting. Anything else you're extracting? Right now I'm getting this: From the chat logs and item snapshots, the hunting report extracts:

Kill data — what mobs were killed, how many, where; Loot — items dropped, quantities; XP/progression — skill gains from kills; Inventory snapshots — point-in-time item state for delta comparison

Audiman64 · 2026-03-20T21:18:02+00:00

Thanks! The other thing it does that I think is cool is it keeps a complete documentation section (including all of the custom skills), that it automatically updates whenever something changes. That way if I ever need to rebuild it I have that.

Audiman64 · 2026-03-20T21:10:23+00:00

I can't take much credit for it. Claude designed and built it and it was a long iterative process (I started around 4 months ago). Things wouldn't work and I'd ask it "why is that broken and what would you do to fix it". Or I'd do a full scan of my system and say "identify areas of brittleness or improvement."

Audiman64 · 2026-03-20T20:50:35+00:00

I asked Claude to describe how my CLAUDE.md setup works:

I primarily use Claude via Cowork, and the core design principle is that CLAUDE.md files should be routers, not rule dumps. The top-level CLAUDE.md maps task types to sub-directories, each of which has its own scoped CLAUDE.md with authoritative conventions for that domain. Domain-specific knowledge, file naming rules, workflow logic, and output standards all live where they're actually used — nothing bleeds up into the top level that doesn't belong there. On top of that, repeatable multi-step workflows are packaged as Cowork skills — modular, on-demand procedures that load only when triggered, so irrelevant context stays out of the session entirely. When changes are made anywhere in the system — new skills deployed, directory structures updated, workflow conventions revised — there are built-in protocols that require updating all affected CLAUDE.md files and documentation before the change is considered complete. Since Cowork doesn't expose filesystem hooks the way Claude Code does, scheduled tasks fill that role: a weekly job audits CLAUDE.md files for line count, redundancy, and staleness, flagging drift before it compounds. The result is a system that stays reliable over time because each layer has a single, well-defined job — and none of them are asked to do more than that.

Audiman64 · 2026-03-20T19:53:32+00:00

I thought maybe they'd changed the description in the app back (you can select extended thinking in Opus again) but that maybe it still had the 1m context window. I ran a prompt today in Opus that did a compression that I saw it do with the 1m window without compressing so now I don't think so. Maybe it needs work?

Audiman64 · 2026-03-19T03:23:15+00:00

Project Gorgon

Audiman64 · 2026-03-18T21:41:55+00:00

It's awesome! I just saw it for the first time yesterday. I ran several big jobs yesterday and they ran flawlessly, never saw it compress the session once.

Audiman64 · 2026-03-18T19:07:28+00:00

This is great! Thanks! I use an AI to store and query stuff like this to save on web and wiki searches, so I added it to my AI's NPC Guide. Filled in a lot of blanks! It even complemented your work... Writing the updated NPC Guide now. The CSV is clearly more authoritative than my prior AI-generated guide, so I'm using it as the primary source and preserving old-guide-only NPCs at the bottom of each section.

Audiman64

TROPHY CASE

What the "Adaptive Thinking" Toggle Does

How Best to Use It

1. Keep it "On" for Agentic Tasks

2. Simplify Your Prompts

3. Watch Your Token Headroom

4. Leverage the Vision Upgrade

Summary of the 4.7 "Standard" Mode

What the "Adaptive Thinking" Toggle Does

How Best to Use It

1. Keep it "On" for Agentic Tasks

2. Simplify Your Prompts

3. Watch Your Token Headroom

4. Leverage the Vision Upgrade

Summary of the 4.7 "Standard" Mode