Permanent one working with a different model. Like 1 pixel per hour with a fixed drop rate (instead of this “stay and place as fast as you can for best performance”), and you can hold like 36 pixels. So basically you drop a few dozen pixels daily then you’re done. After every 100,000 clicks, you move the window 100 pixels to the right, making the leftmost 100 pixels locked forever creating a slowly growing endless immutable banner.
You could mitigate that by adding a limited, rotating color pallet. every time pixels are locked two colors are taken away and two different colors are added. You would always be able to see beforehand when certain colors would be made available, enabling a new level of planing. It also forces creative solutions in defending your art
That idea would even work standalone without the immutable thing
36 pixels at once would be fine early on when there’s plenty of room and everyone’s doing their own thing, but once it starts to fill up and people start interacting more, other people need time to respond to each pixel.
Maybe have the number go down over time, or say every time you overwrite an existing pixel it reduces your total stack capacity.
Well my point with 36 pixels is that it would let people use the site in a healthy way (daily) but also allow decent velocity of creation for a slow-developing canvas. The details could be tweaked I just figured “once a day sounds right, no pressure then” and "150 users doing 24 pixels per day would fill a 10th of the canvas (the scroll-right number, 100,000 pixels) in a month. Obviously the numbers could be tweaked depending on activity of the community and the dimensions of the editable canvas, I would just say targeting a good experience for “daily use” is healthy for a permanent site. Because I know my use of this site this weekend was anything but healthy.
Maybe put the cap at 16 (assuming hourly pixel generation), so you can hit the site twice daily plus a little wiggle room while still reaching peak output. Too often the canvas felt like being the little Dutch boy with the finger in the dike.
Imho the approach of punishing overwriting with slower regen is the right move - every overwrite pixel you place should add a 1 pixel delay to your pixel generation, so vandalizing (and repairing) takes twice as long as creating.
Permanent one working with a different model. Like 1 pixel per hour with a fixed drop rate (instead of this “stay and place as fast as you can for best performance”), and you can hold like 36 pixels. So basically you drop a few dozen pixels daily then you’re done. After every 100,000 clicks, you move the window 100 pixels to the right, making the leftmost 100 pixels locked forever creating a slowly growing endless immutable banner.
Infinite German flag? Sounds like an infinite German flag to me
You could mitigate that by adding a limited, rotating color pallet. every time pixels are locked two colors are taken away and two different colors are added. You would always be able to see beforehand when certain colors would be made available, enabling a new level of planing. It also forces creative solutions in defending your art
That idea would even work standalone without the immutable thing
Call it Tapestry
Infinitapestry.
36 pixels at once would be fine early on when there’s plenty of room and everyone’s doing their own thing, but once it starts to fill up and people start interacting more, other people need time to respond to each pixel.
Maybe have the number go down over time, or say every time you overwrite an existing pixel it reduces your total stack capacity.
Well my point with 36 pixels is that it would let people use the site in a healthy way (daily) but also allow decent velocity of creation for a slow-developing canvas. The details could be tweaked I just figured “once a day sounds right, no pressure then” and "150 users doing 24 pixels per day would fill a 10th of the canvas (the scroll-right number, 100,000 pixels) in a month. Obviously the numbers could be tweaked depending on activity of the community and the dimensions of the editable canvas, I would just say targeting a good experience for “daily use” is healthy for a permanent site. Because I know my use of this site this weekend was anything but healthy.
Maybe put the cap at 16 (assuming hourly pixel generation), so you can hit the site twice daily plus a little wiggle room while still reaching peak output. Too often the canvas felt like being the little Dutch boy with the finger in the dike.
Imho the approach of punishing overwriting with slower regen is the right move - every overwrite pixel you place should add a 1 pixel delay to your pixel generation, so vandalizing (and repairing) takes twice as long as creating.