04:18:24 <m-relay> <b​asses:matrix.org> ahh people are NOTICING https://libreddit.bus-hit.me/r/Monero/comments/1df253t/seems_like_the_merchants_page_needs_a_refresh/
04:19:54 <m-relay> <r​ottenwheel:kernal.eu> Must be plowsof's fault.
04:20:46 <m-relay> <b​asses:matrix.org> bruh that monero.social delay... 4 days
05:27:13 <plowsof> Currently looking into translations 
07:55:16 <m-relay> <p​lowsof:matrix.org> so the overall goal for looking into "weblate webhooks" is to get po4a running in a workflow which then makes a PR to -site after weblate pushes .po/.pot file changes to an external repo (a github account i create or so)
07:56:29 <m-relay> <p​lowsof:matrix.org> ive done similar tasks for the "copyright" updater so no major issues there, im now working through some po4a complains with our repo. a new update doesnt like in-line yaml lists https://github.com/plowsof/monero-site/actions/runs/9506969951/job/26205368741#step:8:107 , im making issues / checking who i can blame for this
07:57:48 <m-relay> <p​lowsof:matrix.org> even if weblate was online, the actual problem is webhooks and automated PR's with changes - instead of - a site maintainer, remembering to do it every several months on their personal machine with local changes/scripts not pushed to -site
07:58:11 <m-relay> <p​lowsof:matrix.org> the whole process is confusing^ so we need it in workflows, in the open
07:59:15 <m-relay> <p​lowsof:matrix.org> the eventual "PR" that is made to core, will have "fuzzy" things in it, and require edits, to be done in the open on GH for the next generation of -site maintainers to learn from, instead of what we have now