I like the escalating time, but the pacing issue is a fair point.

So perhaps the escalation could be delayed? Give it a tiny larger timer (let’s say, 40s?), and make the second pixel take as much time as the first. Like this:

• current times - 30s, 60s, 90s, 120s, 150s, 180s; total 630s
• my proposal - 40s, 40s, 80s, 120s, 160s, 200s; total 640s

This way you’d be only getting less pixels per minute after 80s of inactivity, not 30s.

I think I agree on the cooldowns. Often times I wanted to step away and let the pixels accumulate, but it’s hard to resist when you realize you’d be missing out on double or triple the amount of pixels you could be placing. If the goal was to reward the player for actively placing pixels, all I can say is it didn’t feel very rewarding.

I kinda disagree about the integer scaling. 1x to 2x zoom is a very big shift without any in-between. It would also feel strange on pinch-to-zoom on mobile without in-between. I think instead it could snap to an integer scaling, or have a zoom slider that works to integer scaling. Overall though I agree, having a way to snap into integer scaling makes the pixel art look better

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

To get it actually running you need to do more than set up just the env but ive got what I needed to do here

share.ategon.dev/u/IzcMWM.md

If you want to allow logging in so you can test the features that get unlocked from that heres some code changes to get it working so you can bypass setting up openid

share.ategon.dev/u/W7IODE.md

Client will be up at localhost:5173

there’s an issue to write instructions on how to setup the environment

the server requires the authentication server to be fediverse-auth with the current implementation, but there’s an issue to add support for other providers

(once the documentation is written i’ll be putting it in #canvas-meta:aftermath.gg to keep people in the loop)

i’ll keep a note of that, a couple people have also suggested alternatives to canvas expansion

i’m glad you enjoyed the event, it was really fun to run (and fix bugs for) :)

i’ve created an issue to track this :)

this error was being sent by the server, so somewhere along the chain your computer got desynced from the pixels the server was aware about

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!

that’s a cool take on canvas, i like it

i’ve created an issue for it to keep track of it :)

(for completeness as i’m going through all the comments)

there’s a suggestion for that and it should be implemented for next year 👍

If you undo the changes done by a bot it could cause chaos. It is better to let users know it needs to be fixed.

Also you could do some sort of proof of work to make it unfeasible to have a bunch of alts.

there’s an issue to add support for undoing pixels with bans, but that would mainly get used in very bad circumstances and wouldn’t be the default

as others have mentioned, there’s not going to be anything that automatically does actions against IPs, instead opting for a flag that moderations can look into further

i’ve also mentioned somewhere else in the thread, but i wouldn’t want to punish new accounts as, especially this year, it brings new people to the Fediverse and i don’t want to hamper the growth of that :) (it also isn’t very possible to get a reliable creation date of new accounts because of how the fediverse is designed)

i’ve created an issue for the lower cooldowns for smaller instances

sounds like a neat idea imo :)

and for the second suggestion, i’d like to avoid imposing restrictions on new accounts as Canvas has brought a lot of people to the fediverse and i wouldn’t want to hamper their contributions because they just found out about it

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

ooo that sounds fun

i’ve created an issue for this so i can keep track of it :)