you can still use the tinybots one for ratings, and the new one for gens
db0
I suspect some misconfiguration on their pictrs.
Depending on the model that you choose, you can need different settings. For example pony requires clip_skip 2, while flux requires euler_a and cfg 1.
Also make sure you're using artbot.site
If only we had an option to disable downvotes from non-subscribers!
Another solution would be to set it up via a bot. I could make a bot that you invite to your community and it automatically bans anyone who downvotes more than some % of posts, and allow that to be configurable by the mod. Not quite sure I can get that info from the API, but if not I could try my hand at a plugin.
You can't disable downvotes per community only. Only instance-wide
People keep insisting how little time it takes them when the argument against electoralism is toward the massive amount of volunteer work wasted around it and the show of support to the concept itself.
That's why I say if you don't restrict to single process. As to why something which might be slightly more inefficient (it's not going to be that much), it's because of ease of development and pool of potential developers to help you with it.
honestly, we really just need a separation between "report to mod" and "report to mod & admins" or smt.
That's terrible, how did it mess out so bad? @[email protected] draw for me a green dragon on a rocky mountain-top style:flux
I am using it in the AI Horde for mostly immutable fields which I don't need to search often (although sometimes I might use them for DB filtering).
They work well in the way I use them, no complains so far.
Theoretically artbot.site is still missing some of the features of the old one. It's a completely fresh refactor. Eventually ratings and the rest will be also available there I hope