Hi all ... apologies for not checking in, and I also missed zoombee's PM ... (I don't check FT much these days).

The current situation is because I let the domain expire, I apologise for any inconvenience this has caused. From what I could see, the data in MM was quite old, and I didn't have a good feel for how much it was used (most of the hits in the logs seemed to be from automated checks, rather than real people). It became more & more time consuming for me, and I don't make any money from it at all, in fact it cost me money for domain names etc.

It seems that someone has taken over the slfft.org domain now (see below) - if we need to move to a new domain, it's not too big a deal. Looks like DropCatch (who registered it) do this on expiring domains, and then try to auction them off. There's no value in the domain slfft.org, so no need to pay them anything to get it back (it just means updating links as & where needed).

Current MM Status:
- source code is secured; much of it is in GitHub
- I still have the hosting up which was behind slfft.org, I just let the domain lapse
- flight & airport databases are secured, but fairly out of date (e.g. flight schedules)
- OW rules are out of date, the code has not been updated for some years to reflect changes
- the tool is static/standalone, it does not require a server connection (apart from loading maps etc.)
- it's written in JavaScript. hauteboy wrote most of it, I have added bits & pieces, and also updated the flight DB
- there are other tools I wrote which take the raw data and produce the flight DB. These are only partially on GitHub, some I didn't want to share

To make MM useful again involves the following:
== determine what level of interest in bring it up to date ... there's no point doing a ton of work if there is no use for it
== getting a domain to host it on (again, the actual hosting part isn't an issue at this point)
== securing a source for flight schedule updates
== updating the code which produces the MM flight DB from the new schedule source
== updating the OW rules code within MM
== me to get the build process back together

There are lots of other improvements which could happen ... but the key part is securing the flight schedule data to make this useful.

I'm certainly willing to work with someone on this....if you think you can help from securing a domain, as a javascript programmer, securing a source of flight schedule updates etc.... then please contact me. I'll make an effort to stop by here as well as look out for FT PMs.

Domain Name: SLFFT.ORG
Registry Domain ID: D402200000008748683-LROR
Registrar WHOIS Server: whois.namebright.com
Registrar URL: http://www.NameBright.com
Updated Date: 2018-12-24T05:04:40Z
Creation Date: 2018-12-21T14:30:38Z
Registry Expiry Date: 2019-12-21T14:30:38Z
Registrar Registration Expiration Date:
Registrar: DropCatch.com 1292 LLC
Registrar IANA ID: 3501
Registrar Abuse Contact Email: [img]https://source.domaintools.com/email.pgif?md5=364741e308ddbc35367f1de06df5a82e&fa ce=arial&size=9&color=000000&bgcolor=FFFFFF&face=a rial&size=9&color=0000FF&bgcolor=FFFFFF&format=tra nsparent&format=transparent
Registrar Abuse Contact Phone: +1.7204960020
Reseller:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited
Registrant Organization:
Registrant State/Province: Grand Cayman
Registrant Country: KY
Name Server: NS1.BRAINYDNS.COM
Name Server: NS2.BRAINYDNS.COM
DNSSEC: unsigned