71–76 of 76 posts
* Picking some RFCs and then writing a client/server is fun as a coding exercise.
* I had a go at implementing POP3 and HTTP years ago in a MUD / LPC, but HTTP has been done to death now.
* Documentation is also really really good and I like the self-describing code, but have you thought about adding any unit tests i.e. for the algorithms?
Earlier quoted context omitted.
Check your monitor gamma and white level using something like this: http://www.lagom.nl/lcd-test/gamma_calibration.php You might be crushing whites, or just have incorrect gamma.
Thanks for the link! I've seen the site before but never thought of testing my screen when I got my new laptop. It's very difficult to tell, though. The gamma varies between 1.9 and 2.3 (roughly) depending on the angle at which I look at my screen. Every time I sit this will be different. Opening the article again, it also depends where I look: when tilting my laptop back a bit, the text appears darker (even black if…
If you have something like the Nvidia Linux control panel for adjusting colors, lowering the white level and raising the black level can help compensate a bit. The open source Media Player Classic (or MPC-HC maybe) player also has a nice shader to correct for the vertical variation, but I don't know of any way to apply it to the whole OS.
Earlier quoted context omitted.
> takes it apart and puts it back together to gain the kind of knowledge you will never find in a book/blog post. Interestingly, the author still worked a lot with the docs (RFCs), not just with the software itself. I believe this is important for any hands-on activity. Even though the documentation isn't your starting point, and may be too cumbersome and badly structured, sooner or later you should go back to them,…
I thought it was fairly discouraging that the docs weren't sufficient to get the author up and running with ssh; a lot of seemingly undocumented gotchas popped up.
Earlier quoted context omitted.
It's very odd to have to depend on a browser feature that is basically for accessibility in order to read a website because the colour choices are bad.
It's weird to me that people want millions of random people controlling how content is visually presented; aka, wish the web would die already.
It's interesting that "The transport protocol doesn’t cover who sends their banner first". It'd be good if I could configure my server to keep quiet until the client identifies itself as an SSH client. I run it on an unusual port and it gets scanned frequently. sshguard helps but I'd prefer it wasn't announcing to any client that it is an ssh server.
After installation, simply type:
$ sudo apt-get -y install sshguard
And then edit the whitelist to include your local IP if you want;
$ sudo vim /etc/sshguard/whitelist $ sudo service sshguard restart
Nice. What first revealed me the hidden complexity of SSH was typing this during a live SSH session: ~? Which show you the SSH supported escape sequences.