Currying to OPS returns an HTTP 500 Internal Server Error

A user on the RED forums reported this.

./redcurry.rb "URL" RED OPS
CURRYING: Super Meat Boy! Choice Piano Cuts | redacted.ch ===> orpheus.network ... FAILED: ["./redcurry.rb:113:in `post'", "./redcurry.rb:421:in `curry'", "./redcurry.rb:455:in `<main>'"]
Target tracker returned HTTP 500 Internal Server Error

I personally ran into this error as well, so I don't think it's user error.

---

Update: I just checked the OPS torrent upload form, and it looks like the form now includes a torrent-new hidden field, which is set to value="1".

@_mclovin Do you think it would be a good idea to add this torrent-new field to the target_payload Hash, but only when currying to OPS?