In theory that's a good resource, Jimin, except that it's wrong. :) The "server name" could be anything, and has very little to do with the domain name. It is true that you can usually log in to a server (a remote computer) by giving whatever program you're logging in with the domain name, but that doesn't mean that the server itself has the same name as the website. That page is also very, very wrong in calling the the top-level domain (.org etc.) the "domain name." It's important to note that that page was almost certainly written by a librarian, not a tech professional. (Of course, I'm an English PhD, not a tech professional myself, but still.) And when I looked at the source code, I could tell that it was hand-coded in HTML, which indicates to me that it's probably many years old.
Wish there were a "dislike" button. :)
Which is better, OSS or Proprietary Software? This article poses both sides of the arguments, mainly that OSS is lauded for it's "community" support, while Proprietary Software is backed by professional, tried and true support. The main conclusions were that OSS and Proprietary Software essentially match in content quality until the codes become longer. In that case, Proprietary Software comes out on top.
Don't forget to add a comment that describes what's at the link, Milan. I'll give you credit this time, but not next time.
That is clearly an *ancient* web page. If you do View Source on it, too, you can tell (at least I can) that it was hand-coded in HTML rather than generated by a CMS. And all the tags are written in capital letters, . No one does that anymore.
Not a bad site at all, Emily -- thanks for finding it. I notice too that under "Learning Tools" there are various "Cheat Sheets" of things like a list of all two-letter TLD country codes. Could be useful.
Here's a tremendously engaging video of Clay Shirky giving the talk I just linked to about where people find the time to edit Wikipedia -- he thinks they probably stop watching TV. Which do you think is more productive?
Another great quote from this piece:
"So if you take Wikipedia as a kind of unit, all of Wikipedia, the whole project--every page, every edit, every talk page, every line of code, in every language that Wikipedia exists in--that represents something like the cumulation of 100 million hours of human thought. I worked this out with Martin Wattenberg at IBM; it's a back-of-the-envelope calculation, but it's the right order of magnitude, about 100 million hours of thought. And television watching? Two hundred billion hours, in the U.S. alone, every year. Put another way, now that we have a unit, that's 2,000 Wikipedia projects a year spent watching television."
Hmm, interesting. The service she describes where libraries sell books is fairly rare, still, although it's made possible by a thing called an Espresso Book Machine that prints copied of ebooks: http://www.ondemandbooks.com/
I hate when I can't figure out the date of things. I even looked at the source code to try to find out when that video was recorded, but I couldn't. I did discover that the girl in the video (I love her sweater!) is one of the co-hosts of another How Stuff Works podcast called "Stuff You Missed in History Class" at http://shows.howstuffworks.com/stuff-you-missed-in-history-class-podcast.htm -- that might be useful! Certainly relevant. :) Their latest episode is about an 18th-century "Vampire Panic" in New England. Sign me up.