4 ms·

Its crazy that I built this without knowing any rust or WASM using ChatGPT

4 points by morphicpro 3y ago

hdlothia 3y ago
What am I supposed to see after I click analyzer colors? I'm on mobile chrome and nothing happens for me
- morphicpro 3y ago
  well if it was working for you, you would have see a color swatch of unique colors. Given this is running in wasm via a rust app I'm not sure about browser compatibility. Give it a try on maybe a desktop? or possibility try again as I pushed a bug just two moments ago and maybe thats why. Github.io takes a moment to update Edit: I tried on my phone via firefox and it worked so maybe try again.
  - hdlothia 3y ago
    I tried it again and it worked! Cool project!
    - morphicpro 3y ago
      Awesome, thanks for the follow up.
  - BandButcher 3y ago
    Curious, did you use chatgpt to fix the bug? Or did you ask it what could be wrong? Or did you do it yourself
    - morphicpro 3y ago
      it was a github issue related to paths because I tried to point to the pkg dir. Github pages didnt' like it.
      - morphicpro 3y ago
        I need to just stop being lazy and make an action to handle the bins.
BandButcher 3y ago
Very cool, also be careful with handling raw binary data chatgpt
- morphicpro 3y ago
  Given its a wasm app running client side completely from static assets, I'm not worried at all. Do you know of any risk in terms of attack vectors? I guess maybe someone could exploit the client by some other means and then take advantage of the export in some manner the could end up getting the client to download an "image" with embed script. That's also just conjecture I have no clue.
  - BandButcher 3y ago
    most likely there are no security issues in the code, but there could be potentially, see this link: https://security.stackexchange.com/a/81926 https://security.stackexchange.com/a/81926 tldr: its possible for images to not really be images. Whenever you are getting user input, its usually best practice to always validate it "server side", in this case, the rust code, which is compiled machine code. An attacker could possibly upload a malicious "image" and if there are rust functions that operate on that data blindly, it could lead to a pwnage (ex. access to memory outside the browser/colorizer program)

4 points by morphicpro 3y ago

hdlothia 3y ago

What am I supposed to see after I click analyzer colors? I'm on mobile chrome and nothing happens for me

morphicpro 3y ago
well if it was working for you, you would have see a color swatch of unique colors. Given this is running in wasm via a rust app I'm not sure about browser compatibility. Give it a try on maybe a desktop? or possibility try again as I pushed a bug just two moments ago and maybe thats why. Github.io takes a moment to update Edit: I tried on my phone via firefox and it worked so maybe try again.
- hdlothia 3y ago
  I tried it again and it worked! Cool project!
  - morphicpro 3y ago
    Awesome, thanks for the follow up.
- BandButcher 3y ago
  Curious, did you use chatgpt to fix the bug? Or did you ask it what could be wrong? Or did you do it yourself
  - morphicpro 3y ago
    it was a github issue related to paths because I tried to point to the pkg dir. Github pages didnt' like it.
    - morphicpro 3y ago
      I need to just stop being lazy and make an action to handle the bins.

BandButcher 3y ago

Very cool, also be careful with handling raw binary data chatgpt

morphicpro 3y ago
Given its a wasm app running client side completely from static assets, I'm not worried at all. Do you know of any risk in terms of attack vectors? I guess maybe someone could exploit the client by some other means and then take advantage of the export in some manner the could end up getting the client to download an "image" with embed script. That's also just conjecture I have no clue.
- BandButcher 3y ago
  most likely there are no security issues in the code, but there could be potentially, see this link: https://security.stackexchange.com/a/81926 https://security.stackexchange.com/a/81926 tldr: its possible for images to not really be images. Whenever you are getting user input, its usually best practice to always validate it "server side", in this case, the rust code, which is compiled machine code. An attacker could possibly upload a malicious "image" and if there are rust functions that operate on that data blindly, it could lead to a pwnage (ex. access to memory outside the browser/colorizer program)