I would love to be able to do the clustering from a CSV instead of a collection of Markdown files. I know I can easily generate the files, but I used to do this directly for very short text inputs (just titles or words) on nomic.ai (before they pivoted to 'Enterprise')
Grist [1] desktop [2] is a (kind of) local "wrapper app" over an sqlite database. It is "As extendible as it is flexible" [3]
The problem is I feel the tabular DB format is "too raw" for some usecases. I prefer Outliner/DB combos (like the upcoming logseq DB version) or maybe one of the local Notion alternatives.
Would it be possible to import titles as a text list, instead of requiring files?
I'm not a hoarder, but I do have a (very) long Excel file of movies and documentaries that I want to watch or have already watched. Most of them are available on streaming sites or for rent/download on demand.
You've got a great IMDb scraper and filtering UI. That's all I really need! :)
With Suno 3 (and possibly Stable Audio 2), we are definitely experiencing a moment for music that parallels what we saw with ChatGPT 3.5 and Dall-E 2. The unexpected jump in quality (like sora recently) is again surprising (to me).
As with these 3 past breakthroughs, Google seems to be (slightly) lagging and again misses the "defining moment". I'm willing to say that OpenAI could have achieved something similar (and claim a 4th turning point), but the headache of copyright issues likely pushed them to focus on Sora first. I'm almost certain Udio and Suno were trained on (a lot) of copyrighted music.
So, an LLM scoring over 80 on MMLU is no longer newsworthy on Hacker News? We've indeed come a long way.
Or perhaps it's just the skepticism surrounding such "claims". That's why I reckon more chatbots that don't rely on an API, similar to Inflection (or Microsoft's Copilot ?), should be directly integrated into the LMSYS Leaderboard. Isn't this what they did with Gemini/Bard?
> In other words, you can drag and drop downloaded states into your model, like literal plug-in cartridges
The same could be said of "control vectors" [1]. Both ideas are still experimental, but is seems to me IINM that they could replace "system prompts" and "RAG" respectively.
I'm patiently waiting for the planned database tables [1] (or the similar plugins to mature). However, even if this is implemented correctly, it is still going to be on a page, not block level (query/attribute/two-way links...). That is why I will probably stick with outliners.
Or, I may give Siyuan [2] a second chance. I'm actually referring to this now because they just released 3.0 with those local notion-style DB tables. Think Anytype but with an Obsidian feel, and it works on the block level!
I always wanted to sort/filter goodreads like this. I don't know how you scraped the site, but the Kaggle datasets I've seen are always deficient in one way or another: either too small (less than 10k), or books are scraped randomly (not top), or (at best) they use Best Books Ever lists (skips many top-rated books). I hope your source data is better.
It is getting somewhat better recently, but a phone like the Samsung A15 is still an exception : for under $170, you get 4+1 years of support, which is good enough I guess (less than $3/month).
What I would improve is the discoverability of improvements that already exist, if that makes sense : So many scripts, extensions, and UIs are out there. Maybe someday I will organize it together and feed it as RAG to a custom GPT.
And speaking of GPT, I just used it to create (in less than 1 minute) a userscript that does your request.
> It was a pain > all worth the hassle for the teenage me
My perspective is this: If I accepted (like the OP) how "difficult" it was to set up a system for discovering music before, why wouldn't I accept a little "hassle" with Spotify? because I'm paying? No, personally, I'm paying for the music DB, not the app. dashboard? Ignore. Official playlists? Ignore. How difficult is that? It takes way less effort to get around Spotify "pain points" than any prior system, and none of these offer what Spotify does best: enriched API access to "unlimited" music.
But of course, we do need to complain to make things better (especially for the artists).
Hmm... I've always wanted something like this. Good execution. Good use of (Andy Matuschak?) Sliding Panes.
However, my opinion is that this is going to work well only in very specific situations: small teams and discussions with a high ratio of long, analytical (as opposed to synthetical) comments over multiple levels (and not just the first).
It's just too advanced for most discussions. HN/Twitter are n-level (and a thread of tweets is a kind of pre-quotes). But Most Messaging/forums don't even have a third level. And a lot of people seem to find a one-level UI like Discord and IRC enough.