-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace hacked website mvmanila.com #469
Comments
It is not hacked. Don't use inflammatory language when the truth is sufficient. I turned it off several years ago. I can do that because I paid for it. Nobody cared very much back then. |
Dear Cecil, Does anyone have the original files and webpages that were on the old mvmanila domain (and which are still being referenced in a lot of places on the shoesrb website and in this github repository) ? |
Cecil, without that final 'e' ;-). I probably have backups of the mvmanila website pages since it was my domain and website. The shoesrb website is statically generated from a template maintained by the Shoes4 folks (also a dead project).. The problem is nobody wants to do the work - AND it is a lot of work and some of it very obscure, like Windows C development experience. And OSX Objective C developers. Even if you could find those people it is so out of date the first thing they would do is update everything and that would take a year or two (part time). Shoes is dead. |
Since the mvmanila.com domain was hijacked, parts of the documentation and the downloads packages are lost (or not accessible to the public).
Could some of the maintainers of this repo replace any reference to the lost website mvmanila.com to a new (active and proper) website?
Would you need some help in setting up a new domain/hosting?
Or could the main shoesrb.com website be used to migrate all the old material that was on the mvmanila.com website? (Hopefully you still have the old webpages and files)
Also, don't forget to remove from the shoesrb.com website any references to the hijacked mvmanila.com website.
The text was updated successfully, but these errors were encountered: