• Joined on 2023-07-08
zephyr pushed to api-fixups at ligmo/ligmo 2025-05-10 22:57:45 -04:00
40ce7e141d api: include content hash in emote sets' emotes
zephyr pushed to api-fixups at ligmo/ligmo 2025-05-10 22:21:37 -04:00
109374623f api: version
566f969715 api: update typespec & other dependencies
aceda8c083 emote management api (#27)
1213426c33 go rest api scaffold (#25)
Compare 4 commits »
zephyr pushed to main at ligmo/ligmo 2025-05-10 19:05:00 -04:00
aceda8c083 emote management api (#27)
zephyr deleted branch api-emote from ligmo/ligmo 2025-05-10 19:05:00 -04:00
zephyr merged pull request ligmo/ligmo#27 2025-05-10 19:04:59 -04:00
emote management api
zephyr commented on pull request ligmo/ligmo#27 2025-05-10 19:03:22 -04:00
emote management api

Regardless, if there's a change for this, I think it's at the DB schema rather than the API.

zephyr commented on pull request ligmo/ligmo#27 2025-05-10 18:49:50 -04:00
emote management api

The only restriction is that a single connection, i.e. Ligmotes account × external (Twitch) account, can have at most one active emote set. The same Ligmotes account can have multiple active sets…

zephyr pushed to api-emote at ligmo/ligmo 2025-05-10 18:39:40 -04:00
d11b9ad905 api: english
88ffc91e29 api: move remaining models to global with visibility
b0964723cf api: better docs on ErrAuth
22ea974b7d api: define delete emote endpoint
471d35f48c api: define update emote endpoint
Compare 9 commits »
zephyr merged pull request ligmo/ligmo#25 2025-05-10 18:38:21 -04:00
go rest api scaffold
zephyr pushed to main at ligmo/ligmo 2025-05-10 18:38:21 -04:00
1213426c33 go rest api scaffold (#25)
zephyr deleted branch rest-api-scaffold from ligmo/ligmo 2025-05-10 18:38:21 -04:00
zephyr commented on pull request ligmo/ligmo#27 2025-05-10 18:37:31 -04:00
emote management api

You mean like have an emote set for the user rather than for the user×platform?

zephyr opened issue ligmo/ligmo#29 2025-05-10 16:07:22 -04:00
version the api
zephyr opened issue ligmo/ligmo#28 2025-05-10 16:04:36 -04:00
port db schema to postgres
zephyr created branch api-fixups in ligmo/ligmo 2025-05-10 00:26:45 -04:00
zephyr pushed to api-fixups at ligmo/ligmo 2025-05-10 00:26:45 -04:00
bfb85fc036 api: version
5a887b74ca api: update typespec & other dependencies
Compare 2 commits »
zephyr commented on issue ligmo/ligmo#1 2025-05-09 23:40:24 -04:00
thoughts

actual limit of emote slots is 50000, not infinite, token bucket rate limit of 1k emotes added per week, across all your sets, by any method; 90 day expiry implies you can only get up to ~13k…

zephyr pushed to api-emote at ligmo/ligmo 2025-05-09 14:57:44 -04:00
dd5dc0324b api: english
zephyr pushed to api-emote at ligmo/ligmo 2025-05-09 14:38:52 -04:00
5c866ec499 api: move remaining models to global with visibility
zephyr approved ligmo/ligmo#25 2025-05-09 13:21:37 -04:00
go rest api scaffold

this is just setting up and running the tool, right? there are some things i would do differently if i were writing this code myself, particularly wrt interfaces, but it seems fine for generated code. probably good to get more eyes on this, though.