kuneho

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!

I know, I know. I really shouldn't use NTFS with Linux if I plan to write to it, especially not my only backup drive, which is my external media drive for libreELEC as well.

So I was moving/copying/renaming stuff through SMB on my libreELEC machine. And then suddenly I noticed 50 episodes of old-school Sonic animated series just... disappeared. Strange, but I continued renaming files, and those too poof nonexistent anymore.

Okay, maybe a Dolphin bug - I thought, since I was using Dolphin for SMB. But same from Android (I'm using Solid Explorer)

Then, Ghost In The Shell Stand Alone Complex too disappeared. Then some episode of Serial Experiments Lain.

Star Trek Discovery? Fucking gone, tho I didn't mind that one. All of the files are 0B. Then Regular Show.

Now, this was the point where I needed to step in. Linux just didn't see the files.

Oh well, I have a Windows 10 PC I use for work so it was a time for bringing the drive "home" and give it some chkdsk, in the meantime I was really hoping it wouldn't just destroy my 4TB backup drive. Wasn't sure it would work, but that was pretty much my only hope and idea. Trying to access those folders and files from Windows gave me error messages before the check.

The check and fix dialog of chkdsk was also kinda fucked, the progressbar jumped around, didn't make any sense BUT it restored my files. Hooray!

Except SAC, it was still unreadable from Windows, but! Linux does see all the episodes so I guess it's a win... of some sort. It sill bothers me there is some - from Windows's point of view - invalid files and folders on my BACKUP disk, but this will be another story.

It turned out, libreELEC is using ntfs-3 (and not 3g), which is famous for this kind of errors - files disappearing and the filesystem becoming funky.

So, I ordered a drive just for my media and media PC, tho no idea how to format it (to be readable from anywhere else - maybe exFAT?)

But this scared me like hell 😅

Just wanted to share this with you guys, there's no moral of the story, except do not use ntfs heavily under Linux, or at least do not write it a lot, which is a known thing since forever, I was just a lazy ass, don't be like me, please, unless you have a Windows machine around and some luck. But relying on these two, well...

Cheers!

Update: I formatted my new media drive to ext4. In the end, it'll be a fixed disk under my TV in a linux box, this seemed to be the best choice. I don't think I'll pick it out and use it elsewhere that much or at all.

Hi guys! Hope this is the appropriate place to ask this question, but here it goes.

I have a Dell Inspiron 7520 laptop with integrated Intel and ATI graphics.

Recently I've installed Debian 12 on it, using Plasma.

Everything is fine and dandy, but there's a problem; when the system comes back from sleep, or I boot up the PC with the lid closed down, the screen never comes back. The system is running, but there is no screen.

Also, it's not just a blank screen, it does not get power, no backlight, no image on the screen if I shine a flashlight onto it and look hard.

Interrestingly, if I switch sessions to any ttys, the screen comes back and the terminal session displays fine. If I Alt+F7 back to the graphical session, the screen turns off again.

In theory, every graphics driver should be installed, I have non-free-firmware in my sources.list, all the packages that the Debian documentation mentions are installed.

Don't know, if relevant, but same on both X11 and Wayland.

Any ideas?

Thanks, guys :)

Some specs of the machine:

• CPU: Intel Core i7 (3rd Gen) 3612QM / 2.1 GHz
• GPU: Intel HD Graphics 4000 + AMD Radeon HD 7730M (switchable*)
• RAM: 16GB**

*: Not sure this switchable thingamajig works, tho. Haven't really tested, the only purpose of this machine is to start OBS and begin outputting video on NDI.

**: Though 16GB is not really supported on paper I guess and had some really funky issues before, not sure what was the real purpose, the system is rock solid since the last few OS installs.

Isten nyugosztalja, remélem jól érzi magát az öreg a legendák közt.

I'm still blown away by this track; it's just amazing IMO

Not sure if it's NSFW tho...

by Tim Follin