Not using Codestral (yet) but check out Continue.dev[1] with Ollama[2] running llama3:latest and starcoder2:3b. It gives you a locally running chat and edit via llama3 and autocomplete via starcoder2.
It's not perfect but it's getting better and better.
For example, the number of emails that don't have any form of unsubscribe link at all is shocking. Obviously the service doesn't get a true representation of all types of email but spam emails are a massive pain and a total waste of resource all round.
I've been contracting part-time and developing a few bits.
https://www.videocode.review/ - After working from home for a while we noticed that it was taking longer to pull requests merged. One reason for this is comments were getting misunderstood etc. So I created a way to record a video for a pull request (as either the author or reviewer) to try and avoid some of that misunderstanding. It's GitHub only for now but I would like to get it working with GitLab as well at some point. It's just in beta now, if anyone wants to try it out please get in touch on here or via the contact page.
https://www.stopthat.email - Forward emails to an email address to unsubscribe. This has been going a bit longer and I've tried to automate it as much as possible in terms of finding the unsubscribe links and filling out web forms. It currently doesn't handle JS on web pages so I'm working on that next.
Both have been good fun to develop and have use different technologies, infrastructure and services. Next, I need to let go of my fear of launching and learn some marketing.
I've been using webextension-toolbox[1] for a few years now to develop cross-platform extensions and it's worked really well. I always got the feeling other browsers other than Firefox were Second-class citizens with web-ext (if supported at all) whereas with webextension-toolbox they all appeared to work out of the box.
The first time I tested my extension on Firefox after developing it one Chrome for months it worked the first time. I was so shocked how seamless it was I actually thought something must be really wrong, it wasn't.
I created a similar service earlier this year which runs on exactly the same idea (forwarding emails to unsubscribe to them). It's nice to see some validation for the idea on HN.
I've attacked the problem from a different angle though - I've tried to automate the service a lot more. Automatically looking for the unsubscribe button and filling out any HTML forms that appear etc. It doesn't always work but it's been fun trying to work out ways to automate the different steps etc.
If anyone is interested in a similar product with a slightly different way of doing things, different pricing and a web UI, please check out:
https://www.stopthat.email/
Hopefully you don't mind the health competition ryanmjacobs.
Before I found out about ublock origins filter lists I always wanted to opt-out of these GDPR cookie banners, modals etc but I got a lot of fatigue having to follow all the steps for each website.
Although I hit a snag where some GDPR banners / buttons didn't return when using `querySelector` in the extension but do when you use the inspector / console and do it manually.
Does anyone know why and how to work around it? It was always something I wanted to know why but didn't find the time to dig into (and wasn't important while using ublock origin)
It has a Live Timing Client and a lot of historical data.
I only found it the other day, so I have no had a chance to play with it yet.