August 01, 2014
On Wednesday, 30 July 2014 at 03:43:55 UTC, Walter Bright wrote:
> On 7/29/2014 2:47 PM, Andrei Alexandrescu wrote:
>> There's a pretty negative article about disqus making the rounds:
>>
>> http://www.reddit.com/r/programming/comments/2c19of/your_users_deserve_better_than_disqus/
>>
>>
>> Since we're considering adding disqus flow to our docs, we better think this
>> well. Any thoughts?
>
> The bit about Disqus tracking users bothers me. I know that's what one gets with "free", but I'd prefer our own system like Vladimir's awesome forum software.

Yeah, that seems outright creepy and very invasive. I think that even if we were to decide that we wanted a documentation comment system and we wanted it to have the feature set that Disqus does, we should either find another, existing system which has those features but not the tracking, or we should roll our own. And I don't think that rolling our own would be that hard. Some aspects of it wouldn't be all that different from what the forum software already does, and we already have some great tools for web stuff like vibe.d.

- Jonathan M Davis
August 01, 2014
On 7/31/14, 11:40 PM, Jonathan M Davis wrote:
> I think that even if we were to decide that we wanted a documentation
> comment system and we wanted it to have the feature set that Disqus
> does, we should either find another, existing system which has those
> features but not the tracking, or we should roll our own. And I don't
> think that rolling our own would be that hard.

Don't forget that whenever I read this, I take it you volunteer to do it - and somehow chose to use the royal "we" :o). -- Andrei

August 01, 2014
On Friday, 1 August 2014 at 06:40:40 UTC, Jonathan M Davis wrote:
> ... or we should roll our own. And I don't think that rolling our own would be that hard.

I'm with you. I think Disqus is for those who don't know how or don't want to write this kind of mechanism. I think this community has great people that can do this easily.

Matheus.
August 02, 2014
On Friday, 1 August 2014 at 14:42:41 UTC, Andrei Alexandrescu wrote:
> On 7/31/14, 11:40 PM, Jonathan M Davis wrote:
>> I think that even if we were to decide that we wanted a documentation
>> comment system and we wanted it to have the feature set that Disqus
>> does, we should either find another, existing system which has those
>> features but not the tracking, or we should roll our own. And I don't
>> think that rolling our own would be that hard.
>
> Don't forget that whenever I read this, I take it you volunteer to do it - and somehow chose to use the royal "we" :o). -- Andrei

LOL. Well, the truth is that I don't think that the problem is big enough to be worth going to the effort of writing a comment system. I don't even like the idea of having a comment system on the official documentation. I just think that if we're going to do it, then we need to not use one that's going to be tracking everyone like Disqus does and that we probably should write our own. But I'd prefer that we don't have one at all.

- Jonathan M Davis
August 05, 2014
Hi,​
did you consider using Discourse at least as a replacement for comments
system?  http://www.discourse.org/
It's made by the guys who made stackoverflow.com and it's useful at least
as an alternative to disqus and
also obviously as a forum.
Some blogs (using wordpress) do use Discourse for comments.
However, Discourse backend is wrote using ruby so if you want to self host
you have to do some install work but
they simplified it apparently by providing a docker as the default
installer.


August 11, 2014
On Tuesday, 5 August 2014 at 11:00:44 UTC, Klaim - Joël Lamotte via Digitalmars-d wrote:
> Hi,​
> did you consider using Discourse at least as a replacement for comments
> system?  http://www.discourse.org/
> It's made by the guys who made stackoverflow.com and it's useful at least
> as an alternative to disqus and
> also obviously as a forum.
> Some blogs (using wordpress) do use Discourse for comments.
> However, Discourse backend is wrote using ruby so if you want to self host
> you have to do some install work but
> they simplified it apparently by providing a docker as the default
> installer.

Curious why no one replied to this?

I can not vouch for this one but it looks nice if you go to the demo site on the readme page: https://github.com/phusion/juvia

As a meta-question - is there any way for threads like this be ended with some form of NextAction required? Or is the best course to just let it fall to the wayside?

Thanks
Dan
1 2 3
Next ›   Last »