lofi-dx
www.mechaelephant.com
lofi-dx | www.mechaelephant.com | |
---|---|---|
2 | 3 | |
7 | 1 | |
- | - | |
8.6 | 8.8 | |
2 days ago | 10 days ago | |
TypeScript | JavaScript | |
ISC License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
lofi-dx
-
A search engine in 80 lines of Python
Hey, I tackled phrase matching in my toy project here: https://github.com/vasilionjea/lofi-dx/blob/main/test/search...
I think I tested it thoroughly but any feedback would be appreciated!
www.mechaelephant.com
- Ask HN: Tips to get started on my own server
- A search engine in 80 lines of Python
-
My Second Brain – Zettelkasten
For me, the idea is sound but the implementation always seems so cumbersome. I want something that separates the data from the display as much as possible, has an easy 'note taking' and has an easy install. One problem I always encounter is that if the interface to add notes has too much friction, I stop using it pretty quickly.
Anyway, so I created something over the weekend called 'notenox' [0]. It creates a a JSON file of relevant information, one JSON file per note, with keywords and a "special" keyword prefix called a 'title' that mimics how I've actually been taking notes (email, so the 'title' mimics an email thread). For display, I consolidate all JSON files into a single JSON file and then have it loaded into the browser with some Javascript to group by title or keyword, along with doing all cross referencing and counting on the client end.
Creating notes is done through the command line, because that's a common way I interact with my computer, with different options to create titles, links, keywords, etc. I'm sure there are many different Zettelkasten implementations out there but they always seem so clunky and cumbersome. It's not hard, so the simple use case should be simple, nor should it proprietary or locked behind a SaaS.
You can see my personal notes in action, if you like [1] (sorry, not mobile friendly!).
[0] https://github.com/abetusk/www.mechaelephant.com/tree/releas...
[1] https://mechaelephant.com/notenox
What are some alternatives?
searchkit - Search UI for Elasticsearch & Opensearch. Compatible with Algolia's Instantsearch and Autocomplete components. React & Vue support
anystyle - Fast citation reference parsing
router - 🤖 Fully typesafe Router for React (and friends) w/ built-in caching, 1st class search-param APIs, client-side cache integration and isomorphic rendering.
orama - 🌌 Fast, dependency-free, full-text and vector search engine with typo tolerance, filters, facets, stemming, and more. Works with any JavaScript runtime, browser, server, service!