Yesterday, I tried to build a WebAssembly version of dot-slash-badges. While compilation succeeded, the resulting binary had a size of almost 5 MB. That's too much for an application that, for the average user, likely yields far less than 100KB overall output (about 10KB per badge). Unfortunately, it didn't compile with TinyGo. So, it seems, a purely client-side GUI for dot-slash-badges won't be feasible. 🙁
I really would like to provide a GUI for dot-slash-badges though. But I would need to set up and maintain a server for that, which is not really worth it for just that service alone. But maybe @codeberg would be interested in getting a "badges.codeberg.org" tool? 😉
@codeberg That's great! 👍
Its deployment could work similar to build-deploy-reg-server.
Does that sound like a good way? :-)
@codeberg Alright, nice! :-)
Then I'll start working on the GUI and Rest API and I'll let you know once we can start discussing next steps about deployment.
Cool, no problem. It's there for the taking :-). I'll try to setup the proper go env soon. Maybe I can contribute some more on further dev then.
One thing that bothers me is that the vertical spacing is like 1 pixel off :D also the 2 font weights slightly (optically) render different.
So I'll take a peek at the text metrics to see if something is doable there
Please also see https://codeberg.org/Codeberg/Community/issues/456 to save duplicated efforts!
API and frontend for the dot-slash-badges webservice will be able to be deployed independently. So it should be possible to deploy the API while re-using the frontend component within a unified badge generator, as hinted in the linked issue. That way, the webservice can be developed independently, while still being nicely integrated within Codeberg.
Mastodon ist ein soziales Netzwerk. Es basiert auf offenen Web-Protokollen und freier, quelloffener Software. Es ist dezentral (so wie E-Mail!).