this post was submitted on 16 Jul 2024
105 points (96.5% liked)

Canvas

2097 readers
1 users here now

Canvas — The Fediverse’s r/place

2024 Concluded!

Get a print!

Links

Timelapses

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
105
Suggestions for Canvas and future events! (programming.dev)
submitted 5 months ago by [email protected] to c/[email protected]
123 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] 4 points 5 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.

[–] mindbleach 7 points 5 months ago* (last edited 5 months ago) (1 children)

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.

[–] [email protected] 4 points 5 months ago* (last edited 5 months ago) (1 children)

I get why you're saying this, and I agree with base reason. However, I feel like fixing the problem by removing the feature is not the way to go, as I think that active playing should be rewarded.

Regarding the base time (30s vs. 40s): I proposed 40s because the total waiting time would be roughly the same. It could be also 20s, if necessary/desired, up to the devs.

Additionally it would be great if there was an audible "ping" once you get a new pixel. Then regardless of the timer or how it progresses people would feel freer to do other stuff while checking the canvas.

[–] mindbleach 5 points 5 months ago

One literal pixel every thirty seconds is not "active."

You went people to drool when a bell rings.

Encouraging users to obsess or react is plainly an addiction mechanic. In a collaborative MS Paint session. Tweaking the details of it misses what's wrong with it. It's an antifeature. It's a mistake.

Just give people one pixel every thirty seconds. "Active" means they check at least every couple minutes, at their convenience, where they will have up to six. If they step away for an hour they don't get hundreds.