welpo
commented
1 week ago All of the existing commenting systems that have been implemented by tabi require commenters to log in to a centralised service
Just noting Isso allows anonymous comments: all fields are optional by default, and no account is needed.
Perhaps instead of a shortcode it could be triggered by placing a setting in the
[extra]section, and then the same technique of using a script to update the frontmatter could be used.
That would be preferred for maintenance, yeah. Also using a specific [extra] section in config.toml.
additionally having a shortcode for it would probably still be desirable as that would bring the nice possibility of being able to embed multiple Fedi posts and optionally their comment threads
Can you elaborate? My idea would be as you mentioned: publish a post, mention this on the Fediverse, and use that thread as the comments of the post. In what instance might one want two separate comment sections?
I would be happy to add this to tabi. Indeed, I almost implemented this myself, but I decided four comment systems were enough :)
However, I had bookmarked a nice guide for Hugo. This could serve as a nice reference to implement the feature on tabi.
I'm afraid that doing this work myself is beyond me
Even after looking at the post/guide above? I can't prioritise working (solo) on this feature right now, but I'd be happy to complete a PR or provide guidence along the way!
grifferz
Thanks for this theme. I am very much enjoying making sites with it!
Feature Request
Provide a means to embed a Fediverse (Mastodon) conversation in a page, typically the thread of comments related to a post about the article itself.
Summary
As an alternative to the four existing commenting systems, would you consider adding a view of comments from an associated Fediverse post, such as this existing implementation?
Motivation
All of the existing commenting systems that have been implemented by tabi require commenters to log in to a centralised service, for example GitHub or yet another third party system (even if it is one that the site owner self-hosts like Isso).
Although not everyone has a Fediverse account, it is at least possible for anyone to have one without signing up to a specific service. If a commenter really wants to they can even self-host a Fediverse instance.
It is common to post a notification link about a new blog post or article onto a service like Mastodon, so it's natural for people who became aware of the article to respond on Fedi with their thoughts and comments. If these then are displayed on the article as well then it can bring a fuller experience to site visitors who would ordinarily never go onto the Fediverse to see that conversation.
Detailed Description
Using the linked webcomponent as an example, the way I see it working is something like:
That would embed the display of the conversation rooted at https://fosstodon.org/@dpecos/109574160582937075
Of course, if
hostanduserare set in configuration then the actual shortcode would be a lot smaller as the only variable that would need to change per-page would be the toot ID.The need to update the post with a directive containing the toot ID is a bit clunky but conceptually similar to the problem you discuss with social media cards, in that you are there looking to update the card image path in the frontmatter after the initial post was made; here looking to update a toot ID after a Fedi post related to the post is made.
Perhaps instead of a shortcode it could be triggered by placing a setting in the
[extra]section, and then the same technique of using a script to update the frontmatter could be used. That is probably more suited to automation than having to put a shortcode somewhere in the article, and I guess you would always expect the conversation to be at the bottom anyway.So now that I think more about it, having it as a config setting is probably more sensible in most cases, but additionally having a shortcode for it would probably still be desirable as that would bring the nice possibility of being able to embed multiple Fedi posts and optionally their comment threads.
What do you think?
I'm afraid that doing this work myself is beyond me, so I will just end up using the suggested webcomponent directly from a shortcode. It just seemed a nice feature that could be built in to tabi.