Don’t take me wrong: Write.as is the best at what it does, and I know that it strives to be a minimalist, distraction free, focus-on-just-writing platform. Actually, it’s the best writing platform out there. And that’s what it is: a writing platform. Not a blogging platform.
I’m really looking forward for the development of Remark.as, but if it’s not a priority, then that’s a deal breaker for me.
Disturbingly unbelievable. So this is what happens when you upset some random nameless powerful people that just don’t want your open source project to ever come out of the paper. The worst part of it is that we don’t even know why they’re being banned everywhere.
Thanks for the feedback, everyone. Please feel free to keep discussing, but just wanted to address some things.
First, from what I’ve personally seen on the service over the years (and as some have mentioned here), this probably isn’t a crucial feature for most people on the platform. Most people just want to get their thoughts out without hearing what others think. It’s a rare bit of peace and quiet on the web today that I’d really like to keep enabling, which is why no comments will remain the default.
Still, we’ll be moving Remark.as forward probably in the second quarter of this year. I wrote a post about what I’d like it to accomplish (it’s a bit long, so you can skip to the end for the summary), but it’s going to incorporate everyone’s feedback here, too, so I appreciate it!
This is very cool! Looks pretty mature, and I love the clean UI. But I really want to build Remark.as around a certain workflow, so I think it needs to be made that way from scratch. Still, I appreciate you mentioning this! Your system could be a great alternative for anyone who doesn’t find that Remark.as meets their needs.
Agreed – like I wrote in that blog post, I think this is one of the main problems to solve. Most commenting systems miss the mark.
Again, we are going to build Remark.as. But like you mention, we’re a writing platform – and I think that’s why many agree that comments aren’t crucial for everyone. Our focus is on writers, and comments end up taking most writers away from their real work.
And this isn’t not a priority – it’s just lower priority than features like email subscriptions and ePub exporting, which we have in development right now. I know people want this feature, but we can only do so much at any given time, so we have to decide the order in which to do things. It doesn’t mean Remark.as won’t happen
This. And, as you mention, any comment system needs to promote thoughtful, quiet conversation rather than bombardment of reactionary blurbing.
I’ve found it fascinating since my brain injury in 2002 how I shifted my understanding of email, without realizing it at first. Others with brain injury interact in support groups via email with very thoughtful dialogue, but folks I email outside that community use email mostly as “FYI,” not to be interacted with. As Facebook increased in pupularity, email support group participation dropped rapidly, except for a few who needed the simplicity of email.
I’m not sure what this says other than the platform can be well designed for thoughtful interaction yet it also requires people chooseing to interact well and may not know or remember how until they discover it. How to promote that discover, of the art of conversation?
To make commenting more human , it needs to become conversation rather than commentary. Someone talking at you through a television or lonely comment on a blog isn’t natural and human; a conversation is. If you want to talk to an author, you should be able to do that directly — no public side is needed. Then, if your conversation turns out to be of interest or use to more people, you should be able to make it public, where it can stand as a work in itself.
The most important feature for me would be able to disable it completely. I don’t want comments, I don’t like comments . My dislike grew over the years of managing several blogging platforms with tons of spam. Also, it is a lot of work as blog owners are more or less “liable” over here (where that is true in lawyer terms, I do not know 100%. But you need to manage your comments and remove comments that would break a law if someone makes you aware of these comments. Total hassle .
I love the idea of a comment system that is native and optional for write.as. The biggest feature that I’d want to see is the ability to import comments from social (whether it’s activity pub or otherwise). However, I don’t think that’s a game changer. Honestly, if comments looked like/worked like they do here, that would be pretty dope.
This may have been mentioned, I didn’t read 100% of the responses. But the ability to turn comments on by the post… sometimes you want input and sometimes you just want to speak your mind without others opinions… thoughts?
I am very much interested in Remark.as available to install as own instance. Considering great experience provided by WriteFreely, I expect you guys can make Remark.as as one more clean, fast and smooth open source project.
Even though I got into fediverse this year, I already enjoy Mastodon, PeerTube and WriteFreely. While Mastodon is excellent Twitter alternative, I use WriteFreely as draft notebook for quick notes that some time in the future might become full featured posts on my heavyweight blog. It would be great to receive ActivityPub comments to WriteFreely posts!
While PeerTube has fediverse comments capability, my wish would be to have comments system to integrate with WriteFreely (and perhaps PeerTube too?) to have single comments lifecycle (moderation, user authentication, etc.).
If/when Snap.as goes public as open source project, it could also reuse Remark.as for it’s comment functionality.
Main driver for me to choose WriteFreely was aim to learn Go lang so I hope in a while I’ll be able to contribute and hopefully help with Snap.as and Remark.as if/when they become open source