100s of download and no one can provide any reviews?
Atleast respect the maker, give some feedback that helps fellow folks and the maker! People don't be like that!
GGUFs are heavily scraped upon the first day of upload all over HF, plus having HF track downloads per file rather than entire repo downloads tends to inflate numbers quite a bit. It's likely in the 10s or 1s of actual people downloading as opposed to scrapers.
I should also point out that it's quite normal in human nature to shy away from talking about your sexual interests (regardless of how much the internet makes you think otherwise). Not many people are so open about exposing their Japanese idol fetish just to give some feedback. It's best to respect people's privacy if they use this model.
Yeah... Well, also it's a bit tricky too, as really testing a model enough to provide feedback takes time and more often than not if nobody is saying much it's probably just not impressing enough or doing anything crazy.
Regarding this model, as for the other in the series, I personally have issues with inconsistent roleplay response formatting, not using italics when I expect it to for example, so far Stheno 3.2 remains a lot more consistent and delivers a good and uncensored experience for all roleplay needs, it's my general benchmark/reference and point of comparison.
Since I have all imaginable the fetishes it'd be quicker to say the ones I don't have, haha.
Considering my issues are mostly with response formatting I don't feel like bashing or complaining about that since those can be a non-issue for others or when the model is used in other settings, perhaps to generate shorter responses or with different formatting styles.
I downloaded the model a day ago, and got some very familiar slop messages that I'm used to from Stheno and Magnum merges.
It may be a good model, but I get shivers down my spine every single time I see models that are on top of that dataset. Didn't want to test it further then.
Sure, I whisper in your ear and it sends shivers down your spine. If you need custom stopping strings on a L3 model, you fucked up your merge/finetune, there's no way around it. and maybe we should stop pretending otherwise to push the quality up, instead of down? But I understand that the possibilities are endless.
(It also confuses KoboldCPP so you have to manually enter the rope scaling yourself, which is kinda annoying; but fine.)