2. This is actually helpful thanks, don’t think of using a shortcut and making one myself!
2,349 karma · joined October 23, 2011
2. This is actually helpful thanks, don’t think of using a shortcut and making one myself!
Also, how Apple seems to deliberately avoid including a shortcut to the full settings anywhere in the control center or the shade. It honestly feels like one of those stubborn Apple things where at one point they decided Android including a settings shortcut (gear icon on the shade) was somehow an admission that its quick actions were poorly designed and iOS is above that.
I use Roo Code a lot and always looking for "hacks" to minimize my pay-per-request Gemini 2.5 Pro usage on OpenRouter so this is awesome (current method is using unlimited GPT 5 mini via Github Copilot for most uncomplicated stuff, then Kimi K2 via OR). I also have some customized Claude Code aliases/scripts I use routinely on my dev VMs and will figure out a good way to easily swap between Claude and GLM backends to compare.
Thanks for the rec! It's kinda buried on the z.ai website for some reason, I probably wouldn't have discovered it's a thing without your pointer.
(i.e. setting the "frontlight" brightness to 0% on a Kindle, which would also eliminate color temperature control other than room ambient light).
It does seem hard to believe that e-ink + a reflected frontlight would be any easier on the eyes than an LCD backlight (particularly since it's probably also using PWM). But an e-ink display on its own at least removes an additional light source pointing directly at the eyes, which could provide a potential mechanism for different effects on the eyes/brain.
1. Flip one switch in settings to enable sideloading
2. Download and open an APK
3. Flip one more switch (which you get automatically redirected to and it's highlighted at least on Samsung phones) the first time installing from whichever app source (Chrome/FDroid/etc).
4. Click install
Other than step 1, the user is led through the process via prompts, and step 3 only has to be done once per source. i.e. the first time you install from FDroid, after that you just click install without any nags or scare screens.
As far as I remember the "enable sideloading" switch in settings has always been a thing, and the per source setting was added at least 5+ years ago.
I've seen the cycle of claims going from "10x multiplier, like a team of junior devs" to "nerfed" for so many model/tool releases at this point it's hard for me not to believe there's an element of perceptual bias going on, but how much that contributes vs real variability on the backend is impossible to know for sure.
> We pretty much have those today so by 1997 standards, machines have minds, yet somehow we moved the goalposts and decided that doesn't count anymore
What you describe as "moving the goalposts" could also just be explained as simply not meeting the standard of "as intelligently as any human on any subject".
Even in the strongest possible example of LLM's strengths applying their encyclopedic knowledge and (more limited) ability to apply that knowledge for a given subject I don't think they meet that bar. Especially if we're comparing to a human over a time period greater than 30 minutes or so.
It's pretty horrible performance even on my two year Windows laptop with 16GB of RAM, I could try on my M1 Macbook too but the juice just isn't worth the squeeze for me at this point.
https://docs.anthropic.com/en/release-notes/system-prompts#a...
https://www.reddit.com/r/PromptEngineering/comments/1mknun8/...
Passing in docs usually helps, but I've had some incredibly aggravating experiences where a model just absolutely cannot accept their "mental mode" is incorrect and that they need to forget the tens of thousands of lines of out of date example code they've ingested during training. IMO it's an under-discussed aspect of the current effectiveness of LLM development thanks to the training arms race.
I recently had to fight Gemini to accept that a library (a Google developed AI library for JS, somewhat ironically) had just released a major version update with a lot of API changes that invalidated 99% of the docs and example code online. And boy was there a lot of old code floating around thanks to the vast amounts of SEO blog spam for anything AI adjacent.
EDIT: In fact I see your comment as the 5th result or so searching "XML Startup" in quotes haha.
The latter is a commonly recommended strategy in general for any large task even with more powerful models to keep context manageable and allow recovering easily if on step 9/10 the LLM loses it and starts mangling all the previous work it did. That way you don't have to start all over from the last good checkpoint or commit.
For any problem with a lot of reasoning or problem solving I use "architect" mode first with Gemini 2.5 Pro or Claude Sonnet 3.7/4 to break it into discrete subtasks that 4.1 can follow pretty successfully. This approach is very cost effective as Gemini can do a lot of high level planning quickly and cheaply.
I'm sure a lot of the experience depends on how 4.1 is being used, I've fine tuned my custom Roo code configuration to work around its limits without a lot of sacrifices, I'm sure using it out of the box with Copilot is asking a lot more from a weaker model on its own.
Unlike some other workarounds this is a fully supported workflow and does not break Copilot terms of service with reasonable personal usage. (As far as I understand at least. Copilot has full visibility into which tools are using it to make chat requests so it isn't disguising or impersonating Copilot itself. When first setting it up there's a native VS Code approval prompt to allow tool access to Copilot and the LM API is publicly documented).
But anything unlimited in the LLM space feels like it's on borrowed time, especially with 3rd party tool support, so I wouldn't be surprised if they impose stricter quotas for the LM API in the future or remove the unlimited limit entirely).
I usually use an agentic workflow and "hallucination" isn't the first word that comes to my mind when a model unloads a pile of error-ridden code slop for me to review. Despite it being entirely possible that hallucinating a non-existent parameter was what originally made it go off the rails and begin the classic loop of breaking things more with each attempt to fix it.
Whereas for AI autocomplete/suggestions, an invented method name or argument or whatever else clearly jumps out as a "hallucination" if you are familiar with what you're working on.