> In NodeJS, you can keep a connection open to an external resource by creating an https.Agent and then providing it to your http requests: fetch(url, {method, agent}). This can have a dramatic impact on latency.
Is it true that you can pass a nodejs agent to fetch ? I don't think so
This doesn't match my experience at all. I'm writing this from my fairphone 3 purchased in 2019 the day of release. I purchased one for me, one for my wife. I replaced the battery on mine once, my wife never had to change it. Her phone started so show sign of age a few month ago, she switched to the FP6. I will switch to the FP6+ soon as the support come to end this month for the FP3 (I could switch this one to eOS, but performance wise, it's not in it's prime, so I figured I could afford an upgrade after 7 years ^^). I reached out to support quite a few times for my wife or I (for order reasons, issues with operators, bugs, etc) and they have always been excellent for me.
Also as you probably noted, I'm quite enthusiastic about their products and have convinced a bunch of my surrounding to purchase fairphones when they had to change phone (models 3, 4 and 5 so far). I never had any of them tell me they regreted following my recommendation and as far as I know they still use their fairphones.
I have been using fastmail for a few years (not coming from gmail) and the service is good indeed (I don't need much tbh). I'm considering switching at some point anyway as I'm trying to move the last parts of my digital life back to Europe, but I have not found an alternative I liked so far
I've been using Mailbox.org for almost a year now and am very happy. They not only host email for you but also online conferencing, simple office suite and storage drive.
A good commit message needs to explain why this change was needed/done rather than what is the content of the commit. Unless Claude also has access to the context via for example the associated issue, it simply cannot write a good commit message since it cannot generally guess why something was done from just the change. This is also the case for humans and the reason why you need to include this in the commit message.
I fully agree, but you'd be amazed at how good Claude is at figuring out the why based on the what. I would never have believed it if I hadn't tried it myself. If it doesn't get the why, then I will typically add it
Anecdotally, I don't use a screen reader and also couldn't care less on the visitors on the site. I doubt anyone but you is interested in this, and probably this number is slightly lower just because of that popup
If I'm not mistaken, it's not a prompt injection attempt, but a training data pollution, in order to prepare for a prompt injection later :) great idea
I'm not sure what you are complaining about, AGPL is doing nothing against commerce and you are free to fork and sell a service using that fork. Just make sure to provide the code source of your fork to your user so they can also make their own forks, potentially making their own commercial services with them. It might be to most pro commerce licence I know.
Is it true that you can pass a nodejs agent to fetch ? I don't think so
reply