On Fri, Jun 3, 2011 at 3:07 PM, Florian Effenberger
<floeff@documentfoundation.org> wrote:
Hello,
I missed the plot on this a bit - is this a problem at Mail-Archive or in
our implementation?
At mail-archive.com
For reference: The algorithm on how to compute the has is here:
http://www.mail-archive.com/faq.html#listserver
i.e. take the msg-id and the list-addres, create a sha1-hash out of it
an url-encode it.
and when applying that to Friedrich's example, I get the same link
that was added to the message.
But also if the link was wrong, there still would be a problem on
their end, as searching Friedrich's mail by using the message-ID
doesn't work either. And with that functionality being missing, the
hash-URLs got no chance (as the msg-id is a crucial part to it -
msg-ids not indexed → direct links not working).
Might be that they disabled the indexing jobs for some other
maintenance or stuff, or it just died because of some bug - no idea...
Anyone already working on it?
It's forwarded to the mail-archive's discussion list:
http://www.mail-archive.com/gossip@jab.org/msg01397.html
So nothing we can do from our side apart from waiting for a response
(but they're usually pretty fast)
ciao
Christian
--
Unsubscribe instructions: E-mail to website+help@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/website/
All messages sent to this list will be publicly archived and cannot be deleted
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.