stork VS adblock-rust

If your content is mostly static, you might want to consider pre-building an index and shipping it as a whole. You could look into something like

* https://stork-search.net/ (Rust/WASM)

* tinysearch: https://github.com/tinysearch/tinysearch (Rust/WASM)

* https://lunrjs.com/ (JS, simple, stable)

* http://elasticlunr.com/ - based on the former, slightly more sophisticated tuning options

Mostly write about Elixir. Check out the search function. It is a rust library run as WASM in the browser (all the right keywords for HN hehe).

My blog: https://victorbjorklund.com/blog

Search library used: https://stork-search.net/

(And yes, I know it is totally overkill to have search when you just got a few articles)

Also another alternative is stork https://stork-search.net/

Stork seems perfect: https://stork-search.net/

It doesn’t do live crawling, so might not be quite what you want, but I built Stork Search (https://stork-search.net) to solve full-text search for static sites.

Today, you’d run a binary as part of a site’s build or deploy process, feeding in the input files. It generates a search index which you deploy alongside your site. The project’s JS library will load that index and turn it into a client-side interactive search interface.

I’d be curious to see if this sounds interesting or workable for you - you mentioned that you don’t want to host your own index, but does that change if “hosting the index” feels similar to hosting an image, instead of spinning up a server?

I’d be interested in building a paid addition that will crawl your site & host the index - you’re probably the 2nd person I’ve seen with that suggestion. Please let me know if you’d be interested in being a beta user.

You can index your crawl data with StorkSearch[0] then use its js interface for search.

[0]https://stork-search.net/

stork: a fast web search made for static sites

There seems to be an open issue regarding this hopefully it is resolved soon.

Brave has written their own (open source) adblock engine (in rust) that is directly integrated into the browser (ie. not an extension, so is not affected by Manifest V3).

https://github.com/brave/adblock-rust

Here is a (somewhat dated) article describing it by the authors:

https://brave.com/improved-ad-blocker-performance/

Brave has its own Rust implementation of an adblocker embedded in the browser: https://github.com/brave/adblock-rust; so it does not embed uBlock Origin (but the filters are mostly compatible)

Disclaimer: I work at Brave but not on the browser.

We support :has currently, which impacts many filters in EL and uBO. Some non-supported filters such as upward() can be manually converted over to use :has instead. The other unsupported procedual filters are a WIP will depend how easy/hard they are implement. No ETA, but have opened a ticket https://github.com/brave/adblock-rust/issues/293

ublock on chromium and brave itself can't use all of the filters in that list: https://github.com/brave/adblock-rust/issues/4

It's open source https://github.com/brave/adblock-rust

I've fixed this in the adblock engine as of https://github.com/brave/adblock-rust/commit/8a755bdb190bb55a3a3acee1e6507085051bdeec, and I'll push to get this patched in 1.47 soon. Thanks for the reports!