Re: CoCo torrent?

RETRO Innovations via Coco <[email protected]> Tue, 2 Jun 2026 11:13:14 -0500
Newsgroups gmane.comp.hardware.tandy.coco
Message-ID <[email protected]>
This is a multi-part message in MIME format.
--===============2672483839735680106==
Content-Type: multipart/alternative;
 boundary="------------00DF2ZMTpnPuoDyQcAvQa0IN"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------00DF2ZMTpnPuoDyQcAvQa0IN
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

On 6/2/2026 11:01 AM, Allen Huffman via Coco wrote:
>> On Jun 2, 2026, at 10:59=E2=80=AFAM, RETRO Innovations via Coco=20
>> <[email protected]> wrote:
>>
>> I second this.=C2=A0 Torrents are great for unchanging material, but th=
e=20
>> web site (I assume) will get updated all the time.=C2=A0 Placing a copy=
 on=20
>> GitHub/GitLab/etc. and letting people pull via cron ensures not only=20
>> that things are always up to date, but git will provide a list of=20
>> what has changed since last pull.=C2=A0 By having the cron/at job save =
its=20
>> output to a timestamped file, you can have a complete record of what=20
>> changed from last time you looked at the files and now.
>
> We could get someone to set up a Git server, since what we would be=20
> hosting (things like book scans, Rainbow magazine, software) would=20
> likely be a violation of terms for a commercial service due to copyright=
.
>
> Though anything that has been officially released to the public domain=
=20
> (like stuff on L. Curtis Boyle=E2=80=99s game site) would be fair game, =
I suspect.
>
> =E2=80=94 A
>
>
>
Setting up the server is easy (Forgejo =E2=80=93 Beyond coding. We forge.=
=20
<https://forgejo.org/>, for example) but we should first get a list of=20
the sites we want to do this with, and see how the maintainers feel=20
about it.=C2=A0 For example:

  * If a site maintainer does NOT want their site mirrored, how do we
    respond?
  * If they do, it would be best if they push their changes into the
    repo directly, as an admin, and then their site just pulls from the
    repo like everything else.
  * Or, maybe they want to host their repo, for control reasons, and we
    can all point to it.

Jim

=2D-=20
RETRO Innovations, Contemporary Gear for Classic Systems
www.go4retro.com
store.go4retro.com

--------------00DF2ZMTpnPuoDyQcAvQa0IN
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DUTF-=
8">
  </head>
  <body>
    <div class=3D"moz-cite-prefix">On 6/2/2026 11:01 AM, Allen Huffman via
      Coco wrote:<br>
    </div>
    <blockquote type=3D"cite"
      cite=3D"mid:4DB4C9E4-6F49-46D5-BDE1-622321B4ED94-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org">
      <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUT=
F-8">
      <div>
        <blockquote type=3D"cite">
          <div>On Jun 2, 2026, at 10:59=E2=80=AFAM, RETRO Innovations via =
Coco
            <a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:coco@listser=
v.adelphi.edu">&lt;[email protected]&gt;</a> wrote:</div>
          <br class=3D"Apple-interchange-newline">
          <div>
            <meta charset=3D"UTF-8">
            <span
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12p=
x; font-style: normal; font-variant-caps: normal; font-weight: 400; letter=
-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-tr=
ansform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-=
text-stroke-width: 0px; text-decoration: none; float: none; display: inlin=
e !important;">I
              second this.=C2=A0 Torrents are great for unchanging materia=
l,
              but the web site (I assume) will get updated all the
              time.=C2=A0 Placing a copy on GitHub/GitLab/etc. and letting
              people pull via cron ensures not only that things are
              always up to date, but git will provide a list of what has
              changed since last pull.=C2=A0 By having the cron/at job sav=
e
              its output to a timestamped file, you can have a complete
              record of what changed from last time you looked at the
              files and now.</span></div>
        </blockquote>
        <br>
      </div>
      <div>We could get someone to set up a Git server, since what we
        would be hosting (things like book scans, Rainbow magazine,
        software) would likely be a violation of terms for a commercial
        service due to copyright.</div>
      <div><br>
      </div>
      <div>Though anything that has been officially released to the
        public domain (like stuff on L. Curtis Boyle=E2=80=99s game site) =
would
        be fair game, I suspect.</div>
      <div><br>
      </div>
      <div><span class=3D"Apple-tab-span" style=3D"white-space:pre">		</sp=
an>=E2=80=94
        A</div>
      <div><br>
      </div>
      <br>
      <br>
      <fieldset class=3D"moz-mime-attachment-header"></fieldset>
    </blockquote>
    <p>Setting up the server is easy (<a href=3D"https://forgejo.org/">For=
gejo
        =E2=80=93 Beyond coding. We forge.</a>, for example) but we should=
 first
      get a list of the sites we want to do this with, and see how the
      maintainers feel about it.=C2=A0 For example:</p>
    <ul>
      <li>If a site maintainer does NOT want their site mirrored, how do
        we respond?</li>
      <li>If they do, it would be best if they push their changes into
        the repo directly, as an admin, and then their site just pulls
        from the repo like everything else.</li>
      <li>Or, maybe they want to host their repo, for control reasons,
        and we can all point to it.</li>
    </ul>
    <p>Jim</p>
    <pre class=3D"moz-signature" cols=3D"72">--=20
RETRO Innovations, Contemporary Gear for Classic Systems
<a class=3D"moz-txt-link-abbreviated" href=3D"http://www.go4retro.com">www=
.go4retro.com</a>
store.go4retro.com</pre>
  </body>
</html>

--------------00DF2ZMTpnPuoDyQcAvQa0IN--

--===============2672483839735680106==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Coco mailing list
[email protected]
http://listserv.adelphi.edu/cgi-bin/mailman/listinfo/coco

--===============2672483839735680106==--