Thinking about implementation, it seems like tooltips would be a great way to handle this. Linking out from the tool tips to some kind of more comprehensive outside IT/cybersecurity resource would be a good bonus. Tool tip text generated by llm could take some of the heavy lifting.
Yes, closing your sinuses is a natural reflex response for humans, and people have greater or lesser at will control over it.
The nose holding for swimming is more about how strong that sinus closure is and endurance. People with larger sinus openings have a more difficult time keeping them closed and resisting pressure like water entering from jumping into a pool. Also some people have a hard time keeping them closed for any prolonged period.
In other words, you just have totally ripped sinuses breh.
Could this be the run-up to Apple acquiring Perplexity? I remain convinced that Apple defending their internal AI division shows they are close to a major acquisition and are just waiting for a valuation dip on one of the major competitors. Distribution is a solved problem for Apple, what they need is proven usecases and a competitive tech stack.
That said, search and consolidating multiple model APIs isn't a great match for what Apple needs, and their optics aren't great. My bet is still on Apple acquires Anthropic in 2026.
As a non-coder interested in self hosting and somewhat aware of cybersecurity, this is the most relevant take for me.
An application that facilitates safe self-hosting of many different service is great, however for it to be actually safe and useful it must either be a cybersecurity service keeping up with the pace of threats (which is essentially the corporate closed source model) or from the ground up be an educational platform as much as an application. Documentation needs to not only be comprehensive, but also self-explanitory to a non-technical audience. It is not enough to state that a setting or feature exists, it must also be made clear why it should be used and what the consequences of different configurations are.
This approach is almost never done effectively by FOSS projects unfortunately. Fortunately I think we are at the point where it is completely feasible for this type of educational approach to be fully replicable and adaptable from a creative commons source to the specific content structure of the application user manual using LLMs (local ones). The big question is, what is the trusted commons source of this information? I suppose there are MIT and other top university courses published for open use online that could serve as the source material, but it seems like there is likely a better formatted "IT User Guide Wiki" and "Cybersecurity Risk and Exploit Alert List" with frequent updates out there that I'm not aware of, perhaps the annals of various cybersecurity and IT associations?
Anyway I'm aware this is basically calling for another big FOSS project to build a modular documentation generator, but man would it help a lot of these projects be viable for a wider audience and build a more literate public.
It is nitpicking, but in legal terms you could say he has shares in the company but not stocks. Stocks refers specifically to publicly traded shares, that is to say shares sold on a stock market. Shares is the more broad term as it can refer not only to stocks but also private equity units of various types. Valve is a Limited Liability Corporation, or LLC, which have Membership Units as the type of shares held by owners, which differs from stocks both in terms of tax treatment and limitations on how they can be transacted.
I don't see it in the hardware design, but from a software perspective the groundwork is there for modularity. Offloading the core compute to the PC frees up onboard processing to run peripherals like full color front cameras (onboard are black and white / IR) and more advance proximity detection, hell hook up lidar and go nuts with full body tracking.
That said, all of that would depend on decent I/O. 2x USB4 ports would go a long way.
It days right in the marketing text that the headset is "a PC" which to me implies full SteamOS distro with no limitations on installing a different OS, if you can get the many hardware drivers to work.
Yes, I'm just pointing out that phones aren't terrible at acting as servers, it's a generational issue.
I'm definitely going to give this a try when I replace my current phone next year.