<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Oops, Meant to send this directly to the list. Discussion
mailing lists *really* should be set up so that replies go to the
list, not to the sender :)</p>
<p>Jeremy, NQ0M<br>
</p>
<div class="moz-forward-container"><br>
<br>
-------- Forwarded Message --------
<table class="moz-email-headers-table" cellspacing="0"
cellpadding="0" border="0">
<tbody>
<tr>
<th valign="BASELINE" nowrap="nowrap" align="RIGHT">Subject:
</th>
<td>Re: [App_rpt-users] Politics</td>
</tr>
<tr>
<th valign="BASELINE" nowrap="nowrap" align="RIGHT">Date: </th>
<td>Sun, 16 Sep 2018 19:36:13 -0500</td>
</tr>
<tr>
<th valign="BASELINE" nowrap="nowrap" align="RIGHT">From: </th>
<td>Jeremy Utley <a class="moz-txt-link-rfc2396E" href="mailto:jerutley@gmail.com"><jerutley@gmail.com></a></td>
</tr>
<tr>
<th valign="BASELINE" nowrap="nowrap" align="RIGHT">To: </th>
<td>Tim Sawyer <a class="moz-txt-link-rfc2396E" href="mailto:tisawyer@gmail.com"><tisawyer@gmail.com></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>Unfornately, the only solution to the current problems is going
to be someone who can show they have copyright in the existing
codebase, and deep enough pockets to fund a lawsuit. Without
that, all that can be done is to bring social pressure - and
unfortunately, the biggest majority of people that use his
software don't really understand open source.</p>
<p>I myself started off with his release, but once I realized he
refused to actually release his code, I immediately started to
move things back to DIAL. My old repeater (now off-air) that
ran AllStar had to use a VPN - I was stuck behind a *Triple-NAT*
so there was absolutely no way I could get a port forwarded, and
OpenVPN allowed me to get around that. But the OpenVPN package
never started on boot properly in his installation, nor did the
SNMP daemon I used for monitoring the performance of the
system. I also had to have another "backdoor" means (a router
with VPN and SSH capability) to get into the node to start the
VPN and SNMP daemons after a power failure. DIAL of course
never had this problem, but it exhibited a different problem -
there was a slight delay in the transmitted audio, so when I
would transmit on the repeater, I would hear about a half-second
of my transmission. It wasn't annoying enough to go back, but
I'd have loved to have gotten ahold of his source code, and
compiled it under Debian to see if that solved it.</p>
<p>Honestly, if I had my own choice, we'd still be running under
CentOS - I much prefer that to Debian, but I'm OK with
Debian/Raspbian, and can't stand Arch at all. I'm honestly
tempted to try to compile against Centos, it's just not worth
the time it would take to build on ARM. My biggest concern
right now is in the fact that the underlying Asterisk code being
used is so old (it's lke 1.4 still, is it not?). But I'm sure
porting apt_rpt to newer versions isn't an easy thing - I just
don't like running end-of-life code. But I have all my setups
majorly firewalled, and usually even running behind a VPN, so
that helps to ease the worry.</p>
<p><br>
</p>
<p>Jeremy, NQ0M<br>
</p>
<div class="moz-cite-prefix">On 9/16/18 4:11 PM, Tim Sawyer wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAG3ht9vYTz7KeWomAOkjMWw_jvTeChRi3oVr-qY=_3Bp0yXiAw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div class="gmail_default" style="font-size:large"><br
clear="all">
</div>
<div class="gmail_default" style="font-size:large">There
has been a ton of inaccurate statements by the
HamVoIP principals in numerous posts, emails and
telephone calls regarding what AllStarLink is up
to. Before you read the rest of this email please
take a look at the August 16 post over on
hamVoIP.org.</div>
<div class="gmail_default" style="font-size:large"><br>
</div>
<div class="gmail_default" style="font-size:large">I
really don't want to wade into this political BS.
I should be coding not spending time on this BS.
Even so I've spent tons of time behind the scenes
attempting to get folks working together. I
hesitate to speak publicly on this but my low key
approach has not worked. So, some false statements
must be publicly corrected. I will address only
this particular post at this time. </div>
<div class="gmail_default" style="font-size:large"><br>
</div>
<div class="gmail_default" style="font-size:large">First,
"The server" is not owned by one person. The very
reason AllStarLink, Inc. was formed is to prevent
that scenario. </div>
<div class="gmail_default" style="font-size:large"><br>
</div>
<div class="gmail_default" style="font-size:large">Second,
there is not just one server. There are numerous
servers around the country run by folks that
donate their time, effort and money.</div>
<div class="gmail_default" style="font-size:large"><br>
</div>
<div class="gmail_default" style="font-size:large">Third,
HamVoIP principals continually imply that AllStar
was unofficially taken over. That's just not true.
The reigns were turned as officially as possible
given Jim's sudden death. Jim's long time friends
and co-developers of AllStar contacted current and
past AllStarLink board members and made
arrangements for what you see today. </div>
<div class="gmail_default" style="font-size:large"><br>
</div>
<div class="gmail_default" style="font-size:large">Additionally,
it's true that migration to the new servers didn't
go perfectly. But it's extreme unfair to bash
individuals who are only attempting to improve
AllStar. Ham Radio is about learning if it's about
anything. Making mistakes happens as part of the
learning process. Now we have a better system and
no one got shot as my Marine friend used to say.</div>
<div class="gmail_default" style="font-size:large"><br>
</div>
<div class="gmail_default" style="font-size:large">The
August 16 HamVoIP statements are divisive and only
serve to build up some individuals at the expense
of others. To HamVoIP principals I say enough of
that crap! If you want to build a better mouse
trap you are welcome to that. Go for it. But don't
justify yourself by speaking badly of others who
have nothing but good intentions. </div>
<div class="gmail_default" style="font-size:large"><br>
</div>
-- <br>
<div dir="ltr" class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div dir="ltr">
<div>Tim WD6AWP<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
App_rpt-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:App_rpt-users@lists.allstarlink.org" moz-do-not-send="true">App_rpt-users@lists.allstarlink.org</a>
<a class="moz-txt-link-freetext" href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users" moz-do-not-send="true">http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users</a>
To unsubscribe from this list please visit <a class="moz-txt-link-freetext" href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users" moz-do-not-send="true">http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users</a> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
</pre>
</blockquote>
</div>
</body>
</html>