LiveJournal Financial Status
Short, concise description of the idea
A page describing the current financial status of LiveJournal.
Full description of the idea
Since LiveJournal is open source and community based, and many of its members (especially the paid ones) think of it almost as a family, I know I - and probably others - are interested in the financial status of LiveJournal. The paid members have placed part of their earned income into LiveJournal to make it thrive. We're interested in knowing where that money goes, besides hearing "to make LiveJournal better!" (which, don't get me wrong, is a good thing!)
Create a (perhaps dynamic) page on livejournal.com that details for LJ members (or at least paid members) the current financial status of LiveJournal. How much money does LJ have? What has past money been spent on? What are future planned purchases? How much money goes to pay staff? Who gets paid by LiveJournal? What is the weekly/monthly/yearly income/expense of running LiveJournal.
An ordered list of benefits
- An increased awareness of how much (or little) money LiveJournal has.
- If users notice LiveJournal has very little money, it could be more incentive to purchase a paid account.
- An increased knowledge of how appropriately (or inappropriately) LiveJournal is spending it's money.
- If users see that LiveJournal is spending it's money wisely, they may be more likely to purchase paid accounts (now having little fear that their money would be used by some kid named bradfitz to purchase tons of cool toys for himself - no offense Brad, I don't believe you're doing that).
An ordered list of problems/issues involved
- If users notice LiveJournal has a lot of money, it could be less incentive to purchase a paid account.
- LiveJournal may not want its financial status known (for privacy and/or security reasons?)
- It may not be worth the time/effort to create, update or maintain such a page.
An organized list, or a few short paragraphs detailing suggestions for implementation
I'm not sure if this information is store in the database somewhere. If it is, then it would be as "simple" as creating some sort of BML page to display it to the user. If its not in the database, a static version would need to be created. Alternatively, it could be added to the database to make dynamic viewing possible. The method of implementation would be up to the staff.