72 lines
4.7 KiB
XML
72 lines
4.7 KiB
XML
|
<appendix id="ljp.csp.faq">
|
||
|
|
<title>Frequently Asked Questions</title>
|
||
|
|
<qandaset>
|
||
|
|
<qandaentry id="ljp.csp.faq.urlitemid">
|
||
|
|
<question><simpara>How do I calculate the protocol itemid to get the <quote>URL</quote> itemid?</simpara></question>
|
||
|
|
<answer><simpara>For protocol methods that return an <varname>itemid</varname>, there is also another variable returned called <varname>anum</varname>.
|
||
|
|
To calculate the public URL itemid, use the following formula: <inlineequation>(itemid * 256) + anum</inlineequation>.
|
||
|
|
</simpara></answer>
|
||
|
|
</qandaentry>
|
||
|
|
<qandaentry id="ljp.csp.faq.datalimits">
|
||
|
|
<question><simpara>What are the limitations on post and user information data?</simpara></question>
|
||
|
|
<answer><para>To help calculate portions of your client, here are the upper limits of client affected data:
|
||
|
|
<itemizedlist>
|
||
|
|
<listitem><simpara>Posts: 65,535 bytes</simpara></listitem>
|
||
|
|
<listitem><simpara>Entry Properties (Currents): 255 bytes or 100 characters</simpara></listitem>
|
||
|
|
<listitem><simpara>Entry Subjects: 255 bytes or 100 characters</simpara></listitem>
|
||
|
|
<listitem><simpara>User Picture Keywords: 40 characters</simpara></listitem>
|
||
|
|
<listitem><simpara>Usernames: 15 characters</simpara></listitem>
|
||
|
|
<listitem><simpara>Name: 50 characters</simpara></listitem>
|
||
|
|
<listitem><simpara>Webpage URL: 255 bytes</simpara></listitem>
|
||
|
|
<listitem><simpara>Webpage Name: 255 bytes</simpara></listitem>
|
||
|
|
</itemizedlist>
|
||
|
|
</para></answer>
|
||
|
|
</qandaentry>
|
||
|
|
<qandaentry id="ljp.csp.faq.downloadpage">
|
||
|
|
<question><simpara>I just wrote a client for LiveJournal. How do I go about getting it on the Download page?</simpara></question>
|
||
|
|
<answer>
|
||
|
|
<simpara>The Downloads page currently requires manual updates, which happen infrequently.
|
||
|
|
Due to the large userbase which uses clients offered up via the Downloads page, we
|
||
|
|
prefer to only add well-established clients to the page at this point.
|
||
|
|
</simpara>
|
||
|
|
<simpara>
|
||
|
|
All too often, someone will code a client and then abandon it after a certain amount of time.
|
||
|
|
If you feel that you are willing and able to commit to maintaining and providing support for
|
||
|
|
a client, then by all means produce one and announce it on
|
||
|
|
<ulink url="http://www.livejournal.com/community/lj_clients/info">lj_clients</ulink>. It is
|
||
|
|
recommended that you create a community for the users of your client, so you can announce new
|
||
|
|
versions and provide a forum for troubleshooting and user support. Once your client has
|
||
|
|
matured, it will likely be included on the Downloads page. If your program has reached a
|
||
|
|
point where you feel it should be included in the page and it hasn't been yet, feel free to
|
||
|
|
drop a post to <ulink url="http://www.livejournal.com/community/lj_clients/info">lj_clients</ulink>
|
||
|
|
asking why.
|
||
|
|
</simpara>
|
||
|
|
<itemizedlist>
|
||
|
|
<title>Client Listing Guidelines for the <ulink url="http://www.livejournal.com/download/">Download a Client</ulink> page</title>
|
||
|
|
<listitem><simpara>As a minimum, clients MUST support the basic features of LiveJournal,
|
||
|
|
such as logging in, posting new entries, editing old entries, history views, etc.</simpara></listitem>
|
||
|
|
<listitem><simpara>Client MUST be mature and well-established before being listed. Having minor bugs is ok, but
|
||
|
|
we don't want to link to clients that have the potential to mess up an account.</simpara></listitem>
|
||
|
|
<listitem><simpara>Client MUST be free to use. You're welcome to create and maintain a
|
||
|
|
client that isn't free/open, we just don't want to provide free advertising for such a client.</simpara></listitem>
|
||
|
|
<listitem><simpara>Client MUST be originally written for LiveJournal. We support the Blogger and Atom APIs, and
|
||
|
|
we encourage interoperational clients, but we don't want to get in the habit of listing clients for
|
||
|
|
competitor services.</simpara></listitem>
|
||
|
|
</itemizedlist>
|
||
|
|
</answer>
|
||
|
|
</qandaentry>
|
||
|
|
<qandaentry id="ljp.csp.faq.userinfopage">
|
||
|
|
<question><simpara>Why doesn't my client show up on my user info page?</simpara></question>
|
||
|
|
<answer><simpara>Recently client logging was disabled because its current implementation was consuming
|
||
|
|
far too many database resources. It will likely reappear in the future, once a more efficient design
|
||
|
|
is coded and tested.
|
||
|
|
</simpara></answer>
|
||
|
|
</qandaentry>
|
||
|
|
</qandaset>
|
||
|
|
</appendix>
|
||
|
|
<!--
|
||
|
|
Local Variables:
|
||
|
|
mode:sgml
|
||
|
|
sgml-parent-document: ("index.xml" "part" "appendix")
|
||
|
|
End:
|
||
|
|
-->
|