HN user

yegle

2,978 karma
Posts19
Comments630
View on HN

Given that:

- Google has been around for 20+ years, so the concept of search engine and the technologies behind it should have been well known.

- Computing power and Internet speed has increased significantly and in many homes (at least outside of US) 1Gbps is norm.

- Everyone is talking about Google deteriorating over the years and prefer the old Google. The old system from the 2000s should be dirt cheap to run with modern home hardware.

- People's need for search engine is highly specific, you presumably would be interested in searching a small subset of the whole Internet.

My question is: why haven't a local run search engine be a thing at least in the tech circles?

It should be able to bootstrap with e.g. an hourly updated "top 100 websites in 50 categories" index file, and adapt to my daily queries to automatically update the index in the background, and iteratively improves the quality of the results.

The rise of the local LLM users proves this model works.

I have the feeling that Git winning the war hinges heavily on GitHub being the way to do open source projects, and that is changing given the sad state of GitHub.

Another contender is Jujutsu (jj) which allows you to use jj as frontend and use Git as the backend (with the potential to support any backend, e.g. Google's proprietary Piper), with the best ergonomic and the widest availability of hosting solutions.

You should have used the `--deploy-hook` on certbot. I use this to copy the cert to Synology NAS and trigger a reload of the cert on the NAS.

BTW: The easiest way to run certbot in a container is to mount a renew script (some shell script as simple as `certbot renew`) to /etc/periodic/daily/renew, then change the container's entrypoint to `crond -d6 -f`.

The MacBook Neo 4 months ago

The A9, in 2015, benchmarked comparably to a two-year-old MacBook Air from 2013. More impressively, it outperformed the then-new no-adjective 12-inch MacBook in single-core performance (by a factor of roughly 1.1×) and was only 3 percent slower in multi-core.

Too bad that performance is (still) locked in the walled garden and cannot be used as a small Linux server.