Dreamwidth Suggestions

Description:
The existing post-by-email optional/extra/advanced features are documented:

http://www.dreamwidth.org/manage/emailpost?mode=help&type=optional
http://www.dreamwidth.org/manage/emailpost?mode=help&type=headers

Should the alt text take the form of another "post" command at the top, like one of these two:

post-alt: image's alt text goes here
post-image: image's alt text goes here

Should it be done another way? If so, how?

Description:
There's a paid feature where you can add /?date=2012-12-12 (for example) to the end of your reading page, and you'll see your reading page as it would have been on that date (had your circle been in the state then that it is now).

This works on your own reading page, but apparently not the reading pages of paid communities. Was this an oversight or a deliberate choice?


Why this would be useful:

Communities' reading pages are usually not particularly useful on a regular basis -- they collect the public entries of the community's members. If you want to read someone regularly, usually you add them to your own reading page or put them in your RSS reader or bookmark them or whatever.

I'm trying to catch up on Alternity this weekend. (Alternity is a journal-based roleplaying game. Most of the character journals are members of the community, and only character journals are members of the community.) It would be really convenient if I could just find the start date and progress through the archives day by day (possibly after throwing a paid account at the community).


Limitations:

It might be a good idea to not have the whole site suddenly hitting a community's reading page for whatever reason.

* Limiting who can do this to community admins would parallel the individual feature, but wouldn't necessarily be useful to the community.
* Limiting who can do this to community members would make sense in general, but wouldn't work for this specific application.
* Limiting who can do this to community subscribers would discourage the casual bot from cruising through and hitting the site with all the hammers.

I believe limiting the timespan available to the reading page was originally done (on LJ with the friends page) because of the load it takes to retrieve entries from all the different journals on all their disparate clusters, particularly when the entries are not recent, and therefore haven't been fetched recently, and therefore are not already cached.

An individual's use of the feature is already calculated into the cost of a paid account. If this were available to anyone who wanted to use it with a paid community, there would be no data on how much it would get pounded if it is used. On the other hand, there are paid communities that would never use it. Another way of paying for the load, if the community's own paid account is not sufficient, would be to require that both the community and the reader have paid accounts in order to fetch this.


Would this be a privacy problem?

It would only contain public information, and community reading pages are already available for two weeks from the current date, for all communities (regardless of their membership restrictions).

It would present the public entries it in a context that would take a bit of doing to get otherwise. Someone could get the same information by adding all the members to their own reading list (in a custom reading group), and getting a paid account, or they could visit all the members' journals from that day.