Re: Announce: amnesia Live system 0.4.2

[Timo Schoeler <timo.schoeler@xxxxxxxxxxxxx>]

thus Hannah Schroeter spake:
> Hi!

Hi,

> Just checked a bit.
> On Wed, Feb 10, 2010 at 11:13:05AM +0100, intrigeri wrote:
>> Hannah Schroeter wrote (09 Feb 2010 21:26:07 GMT) :
>>> 404 Not found for both the RSS and the Atom.
> 
>> oops, sorry, the correct links are:
> 
>> - RSS: https://amnesia.boum.org/torrents/rss/index.rss
>> - Atom: https://amnesia.boum.org/torrents/rss/index.atom
> 
> They're right now.
> 
>>> Btw, if you want people to do something (keep seeds running),
>>> perhaps make it less work for them. I.e. push principle instead of
>>> pull principle (having to actively "poll" a feed on and off, no, I'm
>>> not one of the RSS/... junkies anyway).
> 
>> Well, this would be great, but I don't know any way of pushing new
>> .torrent files to seeds we don't manage ourselves; we need to research
>> this, as solutions probably exist already. Any idea?
> 
> I don't see a *completely* automatic solution, and I didn't mean it
> either. I meant things like announcing them by mail (and ensuring that
> one doesn't need *too* frequent updates,

+1. I could provide a bunch of well-connected machines seeding, but
updates on new releases would be best by email. I like it old school. ;)

> as that would pose additional
> workload on seed operators, as well as additional download load to them,
> too).
> 
>>> One also has to follow quite many links from the start page (or the
>>> download page) to finally actually *get* to the torrents. Perhaps
>>> optimize the link depth?
> 
>> Ack, we will try to fix this.
> 
> Okay.
> 
>>> wget also complains about a certificate mismatch
> 
>>> $ wget
>>> https://amnesia.boum.org/torrents/files/amnesia-i386-gnome-0.4.2-20100207.torrent
>>> --22:25:04--
>>> https://amnesia.boum.org/torrents/files/amnesia-i386-gnome-0.4.2-20100207.torrent
>>>            => `amnesia-i386-gnome-0.4.2-20100207.torrent'
>>> Resolving amnesia.boum.org... 204.13.164.189
>>> Connecting to amnesia.boum.org|204.13.164.189|:443... connected.
>>> ERROR: certificate common name `boum.org' doesn't match requested host
>>> name `amnesia.boum.org'.
>>> To connect to amnesia.boum.org insecurely, use `--no-check-certificate'.
>>> Unable to establish SSL connection.
> 
>> Agreed, this is truly annoying.
> 
>> The certificate is actually valid: it has the *.boum.org wildcard
>> listed in "Subject Alternative Name". Many clients, such as wget,
>> don't understand such valid, though uncommon, certificates. I'll ask
>> the webhost sysadmins to get a new certificate with amnesia.boum.org
>> explicitly listed as a SubjAltName.
> 
> Okay.
> 
> Staying tuned a bit.
> 
> Kind regards,
> 
> Hannah.
> ***********************************************************************
> To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxxx with
> unsubscribe or-talk    in the body. http://archives.seul.org/or/talk/
> 

***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxxx with
unsubscribe or-talk    in the body. http://archives.seul.org/or/talk/