Hey!
Not sure if this is the palce to ask questions, but I have one.
I can't quite figure out how to submit ratings for generated images.
According to the API docs, the /v2/generate/rate/{id}
endpoint is for submitting ratings, but I can't figure out how to actually call this enpoint.
For starters, what is {id} in this case?
I've checked the source at github, and to my understanding it's a WaitingPrompt
id, which, if I'm correct is the id what /api/v2/generate/async
gives back in its response.
Now the API docs tells me I can submit a set of ratings and also a best one from that set. Is this means that if I generate multiple images with one request, I can rate only those images? And should I use the UUID of the images in each rating object, the id I get back from /v2/generate/status/{id}
in each generation object?
Also, should I specify the apikey in headers?
I tried to send POST requests to https://aihorde.net/api/v2/generate/rate/%7Bid%7D
, but I always get back the following message:
{'message':'The browser (or proxy) sent a request that this server could not understand.'}
In the request URL, I tried to use all the IDs I could think of. Job IDs, image IDs... I also realized in the meantime that ArtBot too generates UUIDs for itself...
My "final" request looked like this:
- in the URL, I used the job id of my image generation request
- In the message, I have put one rating, for which ID I used the id what I got in
/v2/generate/status/{id}
response. (generations[0].id)
As for why I try to send in ratings manually; the rating feature is broken in ArtBot (CORS errors, in all browser). As well as everywhere else.
I see references to the v1 API in websites that can in theory send in ratings to Horde, as well in the AI-Horde source code.
So, I'm kinda lost and confused with this rating thing. Maybe I'm doing things entirely wrong.
But anyway. Any help or answer is appreciated! :)
Thanks!
Do you have any custom DNS set up for your wireless connection? If so, it's worth a try to clear it. 3rd party DNSs are prone to just stop working and this can result your 3DS not being able to communicate with... anything.
Also, you can try this too, though you suggest that you can connect to your wireless access point, but also worth a try:
I'm not sure what it does, but some reported this option fixed their network issues. Different kind of issues, however...