<commit_before><h1>Aalto Social Interface</h1>
<p>
  Aalto Social Interface, or <strong>ASI</strong>, is a RESTful platform for social media applications.
  Using ASI, anyone can create their own application that is available to the OtaSizzle user base and social network.
  An ASI application will not necessarily even need its own database.
</p>

<h2>Getting Started</h2>
<p>Read the <a href="http://sourceforge.net/apps/mediawiki/sizzlelab/index.php?title=Getting_Started_Tutorial">Getting Started Tutorial</a> in <a href="http://sourceforge.net/apps/mediawiki/sizzlelab/index.php?">SizzleLab wiki</a>.</p>
<p>Or try the <a href="/test">interactive tester</a> if you already have an application account.</p>
<p>Instructions in a nutshell are:</p>
<ul>
  <li><tt>POST /session</tt> to create a new session.</li>
  <li><tt>GET</tt> resources to view them, create new ones with <tt>POST</tt> and update them in place with <tt>PUT</tt>.
    <tt>DELETE</tt> is also supported.</li>
  <li>If you're unable to <tt>PUT</tt> or <tt>DELETE</tt>, use <tt>POST</tt> with the actual method in the magic field
    <tt>_method</tt>.</li>
  <li><tt>DELETE /session</tt> when finished.</li>
</ul>

<p>All the calls to ASI resources can (and should) be made with an additional <code>event_id</code> parameter. This parameter is intended for the research log to be a semantic identifier of what the user was actually doing when this request was made. So it could be something like <code>"Kassi::ShowItemsListing::2009-07-30_14:17:23::02313"</code> but the message format is not restricted to anything. This identifier should persist for all the ASI-requests for the same action, for example when the user loads a single page in a client application, but a new one must be made for the next action. The parameter's format should be somewhat consistent between calls.</p>

<h2>The ASI resources description</h2>
<p>The following image contains a short overview of the ASI resources. The image is meant for obtaining an overall understanding of the system. A more throughout description can be found from the API reference.</p>
<commit_msg>Changed links on the ASI front page to point to the GitHub wiki<commit_after><h1>Aalto Social Interface</h1>
<p>
  Aalto Social Interface, or <strong>ASI</strong>, is a RESTful platform for social media applications.
  Using ASI, anyone can create their own application that is available to the OtaSizzle user base and social network.
  An ASI application will not necessarily even need its own database.
</p>

<h2>Getting Started</h2>
<p>Read the tutorial <a href="https://github.com/sizzlelab/asi/wiki/Tutorial:-Create-new-services-using-ASI">Create new services using ASI</a> in <a href="https://github.com/sizzlelab/asi/wiki">SizzleLab's ASI wiki</a>.</p>
<p>Or try the <a href="/test">interactive tester</a> if you already have an application account.</p>
<p>Instructions in a nutshell are:</p>
<ul>
  <li><tt>POST /session</tt> to create a new session.</li>
  <li><tt>GET</tt> resources to view them, create new ones with <tt>POST</tt> and update them in place with <tt>PUT</tt>.
    <tt>DELETE</tt> is also supported.</li>
  <li>If you're unable to <tt>PUT</tt> or <tt>DELETE</tt>, use <tt>POST</tt> with the actual method in the magic field
    <tt>_method</tt>.</li>
  <li><tt>DELETE /session</tt> when finished.</li>
</ul>

<p>All the calls to ASI resources can (and should) be made with an additional <code>event_id</code> parameter. This parameter is intended for the research log to be a semantic identifier of what the user was actually doing when this request was made. So it could be something like <code>"Kassi::ShowItemsListing::2009-07-30_14:17:23::02313"</code> but the message format is not restricted to anything. This identifier should persist for all the ASI-requests for the same action, for example when the user loads a single page in a client application, but a new one must be made for the next action. The parameter's format should be somewhat consistent between calls.</p>

<h2>The ASI resources description</h2>
<p>The following image contains a short overview of the ASI resources. The image is meant for obtaining an overall understanding of the system. A more throughout description can be found from the API reference.</p>

{'fraction_non_alphanumeric': 0.1072429906542056, 'fraction_numerical': 0.011682242990654205, 'mean_word_length': 4.71562082777036, 'pattern_counts': {'":': 0, '<': 123, '<?xml version=': 0, '>': 123, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6628807', 'n_tokens_mistral': 1297, 'n_tokens_neox': 1241, 'n_words': 556}