I uninstall the gemini app and disable the google app. It seems they are heavily linked so remmoving it may do the trick. As a practice I don't use any google apps if I can find a good replacement so I am not sure if messages is impacted.
At launch you had 3 themes (blue, green, and silver) as well as classic where you had all the customization of Win2k's settings. Later on (SP3-ish) you got a zone orange/dark theme which was nice.
To do more you either used WindowBlinds or just grabbed a patched UxTheme32.dll which would accept unsigned theme files. Once you did that you had an almost silly number of options to try out from various web sites.
Claude has this by way of projects, you can set instructions that act as a default starting prompt for any chats in that project. I use it to describe my project tech stack and preferences so I don't need to keep re-hashing it. Overall it has been a really useful feature to maintaining a high signal/noise ratio.
In Github Copilot's web chat it is personal instructions or spaces (Like perplexity), In CoPilot (M365) this is a notebook but nothing in the copilot app. In ChatGPT it is a project, in Mistral you have projects but pre-prompting is achieved by using agents (like custom GPT's).
These memory features seem like they are organic-background project generation for the span of your account. Neat but more of an evolution of summarization and templating.
There's a commercial tool that has been available for a long time called Source Insight[1]. It isn't exactly cheap but I've used it in the past for both code splunking and editing and it's was a pretty useful tool.
It isn't an invite only club. Anyone can submit an existing application[0] and an app author can provide a metadata pack to speed up the process. They have some requirements to accept but it isn't a situation where a developer is just waiting around for the letter of invite to arrive[1].
That's because MSFT doesn't really do hibernate any more but does "modern sleep" where it functions like a phone with the screen off. It keeps active network connections, downloads patches and keeps checking for notifications and other such nonsense.
BIOS support for proper hibernation has been getting worse too because with MSFT demanding it, there is little reason to continue support.
I've had older laptops that do the sleep->hibernate setup without too much issue but now it is a crap-shoot on if it is even supported in the hardware.
That's because the goal is not to have functional hibernation, but to start up faster. If the goal can be achieved by using less power instead of shutting down the whole machine and restoring it identically and that's easier it's a valid alternative.
You used to be able to edit ACPI tables to reenable S3 sleep but these days they're stripping the functionality from firmware entirely.
For example, HP's enterprise lines have S3 stubs in their firmware. If you enable them, nothing happens, because someone deliberately removed the S3 blobs entirely.
One of the things I've done that has helped with my writing consistency is to use whatever version of "project" or "library" your LLM of choice has and pre-load it with a technical writing guide (I used the Red Hat Technical Style Guide[1]) and push my docs through that to identify improvements. It has been a great way to keep my own writing consistent and remove randomness from just having my own writing improvement prompt.
reply