[TW5] Commenting Plugin (Google+/DISQUS)

[Chester Cho]

Hi All,

I wanted to try to embed some commenting features to my TW5, so far I have been successfully implement Google+ comment on tiddler basis, however, DISQUS is extremely tricky to implement, so far I have come cross 2 solution but they are not so perfect solution, do you guys have any insight that can share to improve this solutions? Thanks.

https://github.com/sukima/tw5-disqus-plugin

This one look decent, but rather tricky since the README document really isn't readable...I did manage to embed a DISQUS on sidebar with this plugin, but not on tiddler basis.

https://groups.google.com/forum/#!topic/tiddlywiki/msDS-4x8Qms

A workaround DISQUS solution, it works but I want to see if it can be improved.

http://www.chestercho.com/#%24%3A%2Fcore%2Fui%2FViewTemplate%2Fcomment-block

This one is my tiddlywiki5, where the comment-block is the ViewTemplate I embed in every post. It is possible thanks to all the greatly plugins by Tobias (plugin: enable.js, hash, , etc) 

Chester

[Jed Carty]

I implemented comments on my tiddlywiki site using hashover, I did some DISQUS stuff here but I never got it working well, I did an intense debate demo here and I did a muut demo here.

muut can be in each tiddler, but the loading is sometimes weird. The only one that I got to work well is hashover.

[Chester Cho]

Haha, actually I was referring your solution as one of the solution, what I think why comment plugin is rather to implement on TW5 is simply because those JS are not so friendly to static html and they offer little customization option.

I can utilize Google+ comment on per tiddler basis, however the CSS style of that block seems uncontrollable and I am still finding out why. Google+ comment also offer much less control than DISQUS as far I know, so I am still finding the best solution among them.

Chester

Jed Carty於 2016年1月16日星期六 UTC+8上午5時19分32秒寫道：

[Tobias Beer]

The problem with disqus is that it demands hashbang #! to be able to cater for per-tiddler comments and so it does not cater for the plain hash # used by TiddlyWiki.

So, what is required is a modification to the core that would:

1. allow to tell it to ignore any starting bang "!" after the hash #
2. while at it, also allow to encode permalinks with hashbangs #!

And then we' due good to go using disqus in TW.

Best wishes,

Tobias.

[c pa]

>>  implemented comments on my tiddlywiki site using hashover,

I went to the site listed and posted some comments.

1. When I hit the "save" button on the comment, the page tries to navigate away
2. The comments don't seem to save
3. The button to list recent comments doesn't display any recent comments
   

[Tobias Beer]

By the way...

 

The problem with disqus is that it demands hashbang #! to be able to cater for per-tiddler comments and so it does not cater for the plain hash # used by TiddlyWiki.

Here's an issue concerning this that has been lingering about for a while and that I haven't touched yet:

#1188 #!hashbang and disqus compatibility

https://github.com/Jermolene/TiddlyWiki5/issues/1188

I think this will be a great addition to anyone wanting to use TiddlyWiki as a public facing website.

Best wishes,

Tobias.

[Jed Carty]

The comments don't show up because it 1, that is a post meant to just send messages to me and 2, I need to accept any comments before they show up on my site. As it says on the tiddler.

I am not going to let un-moderated comments on my site.

[Jed Carty]

There is some explaination of how hashover works with tiddlywiki here, but there didn't seem to be any real interest in using it so I never bothered to improve the instructions.

[Tobias Beer]

Hi Jed,

 

There is some explaination of how hashover works with tiddlywiki here, but there didn't seem to be any real interest in using it so I never bothered to improve the instructions.

Would be nice if that write-up would actually show how / where it's used.

Also, that splash-screen on your site, what is that?

Best wishes,

Tobias. 

[Chester Cho]

I've looked the issue, but seems self-hosting some commenting system such as Discourse is the only viable solution atm, however this seems to be little counter-intuitive as TW5 is supposed light-weight. Perhaps I should keep my TW5 with those simple Google+ commenting system, since it doesn't actually require heavy discussion.

Tobias Beer於 2016年1月20日星期三 UTC+8下午2時34分36秒寫道：

[Jed Carty]

I am working on some native tiddlywiki commenting systems using the federation ideas at the moment. Because of how tiddlywiki works it is going to be a very different commenting system than the server driven systems that currently exist but it should work.

One seemingly counter-intuitive difference is that if you wanted to comment on my site you would leave the comment on your site and then when I check for comments I would pull them from your site onto mine. This seems weird but it is the logical way to make a distributed commenting system like we need for tiddlywiki.

[Nicolas Mathey]

Hi Jed,

Any progress on your commenting system work? 

I do have also a project in mind to use TW for a collaborative learning platform: TW non-linear concept is perfect for this but lake the "social/community interaction" piece.

[Jed Carty]

I think that we pushed the basic twederation idea for connecting wikis about as far as it can go, at least as far as the technology is concerned. But we didn't get any interest in it outside the small group working on developing it and I think that we all got distracted by other projects. Twederation works, hashover worked for comments but on my site we changed hosts and I never updated the credentials so it is broken there.

My more recent work on the multiuser wikis can probably be used for similar things but I haven't worked on that aspect of it.

[TonyM]

Jed,

I have always being interested in the outcomes of TWFederation, even interested in helping. However every time I tried to learn more it was quite intimidating or had to follow, perhaps because is was more about the technical node stuff. 

I suppose what I am saying the absence of feedback does not necessarily translate into absence of need or interest. 

The difficulty of understanding TWFederation means I have being slowly building a structure of loosely coupled  TiddlyWikis, the first step is almost complete, a way of registering and sharing multiple-tiddlywiki's information to a directory and back out to all Wikis in a network of wikis. The next phase will be finding a way to send tiddlers or sets of tiddlers like a message to other wikis, perhaps even distribute plugins that way.

Truth is I am yet to delve into NodeJS beyond its local hosting solutions including yours and tiiddlyserver. So I have not started playing with the underlying files.

I can see that on a single NodeJS it may be quite easy to integrate wikis but I am interested in single file wikis and multiple hosts as well.

Regards

Tony

[Jed Carty]

TWederation was done completely with single file wikis, none of it used node. And it does what you are describing, it builds a listing of wikis available and give a method to distribute tiddlers among those wikis.

[Ste Wilson]

I signed up one of my wikis to TWederation and the instructions on the site were fairly straightforward.
I think from an end idiot users perspective (ie me) the renaming of shared tiddles with a date stamp to generate a uid is off putting. Would any of the recent discussions around this be applicable /implmenatble to keep titles the same and not break the original tiddlyWiki?

[TonyM]

Jed,

I will review it again in light of you comments and my own advances in understanding.

Thanks
To