-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It's technically mike's side that handles torrent generation currently, not ooodev.org.
If you have an rsync folder that I can use to automatically load the .torrent files from your side, it can be set up fairly trivially to have the torrents authenticated on the depthstrike.com trackers within 2 hours of generation automatically. It is currently not a good idea to accept all torrent infohashes without discrimination, especially for this project. The load spikes are potentially system crippling. - - Harold On 30/08/2010 3:22 PM, Peter Pöml wrote: > Hi Tatsuhiro, hi list, > > Le 05.08.2010 à 17:05, Tatsuhiro Tsujikawa a écrit : >> Hi, >> >> (08/05/10 11:55), Peter Pöml wrote: >>> Hi Tatsuhiro, hi *, >>> >>> Am 21.07.2010 um 17:43 schrieb Peter Pöml: >>> >>> >>> I believe I have fixed the issue, and download.services.openoffice.org >>> delivers the correct BitTorrent Information Hash now: >>> >>> % curl -s >>> http://download.services.openoffice.org/files/localized/ja/3.2.1/OOo_3.2.1_Win_x86_langpack_ja.exe.meta4 >>> | grep magnet >>> <metaurl >>> mediatype="torrent">magnet:?xt=urn:btih:78ebf160c1924d2ff098535bb0362172f467708c& >>> [...] >>> >>> This is not the same hash as the one that torrent.projects.ooodev.org gives >>> -- due to a difference in block size (262144 vs. 131072 bytes). Otherwise, >>> it should fit. I tested with the smaller block size and verified that the >>> hash would be identical in that case. >>> >> >> Thanks Peter. >> >> I think this is a temporary issue until next mirror brain release, but I >> think btih info hash in magnet URI and info hash in tracker must be >> matched to make magnet URI work. >> Because magnet URI does not contain Metadata, BitTorrent client must >> retrieve it from other peers. It first contacts tracker with btih info >> hash. If btih info hash and infohash in tracker are different, tracker >> complains that it does not know that torrent and no peers are returned. >> When using current .meta4 file, all tracker returns failure message, >> which means magnet URI is not usable. > > I see. Indeed, this is the case now. > > I have made the chunk size in MirrorBrain configurable now, and I matched it > to the chunk size that the torrent.projects.ooodev.org size uses. > > So now, the btih is the same. > > On a related note, since none of the used trackers currently allows > unregistered access, I have set up an experimental tracker on my own > (bt.mirrorbrain.org:8091) which allows it. For now, that's the only tracker > sent along with torrents delivered by download.services.openoffice.org. > Hence, the torrents should actually be usable now. I could successfully > download various files a number of times today, when experimenting. > > Thanks a lot for your feedback, > Peter > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJMe/sZAAoJEF8nceBm0DUaaLMH/12gcdgTcrj6mEIV7l82Vl3m i88lJkFGtAbZPYtr1YcK24+TrSx2pSLKG5KgkpG4QD/gSVXxwr/mAnOApJXJOfxt 6nheW7jmJoqF9E0kPHOwzl+6+SwTQ3VJSiyuUbyo7D7RPe/DwogQ/hvk3085T1iv Ardxm1cBetq+roMe1FMt9cyM46vmtkpzsQW4JPby6gtdD7F5hd5iuyaKhC/wR87w hGdZyUMT31qW/wDeUGvoTosXz93TJoL3zkHkyDgM6XVHLC6MpcbsPs0KFeu2DwKk ODoFXrFtJhGh1Jd/A0vFwb96usjO/y9ARvkz1nMs5nuwl1ntA8FhuShAZLAvO8Q= =HOxb -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
