I'm glad this is my first time using openboard so that I don't need this typeof keyboard nostalgia, because, and I don't want to hurt your feelings, BUT, boy, that theme is ugly.
Well. He's old enough to know what those rockets are. Also: That thing was full of rockets on the first day he shared the address and I totally knew it was gonna happen ;)
I'm more afraid of worse things strangers would be able to post directly to his wall.
At least it was a fun father-son-project.
I wrote the server part, he the client part.
First there is the web frontend (sending click requests to a script that saves the clicked pixel in a database, heartbeating to a script to refresh the "image")
You can emulate the rgb output:
Then there is the 64x64 RGB matrix and a raspy connected to it. It is quite hollow on it's back, giving the raspy some place to hide:
The code on the raspy connects to the server and refreshes it's image, if a change happened.
I also "hid" the matrix inside a canvas frame, to help diffusing the single RGBs a bit:
It wouldn't be such a bad idea if there weren't IDEs that would help you review your code more easily.
Think of a text document you would scan for typos. Sure it would help you to print it out and read it on paper. But finding them with words auto correction is much faster.
This kind of auto correction is also present in IDEs (integrated development environment / the program you use to do the actually coding). You can also jump from one part of your code to another part for a quick lookup or analyze it with its help.
So printing it out not only doesn't let you editing it it also slows down reviewing / debugging / refactoring it.
Additional to what others have said: The "salted" part is very relevant for storing.
There aren't soooo many different hashing algorithms people use. So, let's simplify the hashing again with the crossfoot example.
Let's say, 60% of websites use this one algorithm (crossfoot) for storing your password, and someone steals the password "hashes" (and the login / email). I could ran a program that creates me a list of all possible crossfoots for all numbers for 1 to 100000.
This would give me an easy lookup table for finding the "real" number behind those hashes.
(Those tables exists. Look up "rainbow tables")
Buuuut what if I use a little bit of salt (and pepper pepper pepper) before doing my hashing / crossfooting?
Let's use the pw "69" again and use a salt with a random number "420" and add them all together:
6 + 9 + 420 = 435
This hash wouldn't be in my previous mentioned lookup table.
Use different salts for every user and at least the lookup problem isn't such a big problem anymore.
I'm glad this is my first time using openboard so that I don't need this typeof keyboard nostalgia, because, and I don't want to hurt your feelings, BUT, boy, that theme is ugly.