KarnaSubarna

1. Setting up Nvidia runtime for rootless Docker containers in Linux.

2. Resolving port :53 conflict between AdGuardHome (rootless) docker container and Systemd-Resolved.

I also noticed the same trend here and elsewhere as well.

Further read: https://www.tomshardware.com/pc-components/cpus/intel-finds-root-cause-of-cpu-crashing-and-instability-errors-prepares-new-and-final-microcode-update

More important question is - how this nitter instance is still working!!

shh..it's a spyware and adware!

What Firefox provides here:

A connector to LLM providers.
Accelerators (context menu options).

From a coding perspective, this should ideally be a very lightweight functionality.

This feature is very analogous to options to add a search engine, and also to provide accelerators via context menu.

While it can be done via third-party or Official Mozilla add-ons, but (to me) it still makes sense to have it part of the product.

If you're using a VPN at the OS or browser level, just like any other traffic, your query to the LLM service will be routed via the VPN. That VPN could be any VPN of your choice - Firefox VPN, Mullvad, or Proton etc.

The only problem is that most LLMs require a profile/login to work with. In such cases, using a VPN will be useless, as the LLM server will know who you are.

It's just a plain integration with 3rd-party or self-hosted LLM service.

I'm not sure if Mozilla will make money from this feature in any way.

Have you read anything about it anywhere?

Arch Wiki

It's just an integration with LLM services and not AI baked-in the browser code. You can even self-host any such service (Ollama) and integrate Firefox with it. That will make sure your query is not leaving your network.

Rustdesk controversy

The whole discussion on that pull request is extremely sketchy, IMO.