this post was submitted on 16 Jul 2024
1 points (100.0% liked)

Canvas

2249 readers
1 users here now

Canvas — The Fediverse’s r/place

2024 Concluded!

Get a print!

Links

Timelapses

founded 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
1
Suggestions for Canvas and future events! (programming.dev)
submitted 11 months ago by [email protected] to c/[email protected]
7 comments fedilink hide all child comments
 

Hey everyone! Thanks for participating in Canvas. I wanted to make a thread to collect together suggestions people have that can be worked on before the next Canvas.

Feel free to also throw in suggestions for future Events we can build and run for the fediverse.

Ill be collecting suggestions together and making issues for them in the repository for myself or some other contributors to work on (the projects open source so anyones free to contribute! https://git.sc07.company/sc07/canvas Feel free to reach out to me and I can help get you set up with the codebase)

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 0 points 11 months ago (1 children)

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.

[–] [email protected] 1 points 11 months ago* (last edited 11 months ago)

Longer waits would be worse.

It should be one every thirty seconds until you hit some limit. Do not incentivize continuously staring at a timer. Do not incentivize obsessively checking a timer. Just rate-limit people in the simplest way that could possibly work.