-
2016.09.07 16:38 "Re: [Tiff] remotesensing.org URLs (http and ftp)", by Even Rouault
-
2016.09.07 18:42 "[Tiff] Fwd: Re: remotesensing.org URLs (http and ftp)", by Even Rouault
-
2016.09.08 14:19 "Re: [Tiff] Fwd: Re: remotesensing.org URLs (http and ftp)", by Jeff McKenna
-
2016.09.08 14:51 "Re: [Tiff] Fwd: Re: remotesensing.org URLs (http and ftp)", by Bob Friesenhahn
- 2016.09.08 14:58 "Re: [Tiff] Fwd: Re: remotesensing.org URLs (http and ftp)", by Jeff McKenna
-
2016.09.08 15:11 "Re: [Tiff] Fwd: Re: remotesensing.org URLs (http and ftp)", by Even Rouault
-
2016.09.08 16:26 "Re: [Tiff] Fwd: Re: remotesensing.org URLs (http and ftp)", by Bob Friesenhahn
-
2016.09.08 17:01 "Re: [Tiff] Fwd: Re: remotesensing.org URLs (http and ftp)", by Edward Lam
-
2016.09.13 11:32 "Re: [Tiff] Fwd: Re: remotesensing.org URLs (http and ftp)", by
- 2016.09.13 13:21 "Re: [Tiff] Fwd: Re: remotesensing.org URLs (http and ftp)", by Olivier Paquet
-
2016.09.14 02:34 "Re: [Tiff] Fwd: Re: remotesensing.org URLs (http and ftp)", by Bob Friesenhahn
- 2016.09.14 12:34 "Re: [Tiff] Fwd: Re: remotesensing.org URLs (http and ftp)", by Jeff McKenna
-
2016.09.14 20:26 "Re: [Tiff] Fwd: Re: remotesensing.org URLs (http and ftp)", by Kemp Watson
-
2016.09.16 15:26 "Re: [Tiff] remotesensing.org URLs (http and ftp)", by Kemp Watson
- 2016.09.16 15:32 "Re: [Tiff] remotesensing.org URLs (http and ftp)", by Jeff McKenna
- 2016.09.16 16:21 "Re: [Tiff] remotesensing.org URLs (http and ftp)", by Bob Friesenhahn
-
2016.09.16 15:26 "Re: [Tiff] remotesensing.org URLs (http and ftp)", by Kemp Watson
-
2016.09.13 11:32 "Re: [Tiff] Fwd: Re: remotesensing.org URLs (http and ftp)", by
-
2016.09.08 17:01 "Re: [Tiff] Fwd: Re: remotesensing.org URLs (http and ftp)", by Edward Lam
-
2016.09.08 17:53 "Re: [Tiff] Fwd: Re: remotesensing.org URLs (http and ftp)", by Rick Widmer
- 2016.09.08 18:29 "Re: [Tiff] Fwd: Re: remotesensing.org URLs (http and ftp)", by Lee Howard
-
2016.09.08 16:26 "Re: [Tiff] Fwd: Re: remotesensing.org URLs (http and ftp)", by Bob Friesenhahn
-
2016.09.08 14:51 "Re: [Tiff] Fwd: Re: remotesensing.org URLs (http and ftp)", by Bob Friesenhahn
-
2016.09.08 14:19 "Re: [Tiff] Fwd: Re: remotesensing.org URLs (http and ftp)", by Jeff McKenna
-
2016.09.07 18:42 "[Tiff] Fwd: Re: remotesensing.org URLs (http and ftp)", by Even Rouault
- 2016.09.07 17:20 "Re: [Tiff] remotesensing.org URLs (http and ftp)", by Bob Friesenhahn
- 2016.09.16 16:47 "Re: [Tiff] remotesensing.org URLs (http and ftp)", by Fred Rothganger
- 2016.09.25 21:59 "Re: [Tiff] remotesensing.org URLs (http and ftp)", by Bob Friesenhahn
2016.09.09 12:22 "Re: [Tiff] Fwd: Re: remotesensing.org URLs (http and ftp)", by Dimitri Schoolwerth
On 8 September 2016 at 22:29, Lee Howard <faxguy@howardsilvan.com> wrote:
On 09/08/2016 10:53 AM, Rick Widmer wrote:
libtiff.info is available. maybe others too.
So is/was libtiff.io (or did the .io fad fade?), but a quick search shows those are a lot more expensive than most other domain extensions.
As the domain seems to be otherwise completely unused by the registrant I can't imagine why they have an interest in keeping it.
I suppose there are parties that don't mind developers going for an older, less secure, libtiff version. Hopefully not libtiff.org though.
I've just paid $76.15 to GoDaddy for their "Buy Domain Service" for libtiff.org to hopefully see what the registrant wants for it.
Ouch. Another entry for the list "Reasons not to use GoDaddy"...
On 9 September 2016 at 14:16, Gary McGath <developer@mcgath.com> wrote:
> There's an "unofficial mirror" at (https://github.com/vadz/libtiff). Its > most recent update is 5 days ago. Is it reliable?
Vadim Zeitlin is, amongst other things, also still the main contributor of wxWidgets and I have zero reason to think he has any bad intentions. I can't vouch for what "git cvsimport" outputs as I have no experience with that.
[OT]
> I ask because I've posted on my file-formats blog about the situation > (https://madfileformatscience.garymcgath.com/2016/09/08/libtiff-offline/) and
> would like to mention that as a stopgap link, but I want to make sure > it's OK.
That's a site that I sometimes see in search results. Thank you for that site :-).
Regards,
Dimitri