Readability4J VS Typesense

Depending upon the type of content, one might want to look into using the Readability (Browder's reader view) to parse the webpage. It will give you all the useful info without the junk. Then you can put it in the DB as needed.

https://github.com/mozilla/readability

Btw, readability, is also available in few other languages like Kotlin:

https://github.com/dankito/Readability4J

My Hacker News client HACK for iOS and Android has a reader mode ability browser. While on iOS, I was able to use the reader mode feature provided by SFSafariViewController, that wasn't available on android.

So I had to read a ton about this. I ended up using a heavily modified Kotlin version of Readability:

https://github.com/dankito/Readability4J

https://play.google.com/store/apps/details?id=com.pranapps.h...

https://apps.apple.com/us/app/id1464477788

Not sure about OP but I just implemented this in my Hacker News android client (thanks for the idea OP).

This is how I implemented it. I had already achieved article to "reader mode" by heavily customizing the Kotlin port of Mozilla‘s Readability:

https://github.com/dankito/Readability4J

Then I pass the text via Android's TextToSpeech library and it works very well:

    fun trySpeaking(str:String){

Disregarding props-drilling technique in favor of a more reliable and elegant solution we looked for inspiration elsewhere. Another project of ours .find was using Typesense/Algolia components, which looked a bit like black-box/magic, but at the same time provided a clean approach to build complex and highly customizable solutions.

Have you ever tried to look up something, only to realise your search engine doesn't recognise your typos? Typesense to the rescue! It's a fast, typo-tolerant search engine built for an easier browsing experience. The latest version comes with new features such as built-in conversational search, image search, voice search, analytics, and more. Dive into the release notes for the full list of changes and enhancements.

There are actually plenty of non-ES products that are way easier to integrate and tune (and get better results with less effort).

- Typesense (https://github.com/typesense/typesense)

- Algolia

- Google Programmable Search Engine (https://programmablesearchengine.google.com/about/)

Typesense - Open Source Alternative to Algolia

If you like your penny take a look at Typesense https://typesense.org/ - nothing to complain here. Especially nothing complain about pricing.

I work on Typesense [1] (historically considered an open source alternative to Algolia).

We then launched vector search in Jan 2023, and just last week we launched the ability to generate embeddings from within Typesense.

You'd just need to send JSON data, and Typesense can generate embeddings for your data using OpenAI, PaLM API, or built-in models like S-BERT, E-5, etc (running on a GPU if you prefer) [2]

You can then do a hybrid (keyword + semantic) search by just sending the search keywords to Typesense, and Typesense will automatically generate embeddings for you internally and return a ranked list of keyword results weaved with semantic results (using Rank Fusion).

You can also combine filtering, faceting, typo tolerance, etc - the things Typesense already had.

[1] https://github.com/typesense/typesense

[2] https://typesense.org/docs/0.25.0/api/vector-search.html

For something small with a minimal footprint, I'd recommend Typesense. https://github.com/typesense/typesense

I haven’t used Publish, but I’d assume you could use something like https://typesense.org/ to index and search the vault.

A cheaper option would be to use https://typesense.org. You can use DynamoDb streams to automatically load records. It has worked well for me.