(a) Click thumbs-up/down in the conversation [1]
(b) Have the conversation flagged for potential safety concerns
[1]: https://help.openai.com/en/articles/5722486-how-your-data-is....
44 karma · joined October 19, 2023
(a) Click thumbs-up/down in the conversation [1]
(b) Have the conversation flagged for potential safety concerns
[1]: https://help.openai.com/en/articles/5722486-how-your-data-is....
The use case of QUERY is because POST conveys non-safe, non-idempotent requests which can potentially modify stuff according to the REST spec. GET requests on the other hand convey retrieval of a resource. However, due to GET requests not having a body, there's a limit to the amount of data you can put in the URL and you also cannot put sensitive data in it.
Additionally, GET requests are meant to be highly cacheable by default while a lot of the QUERY type requests are usually meant more for one-shot access.
QUERY is meant to address these limitations.
I have an ancient Windows 98 computer which I used to use at my grandparents' home until a few years ago. All the problems you mentioned did exist. However, the machine still felt more responsive than today's laptops. Something being objectively slow is very different from it feeling slow when you use it. As an example, I never had Word autosave turned on. It was always explicit (even if this meant I'd usually lose what I was working on when the computer lost power)
A consequence of this seems to be that clicking the link to a different article leaves you at the bottom of the page even though the article itself has changed.
This seems to be using JS to fetch the markdown and then render it but I do feel that it may be better off to simply pre-convert the markdown as part of the deployment process and serve the static page.
> However, we see positive speedup for the one developer who has more than 50 hours of Cursor experience, so it’s plausible that there is a high skill ceiling for using Cursor, such that developers with significant experience see positive speedup.
In short (there is nuance), Google cooperated with the IMO team while OpenAI didn't which is why OpenAI announced before Google.
- all generated console scripts hardcode the path to python during creation for the shebang
- some of the binaries generated by install processes can link to absolute paths in the venv
Conda does quite a bit of work under the hood to reduce disk space and ran into related issues described here: https://docs.conda.io/projects/conda/en/stable/dev-guide/dee...
I'm more interested in discussions on how this would be handled in other projects and the kind of SOPs companies may already have in place for these kind of scenarios.
The keyboard folio was also better for the RMPP since I often experienced loose contact with the one on the BTUCP when I used it on my lap (flat surfaces were good once I set it up). Otoh, the material used in the BTUCP was much better since the RMPP one uses a polyster weave which often leaves me with slight goosebumps. Additionally, the keyboard folio isn't a feature I use often.
I really can't talk about the others so for all I know, Scribe or supernote might be a lot better. RMPP does have a 90 days no questions asked return policy if you want to try it out (though I'm not sure how much that's worth).