105

Suggestions for Canvas and future events! (programming.dev)

submitted 3 months ago by Ategon@programming.dev to c/canvas@toast.ooo

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)

(page 2) 50 comments

sorted by: hot top controversial new old

[-] Snoopy@jlai.lu 3 points 3 months ago

I would like a shorter timer for small instance. So bigger communities have a longer timer and small a shorter one. But i affraid it wont help at all.

Protected area as in minetest. It would help against grief.

Also for new account with 0 coms, just created during this canva event : restriction, second layer for drawing before approval...something like that ?

[-] possiblylinux127@lemmy.zip 2 points 3 months ago

I wonder if we could do some sort of competition between instances? At the end we could all vote.

[-] Snoopy@jlai.lu 2 points 3 months ago

Great idea we can organize that between our instance instead of waiting for the next year. :D

I quickly drafted some rules :

the competitive instance chose together a subject
the pixel art must be original and not copy-pasted from web. we don't use a template : hosted and template desactivated.each instance will have their private layer. Once the event is over, our draw will be revealed.
2-3 day to draw and send the result
1 week for voting

I love drawing, i'm quite good at it, except perspective :)

[-] grant@toast.ooo 2 points 2 months ago

Sounds like a cool concept, i've added it to the issue tracker to not lose it :)

load more comments (1 replies)

[-] grant@toast.ooo 2 points 2 months ago

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

load more comments (1 replies)

[-] lvxferre@mander.xyz 2 points 3 months ago

Suggestions:

When getting rid of bots, undo their changes.
Assign the pixel timer based also on IP, not just account. That should discourage people who used multiple accounts just to have more pixels.
Don't let freshly created accounts to place pixels. They compound with both issues above.

[-] possiblylinux127@lemmy.zip 2 points 3 months ago* (last edited 3 months ago)

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.

load more comments (2 replies)

[-] grant@toast.ooo 2 points 2 months ago

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)

[-] lvxferre@mander.xyz 2 points 2 months ago

OK! At least the other batch of suggestions was more useful :) Those are fair points.

load more comments (4 replies)

[-] jonathanvmv8f@lemm.ee 2 points 3 months ago

Not suggesting any big things here... All I propose is to have the options for toggling the canvas overlays (empty canvas, heat, template) directly within the canvas editing screen instead of putting it in the sidebar, kinda like Google Maps. I think the sidebar version would be preferred in mobiles, so you could make this desktop only.

Alternatively, you could allow the user to place pixels on the canvas even while the sidebar is opened, like the way it was for the first 48 hours of the event. Also ensure the right side of the color palette is not hidden by the sidebar.

load more comments (1 replies)

[-] BluePower@sh.itjust.works 2 points 3 months ago

I would suggest a small countdown to the end of the event on the place where the pixels count and coordinates belong (circled below), only displaying during the event.