107

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

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

124 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

[-] 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.

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

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

It could cause chaos if done poorly, indeed. But I think that there are ways to minimise this chaos.

One of them would be that reverted pixels are marked as "reverted by the admins", and that appears in an overlay similar to the heatmap.

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

Like in cryptography? I like this idea. Perhaps it could be used when there's a reasonable possibility that two accounts are from the same user; for example same IP, or same username but different instance, etc.

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

The only problem with proof of work (pow) is that it won't perform the same across devices and will kill battery life. The difficulty of the proof would need to be calculated on page load which could open it up to spoofing a different device.