Sorry for being pedantic, but I think it is useful when considered in light of the fact that most folks log on a specific interval and then report on it. IOW if you log hourly you could upload hourly. Plus for some reason some folks seem to be averse to keeping a machine on 24/7 and the periodic upload is useful.
Oh, I don't object. The problem is that a completely-accurate description of the situation takes (by my estimate):
About 2.5 printed pages if you only talk about Davis capabilities;
Another 4 pages if you also include non-Davis software - including possible interactions with WeatherLinkIP;
Another page or so if you include non-Davis IP hardware and associated loggers;
And several pages if the work on interface solutions that don't use a Davis logger is included.
And it's rather unlikely that a "beginner" knows what questions to ask, or even exactly what he/she wants to accomplish. Much less what he/she
might want to accomplish in the future (which can be affected by today's choices).
So, I tried to construct a "minimalist" description of the essential principles, knowing that it's incomplete, but perhaps useful to begin a discussion. A more simplified version of item 3 that may be satisfactory:
3. If you want data to be uploaded 24/7 to a site that you own, you must have a computer running 24/7, as well as one of the three available loggers.
Footnote: I think I disagree with your "hourly" example. I think that most folks who upload to their own weather site, are interested in having their thousands of friends and neighbors be able to see the
absolutely current weather at their house. As witness, I offer the "rapid fire" capability - technically not someone's personal weather site, but it sure looks like it, and the "desire" is similar.