Canvas is available for Lemmy!
This is similar to reddit’s /r/place. Each user gets to place a pixel on a canvas. The pixels are refreshed every 30 seconds.
The website with the canvas is: https://canvas.toast.ooo/
To log-in, you simply provide your instance’s name and your username, and you get a code to log-in.
I have made a template for making an XNO flag. You can reach it by clicking here.
In the settings there is a button that allows you to toggle the tample on/off. You can use that button to make sure that you are placing the pixel in an unoccupied spot.
If you shift + click on a pixel, you can see who placed that pixel, and you can also see their faction. I think the faction is a way for users to label themselves as part of a team, but it doesn’t have any special additional mechanic associated with it.
very cool! how long does this last? it’s charging up an idea i’ve had for a while though, basically a permanent nano canvas where each pixel could be claimed by an address and balance. and then if you take someone’s pixel, there could be a bidding war or something like that. you get your nano back + some extra and then they claim your pixel for themselves. so i guess it would be some type of free market canvas? lots of possibilities there.
basically evolve the OG version https://en.wikipedia.org/wiki/The_Million_Dollar_Homepage
One scary thing about the nano-based canvas is that maybe at some point the person hosting that doesn’t want to host it anymore. But every person who owns a pixel paid for it… They didn’t pay the person hosting the site, so it is not fair to ask that the site hoster pays them back. What happens then?
What I’m thinking is that it might be possible to do this but using NFTs. So, let’s say that you have a 100 x 100 canvas, and 10,000 NFTs, each one corresponding to a pixel. So the NFTs map to the list of pixels Canvas(0,0), Canvas(1,0), Canvas(2,0)… and the owner of the NFT gets to pick the color. Since these NFTs live on the blockchain, there is no single person ‘hosting’ the canvas. Anyone can set up an instance and display the canvas by pulling the information from the NFTs.
I haven’t studied deeply the NFTs, so I don’t know how easy it is to associate a label with the color to them.
I guess we’re juggling multiple concepts atm… could you even skirt the whole payment thing with just rep changes instead? I can’t calculate exactly how that would play out rn, but imagine using 1 seed, generating a bunch of accounts under that, publicize those & associating them to the pixels, and you could monitor the largest rep for each of those accounts? Seems to work for website duplication/experimentation if the code is open-source, you could change the accounts at will. This kind of bleeds into another concept that I think nano is really suited for, which is I would call an interactive network monitor? What I find interesting about this concept is it actually doesn’t require any extra input at all, people could use nano as is for regular economic activity, and you could have these metalayers that are actually just adding/extracting more value 2 those, essentially it’s seeding another layer with the previous layer’s entropy? I think we’re just scratching the surface here…
> you could monitor the largest rep for each of those accounts
I got lost in this part of the argument. What do you mean? The “rep” as in an account’s representative? The account representative is decided by the account owner, and there is only one rep per account. I think I’m misunderstanding what you mean.
delegator, sorry
Aaaah thank you for the clarification. Now I follow the logic!
The RGB representation color of the pixel can be passed as the last nine digits of the amount delegated. The 8-bit RGB value is expressed as (R,G,B) where R, G, and B are numbers between 0 and 255. So if I want to set a pure yellow pixel (255,0,255) I can delegate “1.000000000000000000000255000255” to the account that controls that pixel.
There might be a more user-friendly format to achieve this, but this is the most straight-forward implementation I can think of. A choice can be made to have a more specific format to reject un-formatted amounts and this way prevent accidental black pixels being placed.
As to the “interactive network monitor”, can you expand on that? It is not obvious to me what you mean with that. Would this canvas be an example of such type of monitoring?
with so many digits i think using the smallest 9 raw values is a fine idea, especially for robust first implementations. right… there’s a lot of black space if you don’t restrict the digits, but i actually am not sure if i’m for or against that. black takes less power usually, right? lol
it could be. especially using your suggested implementation, there’s accounts that exist already with delegated raw that will fall within the format, so if you designated that rep as the “place rep” you’d already have begun a place seeded with some beginning pixels.
hm…is there enough space for position coordinates as well?
if it’s something like nyano.place 1 nyano = Ӿ0.000001
1.000001000000000000000255000255
looks like there’s tons of leeway still there.
also i wonder how much this format biases colors, i’m guessing it won’t be too significant esp. at this point
re: interactive network monitor https://music.nanos.cc/ https://github.com/Joohansson/nanomusic this is the best thing that comes to mind that already exists
my imagination is a little more complex and unfinished, but essentially it’s just reinterpreting the meaning of the functions and data that already exist in nano and transforming them into another form. example: reconstruct/interpret the blockchain data as a virtual city. i think doing this actually helps you concretize understanding about network flows, and at some point surely begins to affect them as well.
Oh, right! Yes, there is a lot of space for that. It would be possible to handle this with a single node.
So, there could be a “Canvas” Representative node
The amount delegated to it should follow a specific format, including a canvas-specific code, the 3-digit X coordinate, 3-digit Y coordinate, and the RGB code. There is easily more than enough space with the 30 digits we have to work with.
The color of each pixel is set by the highest amount delegated that claims a pixel.
The special code would make it so that there is no biasing, and that accidental pixel placements are very unlikely.
Oh wow, I had never heard of that!! It is very cool. Do you mind if I will create a post to share that to !community_projects@nano.garden, unless you would like to make that post yourself _