Your home server might have the required bandwidth but not requisite the infra to support server load (hundreds of parallel connections/downloads).
Bandwidth is only one aspect of the problem.
Your home server might have the required bandwidth but not requisite the infra to support server load (hundreds of parallel connections/downloads).
Bandwidth is only one aspect of the problem.
That solves the media distribution related storage issue, but not the CI/CD pipeline infra issue.
Exactly the same rationale as mine.
Users are only shown Big Tech “3rd-party” options. Mozilla made this choice intentionally.
Well, how many users really have LLM local-hosted?
To be honest, I never tried publicly available instances of any privacy front-ends (SearxNG, Nitter, Redlib etc.). I always self-host and route all such traffic via VPN.
My initial issue with SearxNG was with the default selection of search engines. Default inclusion of Qwant engine caused irrelevant and non-english results to return. Currently my selection is limited to Google, Bing and Brave as DDG takes around 2 sec to return result (based on the VPN server location I'm using).
If you still remember the error messages, I might help to help fix that.
Though it is an off-topic but what exact issues you faced with SearxNG?
On Ubuntu, replacing Firefox/Thunderbird snap version with actual deb version.
The built-in AI staff,you referred to, is nothing but an accelerator to integrate with 3rd-party or self-hosted LLMs. It's quite similar to choosing a search engine in settings. This feature itself is lightweight and can be disabled in settings if not required.
But pocket can be disabled via about:config, right?
I thought that’s how all those soft forks handled that mess.
You may self-host SearxNG (via Docker) and avoid direct interaction with search engines - be it google, bing, Brave or DDG.
SearxNG will act as a privacy front-end for you.
This is exactly what came to my mind while reading through the article.