This domain isn't particularly about web content, but this is a webserver since
everyone seems to expect one. There is more to the internet than web, even
though most seem to have forgotten.
That said, here is some information via web that can help people do interesting things with their domain, whether it be their home, a VPS, or other solution.
- Remote DVR. In this case, you'll generally actually have a web server.
I won't bother to detail this further than saying MythTV in combination with MythWeb is a great way to provide functionality that even subscription fee based DVRs are only recently starting to provide. I won't detail this because a web search will uncover plenty of sufficient documentation.
- Your own XMPP gateway. Certain messaging services do not work well with multiple concurrent logins from different places and/or nag you when you try. This becomes increasingly frustrating with the proliferation of mobile phones that will logout/in incessantly in a spotty coverage area. I use google talk primarily (to benefit from them caching my not-particularly secret information) and now bridge all non-google talk messages through one login at my house. I use Prosodey Jabber server and Spectrum component together to acheive this. This comes with some requirements and issues:
- You *must* have nested domain capability. I.e. .im.domain.name. You *must* have a dot after protocol and your jabber server *must* have im.domain.name resolvable/served. Each protocol must be a valid DNS subdomain. I don't know why and it makes things more complicated, but that's the simple reality.
- Everyone using your gateway must trust you enough to keep their IM passwords. This is the primary reason I do not use an established gateway. This sort of gateway *will* remember your credentials in a way the administrator to retrieve.
- If you get odd messages about 'will reconnect' with no success ever *make sure* the password is correct. The prosody+spectrum combo does not sanely report up authentication errors.
- Straightforward remote access. This should be obvious to most. SSH is the best starting point and everything else should go over that. ssh -L 5900::5901 to your home will allow you to vnc in to a vnc server using ssh to protect and authenticate on top of relatively weak vnc mechanisms. RDP may offer more secure access, but I always port forward RDP over ssh as well, as it can't hurt security but it may help immensely.
- Mail server. Now that many web mail providers give convenient imap access, conveniently large quotas, and better backup than you'll likely implement, this is less and less interesting. However, you may still want to set up an email server if you want to forward mail to yourself which means your home gets large attachments before you even go to read it and you can send large attachments without waiting for it to upload over your link. You may also dislike the mail providers web interface and set up something like squirrelmail or roundcube depending on your tastes. Note this can either frontend your imap or *their* imap services. Some recommended software includes dovecot (imap), postfix, roundcube (shiny web interface), squirrelmail (more simplistic html, but more powerful).