matusfaro

This usually happens in single page apps (SPA):

The proper way is to have an actual link but to override the behavior to navigate within the SPA. So if you click it, the navigation will be within the SPA but if you ctrl+click it, the browser takes over and opens the underlying link in a new page.

Typical issue is when a developer forgets to make it an actual link, but only inclides the SPA navigation.

I built something I needed:

A local desktop app that acts as a gateway for LLMs, MCPs and Skills with smart routing and optimizations built-in.

Hey HN!

With Claude and a strong hammer, I made a desktop app that acts as a gateway for LLMs and MCPs to solve some of my problems:

- One place to auth my MCPs and LLMs and to dynamically assign them to apps

- Monitor and intercept requests for debugging AI Apps and MCPs

- LLM routing with local fallback, using up free-tier first across providers

- Just for fun: Enriching LLMs with injected MCPs, Skills, JSON repair, msg compacting/indexing, Memory, etc..

It's a great tool for developing AI apps as well as managing a handful of MCPs and LLMs.

Agreed, I was only suggesting to use Grayscale to cover all types of color-blindness and to encourage creating UIs that are independent from any color as it's a bad habit in general. It's easier to remember to not rely on any color rather than just red-green.

Living in Ulaanbaatar Mongolia for some time I experienced temperatures of -20 -30 -40 Celsius. Every ten degrees lower I thought it was going to be the same, but was I wrong.

My most notable discovery was when I wanted to jump start my car, because the battery died due to the cold. I was about to bring out my jumper cables when my local friend told me to bring the cables inside first.

I didn't understand why and naively ignored what he said only for the rubber jumper cables to literally crumble in my hand, breaking as I tried to straighten them.

Mongolians are so resilient and have so much knowledge on how to survive in extreme weathers with a simple yurt and a livestock of 100 sheep goats and horses.

> love a tool to see which tabs are talking with each other also

Cool idea but probably not that useful and difficult to accomplish. There are many ways to communicate that could be grouped into:

1. tab -> tab (same domain)

2. tab -> tab (different domain)

3. tab -> server -> tab

For #1, there are so many ways to transfer information it would be hard to detect and differentiate whether it's communication or just happens to be using the same resource. (e.g. one sets a cookie or local storage and the other one reads it)

For #3, it would be impossible to detect. Especially if detection is an issue, both tabs could be communicating with unrelated servers which talk with each other.

For #2, it would be the only interesting one as there is limited options (e.g. Broadcast Channel), but at the same time I assume rarely used in practice. And if detection is an issue, they would switch to #3 to avoid it.