It's a bit janky but there's limited text support working in the dev version of the API thanks to some tips from @lunahd
It still needs text sanitation and a bunch of other things but, at least as a proof of concept, it could be an exciting thing coming to the mixer someday.
I still think it's nuts that #Python's best solutions for rendering #SVG are a bunch of wrappers around CairoSVG with the two next best solutions being use Inkscape from the command line and wand, a wrapper around ImageMagick.
My favorite part of the kissing booth is the currency difference. In my country, "50ct" would indicate there's a count of 50 items in the package you're buying, since we use "50¢" for half of a dollar instead of "50ct" for half of a euro.
So, you are welcome to use the kissing both, but you've got to buy it in bulk.
Yeah, yeah, famous and influential anime. But every time I see a reference to Evangelion, I just can't help but think of that Ken Ashcorp song, Absolute Territory. Now #neomoji can enjoy the song too.
I'm not a skilled artist like some of the other #neomoji creators but I'm still sharing what I've made in this git repo. I think that's how CC BY-NC-SA 4.0 works? I know that I'm supposed to credit people whose works I derived mine from and my stuff needs to be shared too.
One of the things people asked for in the poll on what #neomoji content they wanted was interviews with creators.
Much like I'm not an artist, I'm not a journalist either. Are any fans of neomoji actually skilled at this sort of thing? I'm not trying to Chotiner these people just having fun or anything like that. I just figure that it'd be more enjoyable to read if someone who knew what they were doing was involved.
I wish I knew what motivated me to get lots of work done some days and very little on others. But today was a very productive one
/create/random which gives you a random neomoji
/create can now handle GET or POST part specifications
/list returns a dictionary of body part type -> list of parts of that type
/list/<level></level> that returns a dictionary of body part -> details for a given type of body part. The details vary depending on the type of body part.
/part/<level>/<name></name></level> will give you the png of the part you asked for
/part/<level>/<name>/<variant></variant></name></level> will give you the png of the part you asked for in the specific variety you asked for
I set up a git repo on Codeberg so I'm not the only one who can see it. I might have even set it up right? I still don't understand git.
Added support for front and hats in a way that makes adding new categories easier in the future
That's easily the most productive I've been in at least a few months.