784 karma · joined June 21, 2019
It is on hosted on http://www.imdb-sql.com/imdb01-11-2024.parquet
In fact the main reason this project exists is
a) I wrote a jupyter notebook ages ago that'd join the raw data into a queryable form.
b) I committed it and forgot about it after the initial viewing of top movies/series.
c) For the Halloween I wanted to find a good-rated horror movie, a genre I don't watch much.
d) I found my notebook but it was a drag to get it running again, first pandas would keep throwing OOM errors so I had to migrate to polars. Secondly I had to find a spare working laptop since iPad is my primary off-work computing device as of late. Finally the schema is not so intuitive - I need to look up things like region/language codes.
I want something I can just leave unattended but still be able to use a few months later without going through a dev-env set-up. A static website with all the data is one potential way of avoiding maintaining it as it should keep running, just like an exe would keep running on Windows in the past.
I avoid maintaining personal projects as my software job requires me to maintain software and I don't find it enjoyable to do the same in my spare time.
P.S. Query sharing is supported:
https://www.imdb-sql.com/?query=SELECT+*+EXCLUDE+%28titleTyp...
It has these columns: https://www.imdb-sql.com/?query=SELECT+*+FROM+%27imdb01-11-2...
It is produced using https://github.com/afiodorov/imdb-sql/blob/main/notebooks/im...
From this data: https://developer.imdb.com/non-commercial-datasets/
The age rating is not part of the imdb non-commercial dataset.
I just run npm run dev locally. You'll need the parquet file of the data in public/ though, can get it from http://www.imdb-sql.com/imdb01-11-2024.parquet
If anyone with actual css experience wants to open a PR in the meantime I'll be very happy!
However titles are repeated often due to the region/language variations.
P.S. We can share links too https://www.imdb-sql.com/?query=select+1
The SQL flavor is https://duckdb.org/docs/sql/query_syntax/select
Not sure what you mean by scraping in parallel.
1. Macro level: Departments claim broad accountability.
2. Micro level: Pinpointing task ownership causes accountability to vanish.
3. Indefinite states: Ambiguous tasks linger without resolution.
4. Entanglement: Dependent tasks inherit this ambiguity.
This creates a system where responsibility exists in superposition, tasks remain unresolved, and accountability becomes increasingly delocalized.
I am not convinced it follows. Sure LLMs don’t seem complete however there’s a lot of unspoken inference going on in LLMs that don’t map into a language directly already - the inner layers of the deep neural net that operates on abstract neurons.
I wonder which successful game will make use of AI generated content next.
https://www.livetranslate.net/
Second one is more refined but both are functional.
I was pleasantly surprised somebody made a YouTube tutorial in Japanese about the latter https://www.youtube.com/watch?v=8gAkvZYayEc - feels like retro internet where people share things on their personal webpages.
Curiously the first one also landed me a contracting opportunity for a company that wanted to add live captions to their product and we went live with my help.
I also made a decentralized twitter dapp ages ago but AI apps definitely have had more interest.