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

Canvas

2095 readers
1 users here now

Canvas — The Fediverse’s r/place


2024 Concluded!


Get a print!


Links

Timelapses

founded 1 year ago
MODERATORS
 

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)

(page 3) 13 comments
sorted by: hot top controversial new old
[–] [email protected] 0 points 6 months ago (1 children)

It would be amazing if parts of it could be animated. Maybe multiple layers of canvases (say, 5 frames, shown over a second). Each with their own images, which could be viewed as a flipbook.

Instead of going for a larger canvas, go for more layers.

Just a thought.

load more comments (1 replies)
[–] [email protected] 0 points 6 months ago* (last edited 6 months ago)

Thanks for making it open source! I’m curious how complex the authentication stuff was. I didn’t place many pixels but it was fun to peek in and see what changed every once in a while! Would definitely be a fan of more in the future, though I don’t have any ideas

[–] [email protected] 0 points 6 months ago (3 children)

On mobile I kept opening the whois pixel by accident when dragging. I often tap and hold to initiate a drag because I'm still looking at the art, but when i drag away and let go, it opens the whois thing. I think if you drag a certain screen-space distance away it should cancel the whois pixel lookup.

The heatmap I found too hard to tell where recent pixels were placed. I think at 100% opacity the "cold" pixels should be dark blue instead of their actual color.

A couple times I placed a dot, realized I actually didn't want it there and ran out of time to undo, which felt bad having to wait 30s. I wish it was a bit longer.

When you try to place a pixel a few milliseconds too early I feel like it should queue it and wait the few milliseconds for you.

I'm not super sure on the canvas having transparency. Most people treated the canvas as white, not transparent. If you wanted a white-on-white drawing, people will just make an outline.

Maybe a concept worth testing: if you place a pixel next to your own pixels, you get a (slightly) reduced cooldown, that way you get an extra boost when completing your art. (At the same time, I think there is beauty in the canvas being as simple as possible:)

load more comments (3 replies)
[–] [email protected] 0 points 6 months ago (2 children)

I often got the "you've already placed a pixel of that color there" error, even though I never touched this area. I also couldn't fix my own pixelart easily because of this.

[–] [email protected] 0 points 6 months ago

You could get around that bug by choosing a different color and then pressing undo. After that it reverted to the correct color.

load more comments (1 replies)
[–] [email protected] 0 points 6 months ago (1 children)

The event was fun for the first 48 hours - before the expansion. After that it was mostly policing and defending existing art. I would prefer a 48 hour canvas without expansion.

That said, it was fun anyways. Thanks for all your work and thanks to grant for setting everything up and fixing issues on the fly.

load more comments (1 replies)
[–] [email protected] 0 points 6 months ago (4 children)

I'd be keen to run/test a local version, what do I need in the .env.local as a minimum to get up and running?

[–] [email protected] 0 points 6 months ago* (last edited 6 months ago)

It looks like the compose file has REDIS_HOST and DATABASE_URL and point to included services. There’s also a few in the dockerfile for setting PORT (3000) and some node stuff I don’t understand

load more comments (3 replies)
[–] [email protected] 0 points 6 months ago (8 children)

Escalating timers are an antipattern. It punishes anyone who looks away for more than thirty seconds - and thirty seconds per click is not exactly a brisk pace for maintaining attention.

Other than that, good shit, well done. Undo was a welcome surprise. Ditto the repetition prevention.

No wait, one other thing. (Complaint sandwich!) Scaling should be in integer powers. Everything but fully-zoomed-out and extremely-blown-up looked lumpy and distracting. Especially with all the pixel art going on.

[–] [email protected] 0 points 6 months ago (5 children)

One effect of this is that someone steadily editing got more pixels than someone editing in batches, which felt like a feature when defending against trolls.

load more comments (5 replies)
[–] [email protected] 0 points 6 months ago (3 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.

load more comments (3 replies)
[–] [email protected] 0 points 6 months ago (1 children)

I think it was 30s between every pixel at the start.

[–] [email protected] 0 points 6 months ago

It was sort of, but it was a bug. If you just left them, you'd get one every 33ish seconds until you had 6. But if you had 2 then used one, you'd have to wait 66 seconds until you got another, unless you used your last one then it was back to 33.

It was fixed partway through to be as originally intended.

load more comments (5 replies)
load more comments
view more: ‹ prev next ›