<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p class="moz-cite-prefix">Happy 5th AMS Celebration Day dear
Chapter Admins,</p>
<p class="moz-cite-prefix">same procedure as every year (OK, one day
late - but not too late!).</p>
<div class="moz-cite-prefix">Klaus Birkenbihl schrieb am 15.03.25 um
13:01:<br>
</div>
<blockquote type="cite"
cite="mid:09937193-37dc-4399-a787-ce944cc3d3fd@isoc.de">
<pre wrap="" class="moz-quote-pre">...
Once upon a time ... In order to support its work for an open, accessible, and
strong Internet; in order to protect it against monopolistic attacks from big
companies; in order to foster innovation, creativity and unexpected use, ISOC
has set-up an Advanced Membership administration System (AMS). It was
implemented carefully following open standards (as from IETF, W3C ...),
providing excellent usability, privacy, and accessibility. A carefully chosen
Internet-canny and innovative medium size company was mandated with the
implementation. An internal group of ISOC experts carefully supervised this
work ... and they lived happily ever after.
OK, just kidding.--
...</pre>
</blockquote>
<p><font face="Helvetica, Arial, sans-serif">Admitted: the heat is
off. <span class="HwtZe" lang="en"><span class="jCAhz ChMk0b"><span
class="ryNqvb">There are other problems that need to be
addressed.</span></span>
<span class="jCAhz ChMk0b"><span class="ryNqvb">So many</span></span></span></font><font
face="Helvetica, Arial, sans-serif"><span class="HwtZe"
lang="en"><span class="jCAhz ChMk0b"><span class="ryNqvb"><br>
people have come to terms with AMS and its inconsistencies
and errors.</span></span></span> Anyhow<br>
</font><font face="Helvetica, Arial, sans-serif">some indomitable
Gauls still hold out against it. Here are the news:</font></p>
<p><font face="Helvetica, Arial, sans-serif">First some minor good
news - I omit announcements since nearly all announcements<br>
of the </font><font face="Helvetica, Arial, sans-serif">past
were never fulfilled. There are 2 advancements (credits go to
Rubén Martín ,<br>
[<span style="white-space: pre-wrap">Community </span></font><font
face="Helvetica, Arial, sans-serif"><span
style="white-space: pre-wrap">Engagement Manager Europe] who pushed for them). (Btw. in the following
"register" means "register with AMS as ISOC Chapter member"):</span></font>
<br>
</p>
<ol>
<li><font face="Helvetica, Arial, sans-serif">Chapter
notifications: Now fully implemented, alerting chapters when a
member<br>
applies or leaves. There are localized email templates members
get and ISOC‑ID<br>
is in new‑application emails.</font></li>
<li><font face="Helvetica, Arial, sans-serif">There is a simple t<span
style="white-space: pre-wrap">wo‑step link (log in → submit) for ISOC-Members to apply for
</span>a Chapters membership. Also intended to make it less difficult to
register Chapter<br>
members not yet registered with AMS.<br>
</font></li>
</ol>
<p><font face="Helvetica, Arial, sans-serif">Beside of this I
released isoc-ams last year. (Version 1.0 dates from last
Friday). Its a<br>
Python based command line app - also providing an API as base
for tailored applications.<br>
It allows e.g. for the following:</font></p>
<p><font face="Helvetica, Arial, sans-serif"> > </font><font
face="Courier New, Courier, monospace">isoc_ams.py -i -u </font><font
face="Helvetica, Arial, sans-serif"><i>isoc-user-id</i></font><font
face="Courier New, Courier, monospace"> -p </font><font
face="Helvetica, Arial, sans-serif"><i>isoc-password </i></font><font
face="Courier New, Courier, monospace">< commands.txt</font></p>
<p><font face="Helvetica, Arial, sans-serif">with "</font><font
face="Courier New, Courier, monospace">commands.tx</font><font
face="Helvetica, Arial, sans-serif">t" holding lines like:</font></p>
<blockquote>
<p><font face="Courier New, Courier, monospace">deny 23232 22556
12363</font><font face="Helvetica, Arial, sans-serif"> # to
deny pending applications with respective </font><font
face="Helvetica, Arial, sans-serif">ISOC‑IDs</font><br>
<font face="Courier New, Courier, monospace">approve 253232
242556 132363</font><font face="Helvetica, Arial, sans-serif">
# to approve applications with respective </font><font
face="Helvetica, Arial, sans-serif">ISOC‑IDs</font><br>
<font face="Courier New, Courier, monospace">delete 253277</font><font
face="Helvetica, Arial, sans-serif"> # to de-register </font><font
face="Helvetica, Arial, sans-serif">ISOC‑ID</font><font
face="Helvetica, Arial, sans-serif">s from AMS.</font></p>
</blockquote>
<p>More on <a class="moz-txt-link-freetext" href="https://github.com/birkenbihl/isoc-ams">https://github.com/birkenbihl/isoc-ams</a>.</p>
<p>I use the isoc-ams API (since Jul 25) in a job (running as part
of my daily backup job)<br>
to automatically:</p>
<ol>
<li>invite new pending applicants<code></code></li>
<li>deny pending applications that didn't respond (timeout = 30
days)</li>
<li>approve pending applicants that successfully joined the
Chapter</li>
<li>de-register members from AMS that e.g. left the Chapter</li>
<li>receive a list of Chapter members not registered with AMS</li>
</ol>
<p>Happy AMSing</p>
<p>Klaus</p>
<pre class="moz-signature" cols="0">--
Klaus Birkenbihl
Internet Society German Chapter (ISOC.DE) e.V.
c/o ict-Media GmbH
<a class="moz-txt-link-freetext" href="https://www.isoc.de">https://www.isoc.de</a></pre>
<p class="moz-cite-prefix"><br>
</p>
<p><br>
</p>
<ol>
</ol>
</body>
</html>