It's free for now and I've ported the first chapters from the previous version, would love to hear what you think !
Karim
839 karma · joined December 5, 2013
It's free for now and I've ported the first chapters from the previous version, would love to hear what you think !
Karim
I recently learned you can use LUA to write custom plugins and change some of the converting behavior. I'm using it for example to create slides similar to the "sent" program.
It helps me bootstrap new presentations and talks very quickly: https://github.com/KarimJedda/justslides
> POST on /queries/enlisted-students-on-joining-date/version/1 { "date": "2023-09-22" } to retrieve all students that joined on a given date.
always ends up in a complete and absolute mess, where every possible query gets it's own random name, different parameters, ending up with duplicates all over the place. Also, while it can be possible to cache these POST requests (responses), it's additional work and more friction compared to REST. I'm not convinced the tradeoff is worth it in this particular case.
All in all, I don't know if the current proposal can be an alternative either but the idea of a "REST-lite" goes in the right direction and it's a great start.
However this is a complete no for me:
> When a requested student is nonexistent, your API can return 200 OK HTTP status code with a { "user": null, "message": "No user exists with the specified ID" } response body.
If nothing is found, I want a 404! :D
This has been working for months now and is the best method for this type of stuff, a thing for moat-lovers. Too bad it wasn't explored here, the text-based methods turned out to be mainly an unreliable waste of time.
I think what this could lead to is homogenization of the content serving layer, since all you'd really need is to get content to the user that can move their filters from one site to the other, the display layer being less relevant (and differentiating). But let's see, exciting times.
Essentially, I wrote a small browser extension, that takes the content of LinkedIn, Twitter, YouTube posts/titles, and filters them out based on if they are clickbait, low effort, etc.
It's liberating :D
ref: https://github.com/duckdb/duckdb-wasm/issues/1542#issuecomme...
Thanks!!
I tried it with German & English without issues. It should also work for French but might need a bit of tweaking. The code is very straightforward, but depending on the context I'd recommend experimenting with the parameters that would suit you.
It's using a model called "Whisper" under the hood.
Have fun :)
I think something might be off with the example. Can't wait for this stuff to work on llama.cpp. Going to try it with mistral & stable lm now, thankfully tomorrow is a holiday in Germany :)
Some of the instructions are ignored though so I'd be careful there, one instruction is to rewrite the previous response by "starting every sentence with the letter A" which is a bit of a hit or miss right now.
I haven't taken time to compare between the different releases but if anyone is having the same type of issues, I recommend downgrading even if it might mean less features.
What I want to see for myself is how Unit compares to those for this reduced scope (api's/services) and how fast I can be productive with it. This could be a good starting point for a lot of new applications, kind of an "airflow (the data orchestration thing) on Webassembly".
So main points are performance (is it good enough) and developer experience (is it easy to maintain/change).
Nothing really ground breaking, just trying out stuff.
Huge potential!
What's your recommended approach? Even if open-source, curious to learn.
https://karimjedda.com/beautiful-data-visualizations-powered...
I'm wondering if there is any way of running this locally, against my own models?
It is based on the results of a previous survey: https://old.reddit.com/r/rust/comments/wkv8gv/rust_foundatio.... Looking at where we are now it's safe to assume that not all community feedback was given the same level of care, the (vocal) community is against this, as am I.
What the job actually gets you (mandate, network, access, decision power, ...) is the real value money couldn't buy otherwise.
But then again this argument might be wrong, because if it were the case why list the job in the first place?
Looking at how the inference runs, this shouldn't be a big problem, right? https://github.com/setzer22/llama-rs/blob/main/llama-rs/src/...
Seems it now also supports AVX2 for x86 architectures too. https://twitter.com/ggerganov/status/1634588951821393922
Might be helpful for someone, my small contribution to how to get started with Rust by "keeping it close to Python" https://karimjedda.com/carefully-exploring-rust/