thank you for your suggestions! i've created issues in the tracker for each one so i can keep track of them :)
I'll be working on some better moderation tooling for next year's canvas (+ any other fediverse event) but with the nature of this, the tooling won't be in the open :/
here's the issue i created for enabling these external moderation tools
if you have any suggestions (execution or specific checks) feel free to shoot me a DM on matrix
thank you (and everyone else in this thread) for the constructive feedback!
i've added the timers as an issue in the tracker to help with keeping track of everything
i think i got the main points given in this thread, but if theres something you think is missing feel free to reply to this so i can add it 👍
i've also added the weird zooming issue also
i'm glad you enjoyed the event, it was really fun to run (even with the issues 😅)
i've added your suggestion to the issue tracker so i can keep track of it
I've created issues in the issue tracker to keep track of these for next year :)
- Mobile Pixel Whois triggers too easily
- Heatmap colors
- Increase undo cooldown
- Grace period for pixel cooldowns
- No white background
- Idea: adjacent self pixels should receive a slight reduced cooldown
thank you for the suggestions!
Sorry, I phrased it badly 😅
There's no user table (from the server) but each pixel is tagged with whoever placed the pixel
I've edited my original post so it doesn't confuse more people
There is no tools right now that allow that to happen
but the database dump is tagged in this post which would allow for people to make those tools 🙏
The matrix homeserver that was being used was in the same VM as the rest of my fediverse services, which all of them got hammered when the event started
Before next years event (or any other event) I am going to be getting a dedicated server for all of my fediverse services to prevent this
ooo that sounds fun
i've created an issue for this so i can keep track of it :)