That would be great if ghost team should add internal ghost commenting system. This would help us to easily manage comments from our admin panel instead of depending on third parties. Now discuss started showing ads in his comment box section and that was not good at all. I would highly recommend having self-hosted comment system or that would be great if ghost team include this feature in their future upgrades.
While I agree on native commenting would be really nice:
Why don’t you try Isso from posativ for now? There’s some blogs out there on how to set it up and integrate it into your ghost blog. I’ve got it up and running for my blogs and it’s like disqus, but it’s not tracked or hosted by third parties.
times like these make me wonder why any sort of non-breaking gateway to ghosts’s db hasn’t been implemented in any form, even creating a generic API endpoint to allow diehardhard users to mess with an otherwise irrelevant table in the ghost data base would be an infinite improvement over nothing.
I fill the gaps between ghost themes and extended data by using MongoDB’s could cloud service, but that sort of workflow is best suited for the certifiably insane and I don’t see this suiting many people.
I’am still new to GHOST as a kinda Blogging CMS for me but i don’t support nor like the Idea of a native System for Comments implemented deeply within the Core. In my humble Opinion the Demand for this Functionality would be better solved as a Plugin or Add-On that can turned On/Off if necessary and works more like an Extra instead of a Component of the Core.
WordPress for Example has a build in System for Comments and it’s a Mess like the rest of it. I know that GHOST doesn’t work like WordPress and that’s a good Thing. So we should see GHOST as what it is and what it shouldn’t become, the next WordPress-Like-Thing.
GHOST is for Publishing, anything above that is Optional in my Opinion.
Commenting systems are not easy to do right. They’re also a classic iceberg problem, where it seems like a small thing but a mountain lies beneath. Because of spam and bad actors, you automatically need filtering and moderation tools. And these in of themselves are projects of their own.
I set up a site with Discus but switched to IntenseDebate. I find it to be a much better solution. The comments are less cluttered, easier to configure and they use the site’s CSS so they look natural. It is easy to moderate and the junk filters are configurable and effective. System is built and maintained by Automattic (sp) the same folks that built WordPress so it should have some longevity. Here is a page that has a couple comments. Thousand Islands Land Trust, Happenings July 2019
Exactly how I feel, Ghost needs to keep a clean core to keep it fast and uncluttered; that being said, a module system for Ghost which allowed for extensions (without using webhooks or similar) would be really nice. The current extensions feel really cluttered and convoluted to me, as your passing a bunch of public data around to get anything to work.
Ghost is not a Blog but a light CMS, by definition a Blog must have a build in System for Comments but adding this feature does not make it a WordPress.
The performance depends of how the code is made, not of the features,
FreeOffice for example has most of the Excel features and it runs a lot faster, is more accurate and needs less resources.
I agree Ghost needs and internal commenting system. Actually it is mandatory if it really aspires to become a professional tool.
As a creator you need to be in contact with your audience and “likes” and “comments” are the modern way. (even this forum have likes).
The true method to get good ranks in SEO are comments and shares. Ghost should manage trackbacks and pingbacks too.
Comments are so important that big editorials charge you just for commenting ie Condé Nast
If Ghost goal is to make it simple for publishers, it must have the tools in its system, instead of forcing them to manage one vendor per feature.
Even Facebook and LinkedIn can be used as Blogs and they have all the tools that people loves so Ghost needs to be one step forward. The membership tool is good, but it will need more to make professionals to change, even from WordPress.
I may advice the Ghost team to get the point of view of professional creators/publishers. Now with the hosted service the technical side does not matter any more.
It is not the same to upload a page with a disquss widget than making money with your content.
If you’re looking for something that’s fast loading and more integrated with your site then there’s always the JAMstack approach. Using Ghost as a headless CMS you can combine it with services like Staticman in a seamless static site.
Rest assured we are reading all your comments and listening to your feedback, but we believe there are a lot of options out there that are already doing a great job
I agree with the above comments that comment functionality should probably be provided via a tight integration and native support for a specific plugin as opposed to being built into core. However, that leaves the question of which commenting plugin Ghost should select to provide native support for. The way I see it is this:
The options discussed above are ‘open’ and in line with Ghost’s core values, but are often a) less powerful b) may not have a secure development future
Options like Disqus suck for obvious reasons
I’m surprised no one has discussed the option of providing native support for Coral Talk yet. Coral was created by Mozilla and recently acquired by Vox Media who have maintained its open source license (and who state will keep it open source in future), and has strong adoption in a lot of enterprise publishers. Seems like a nice middle ground between the considerations discussed in 1) and 2), i.e. the balancing act between ‘power’ and continued development.
Of course, if this option is to be explored, Ghost will have to speed up moving to Node12 as ‘recommended support’ from v10, as Coral only supports Node12 and above.