-
Notifications
You must be signed in to change notification settings - Fork 122
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
Archive Repo #112
Comments
I don't think that is a good idea since native search has limits. |
I mean the GhostHunter search has limits as well, including but not limited to the fact that its main maintainer for the past four years (me) doesn't actually know Javascript and doesn't even use Ghost anymore... |
@Windyo Thank you for your honest reply! If you're the main maintainer for the past four years and you don't actually know JavaScript and don't even use Ghost anymore, then I withdraw my objection. |
Yeah, in short I just stumbled upon GhostHunter when Ghost published its internal API at the time. The official API versio was v0.1, there wasn't content api keys or anything. GH used RSS at that point to fetch the posts and that started to slow down starting at 100 posts, and got worse progressively as to be nigh unusable after something like 200. My main contribution was learning just enough javascript based on my BASH skills to see how to call the API from GH and shove that into the lunr array in my own fork. I opened a PR thereafter. Over the years I did a bit of maintenance here and there, added functions as I needed them (description parsing etc), followed Ghost versions, added merges from people that followed code styles, but that's pretty much it. If you check forks, a few people have done refactoring which was sorely needed. I stopped using Ghost two years ago when I completely stopped blogging, and my career path never needed me to really learn Javascript, so in effect yes - GhostHunter has been pretty much fully maintained by a person that doesn't know JS for the past 4 years. :) Yes, I know no one cares, but it's not a story that I can break out at parties :D |
@jamwise new official search feature means we should archive this i think.
The text was updated successfully, but these errors were encountered: