After a small discussion this morning (, we're adding support for the `commentsEnabled` field, which is now in both @pixelfed and .

This will land in our next release, v0.9

@writeas_dev Does that mean #writefreely will have post comments functionality? I might be missing something there... I know it works on @Chocobozzz #peertube smoothly 👍 Or for comments to be on WriteFreely will have to wait for @remark_as ? 🤓 @write_as

@writeas_dev @Chocobozzz @remark_as @write_as Sorry, failed to read first: "WriteFreely doesn't support comments today, so this will always be false." 🤓

@gytis Yep :) They'll have to wait for @remark_as. But in the meantime, hopefully other platforms will start supporting this as well, so people can see that comments are disabled right now. And then when we add comments, people will be able to see which posts they're enabled on. @Chocobozzz @write_as

As this new field been discussed by #ActivityPub contributors? Has the spec well written and reviewed? Has all security aspects been considered?
I don't think so...
It appears that this field is wrongly designed: if an #ActivityPub server doesn't understand that (currently) proprietary field, it would allows comments. Useless, and kind of confusing for the initial user...

@malendur It's meant to improve usability -- that's it.

Today if an authoring platform doesn't allow comments on a post, there's no way to communicate it. Since 3 platforms support this function, we've gone ahead with the solution we have today.

This shouldn't be a usability issue but a privacy one. #ActivityPub should be improved on that aspect (and learn from #zot for instance).

@Luka Audionixgenderbender as said, since it's a privacy flag, you can't just use the extensibility of JSON-LD (not #activityPub 's one, not even #activitystreams 'one) to add a proprietary flag... #Pleroma devs explained it clearly, is just wrongly designed.
Sign in to participate in the conversation
A Bunch Tell

This instance is only for A Bunch Tell projects.