4 ms·

Waiting for someone to ask ChatGPT to make a Firefox version of this extension...

by jeff_carr 4y ago

tantalor 4y ago
> You are a chat bot that rewrites Chrome extensions for other browsers...
- hxugufjfjf 4y ago
  You are a chat bot that rewrites Chrome extensions to firefox, how would you rewrite the following code? https://github.com/wong2/chat-gpt-google-extension https://github.com/wong2/chat-gpt-google-extension To convert the code from the GitHub repository you provided into a format that is compatible with Firefox, the following steps could be taken: Replace instances of "chrome" with "browser" in the code. In the Chrome extension API, the "chrome" namespace is used to access various features and functionality, but in Firefox, this namespace is replaced with "browser". Therefore, all instances of "chrome" in the code would need to be replaced with "browser" to ensure that the code is compatible with Firefox. Replace any references to Chrome-specific APIs with their Firefox equivalents. The Chrome extension API includes a number of features and APIs that are specific to Chrome, and these would need to be replaced with the corresponding Firefox APIs in order to ensure that the code is compatible with Firefox. Update the manifest file to use the correct format for Firefox. The manifest file is a JSON file that specifies various metadata and configuration information for the extension, and the format of this file is different for Chrome and Firefox. Therefore, the manifest file in the code would need to be updated to use the correct format for Firefox. Test the code to ensure that it is functioning properly in Firefox. Once the code has been converted and updated to be compatible with Firefox, it would be necessary to test the code to ensure that it is functioning properly in Firefox and that all of the desired features and functionality are working as expected. This may involve installing the extension in Firefox and testing it with a variety of inputs and scenarios to ensure that it is working properly. Overall, these steps would involve significant modifications to the code in order to make it compatible with Firefox. However, by following these steps and carefully reviewing and testing the code, it should be possible to convert the code
  - mk_stjames 4y ago
    This is the same answer format of essentially any deep technical question I've given it. Essentially: 1. Do the thing that is the first thing that is mentioned and that any first year student learning about thing hears about the thing. 2. Do some more complicated things in a hand-wavey manner that solves the problem. 3. Check to see the problem is solved. If it is not, do some more of the hand waving in step 2. 4. There may be other problems to check for in the future even if this solution works. Who knows! But I solved your problem.
    - flancian 4y ago
      Is it bad I think this is a decent high level algorithm? As in, the user then filling in details or asking the assisting model to fill them in via subsequent prompts seems like a solid start to a problem solving session.
      - mk_stjames 4y ago
        The problem is the part that I denoted as "hand waving". If you are asking it things about coding or other details it seems pretty good at, it can get pretty deep into it and thus that 'hand waving' can be resolved. If you are asking about aerospace engineering concepts at the level of a PhD thesis... it just hand-waves away problems in ways that, when pressed, it cannot give detail on. So, as far an a algorithm goes, the problem becomes determining the computational complexity of the 'hand waving' part. For writing reactJS frontend APIs it seems like it's pretty damn low and thus the AI can spit out code and even fix bugs for you. For developing something that actually took a human 7+ years of undergrad, graduate, and PhD work to ascertain and work out.... no chance. But yes that general algorithm works for all walks of life essentially and I keep getting a format like that for everything setup I ask about, as if it was trained on 'How to answer a hard technical question in these easy steps...' and it is sticking to that.
        Sugimot0 4y ago
        I'm not well versed in this but IIUC the less context/data that exists, the less it should afford the creation of a succinct response, right? This would make sense for the gap between "frontend js api" responses, and "aerospace thesis" responses. Would it be safe to assume the limiting factor with this or any algo of this type might always be availability of context/data, and these niche questions might always be an edge case? Are there alglrithms that can reliably extrapolate "new" data/context that does not exist yet and is accurate IRL? Sorry if my terminology or understanding is way off, I don't know much about this field.
unflxw 4y ago
Done: https://github.com/unflxw/chat-gpt-google-extension https://github.com/unflxw/chat-gpt-google-extension The README includes the conversation I had in order to port it. Close to zero thinking necessary. I have never worked on a browser extension before.
- frobolo 4y ago
  Bravo, and thank you for this.
- mtrovo 4y ago
  Now you got my attention, this is really impressive. Maybe this could be used on VSCode as a pair programming partner.

Waiting for someone to ask ChatGPT to make a Firefox version of this extension...

tantalor 4y ago

> You are a chat bot that rewrites Chrome extensions for other browsers...

hxugufjfjf 4y ago
You are a chat bot that rewrites Chrome extensions to firefox, how would you rewrite the following code? https://github.com/wong2/chat-gpt-google-extension https://github.com/wong2/chat-gpt-google-extension To convert the code from the GitHub repository you provided into a format that is compatible with Firefox, the following steps could be taken: Replace instances of "chrome" with "browser" in the code. In the Chrome extension API, the "chrome" namespace is used to access various features and functionality, but in Firefox, this namespace is replaced with "browser". Therefore, all instances of "chrome" in the code would need to be replaced with "browser" to ensure that the code is compatible with Firefox. Replace any references to Chrome-specific APIs with their Firefox equivalents. The Chrome extension API includes a number of features and APIs that are specific to Chrome, and these would need to be replaced with the corresponding Firefox APIs in order to ensure that the code is compatible with Firefox. Update the manifest file to use the correct format for Firefox. The manifest file is a JSON file that specifies various metadata and configuration information for the extension, and the format of this file is different for Chrome and Firefox. Therefore, the manifest file in the code would need to be updated to use the correct format for Firefox. Test the code to ensure that it is functioning properly in Firefox. Once the code has been converted and updated to be compatible with Firefox, it would be necessary to test the code to ensure that it is functioning properly in Firefox and that all of the desired features and functionality are working as expected. This may involve installing the extension in Firefox and testing it with a variety of inputs and scenarios to ensure that it is working properly. Overall, these steps would involve significant modifications to the code in order to make it compatible with Firefox. However, by following these steps and carefully reviewing and testing the code, it should be possible to convert the code
- mk_stjames 4y ago
  This is the same answer format of essentially any deep technical question I've given it. Essentially: 1. Do the thing that is the first thing that is mentioned and that any first year student learning about thing hears about the thing. 2. Do some more complicated things in a hand-wavey manner that solves the problem. 3. Check to see the problem is solved. If it is not, do some more of the hand waving in step 2. 4. There may be other problems to check for in the future even if this solution works. Who knows! But I solved your problem.
  - flancian 4y ago
    Is it bad I think this is a decent high level algorithm? As in, the user then filling in details or asking the assisting model to fill them in via subsequent prompts seems like a solid start to a problem solving session.
    - mk_stjames 4y ago
      The problem is the part that I denoted as "hand waving". If you are asking it things about coding or other details it seems pretty good at, it can get pretty deep into it and thus that 'hand waving' can be resolved. If you are asking about aerospace engineering concepts at the level of a PhD thesis... it just hand-waves away problems in ways that, when pressed, it cannot give detail on. So, as far an a algorithm goes, the problem becomes determining the computational complexity of the 'hand waving' part. For writing reactJS frontend APIs it seems like it's pretty damn low and thus the AI can spit out code and even fix bugs for you. For developing something that actually took a human 7+ years of undergrad, graduate, and PhD work to ascertain and work out.... no chance. But yes that general algorithm works for all walks of life essentially and I keep getting a format like that for everything setup I ask about, as if it was trained on 'How to answer a hard technical question in these easy steps...' and it is sticking to that.
      - Sugimot0 4y ago
        I'm not well versed in this but IIUC the less context/data that exists, the less it should afford the creation of a succinct response, right? This would make sense for the gap between "frontend js api" responses, and "aerospace thesis" responses. Would it be safe to assume the limiting factor with this or any algo of this type might always be availability of context/data, and these niche questions might always be an edge case? Are there alglrithms that can reliably extrapolate "new" data/context that does not exist yet and is accurate IRL? Sorry if my terminology or understanding is way off, I don't know much about this field.

unflxw 4y ago

Done: https://github.com/unflxw/chat-gpt-google-extension https://github.com/unflxw/chat-gpt-google-extension The README includes the conversation I had in order to port it. Close to zero thinking necessary. I have never worked on a browser extension before.

frobolo 4y ago
Bravo, and thank you for this.
mtrovo 4y ago
Now you got my attention, this is really impressive. Maybe this could be used on VSCode as a pair programming partner.