A tool which I can train on the conventions used in a media library file structure (directory, file names) and then use it to change the file names of new files to the library convention.
Ask HN: What small library or tool do you want that doesn’t exist?
141–145 of 145 posts
Re: Ask HN: What small library or tool do you want that doesn’t exist?
#142Re: Ask HN: What small library or tool do you want that doesn’t exist?
#143Earlier quoted context omitted.
It would be nice if there were a multi- service client like a feed reader that organized by unique post and offered the conversations of each service as attributes to it.
Yeah that'd be really nice, some services like Feedly offer deduplication but I suspect that only applies to text - not images.
Elfeed for Emacs is very hackable. This might be a nice project.
Re: Ask HN: What small library or tool do you want that doesn’t exist?
#144Some form of a meme search (and recommendation) API.
Currently everyone around (I included) scraps memes from reddit, and then displays them on their website, app or chatbot.
I would love to have some API do the heavy lifting by:
- indexing memes from reddit and other social media sites. Where I can search with text or an image.
- recommending memes directly to my users, based on their like(s) or dislike(s).
(bonus) a text to meme creator. A user inputs text on the front end, I send it to the API, it returns a nice full meme.
Re: Ask HN: What small library or tool do you want that doesn’t exist?
#145Almost every data exploration tool requires a date range to work, and yet there's no standard language for expressing these. I want a parser that: - Undertands simple ranges (e.g. "2022-04-01 to 2022-05-01"). - Understands relative ranges (e.g. "4 weeks ago to 2 weeks from now"). - Understands ranges to be expressed by omitting components (e.g. "2022" means "2022-01-01 to 2022-12-31"). - Has equivalent parsers for ot…
Something could be based on the "Rosie Pattern Language"[0]. There is already a parser for en_US/en_EU dates[1], which should be simple to extend to date ranges.
Another option would be using Tree-sitter[2]. It would be overall similar to using the Rosie Pattern Language, but Tree-sitter seems to have a more active community.
I wouldn't be surprised if one could write an automated Tree-sitter to Rosie Pattern Language translator.
[0]: https://gitlab.com/rosie-pattern-language/rosie/-/blob/maste...
[1]: https://gitlab.com/rosie-pattern-language/rosie/blob/master/...