Support for comment visibility #217

New issue

Closed

opened 2018-09-12 17:32:56 +00:00 by trinity-1686a · 4 comments

trinity-1686a commented

2018-09-12 17:32:56 +00:00

Owner

Currently any comment Plume receive is shown on the bottom of the concerned post. Visibility for blog post may be assumed to be public, however comments from other software of the fediverse should probably have their visibility respected

1000i100 commented

2018-10-18 06:59:45 +00:00

(Migrated from github.com)

Visibility for blog post may be assumed to be public
As default, perhaps, but as the only option, in my opinion, no.
I would like to be able to comment as a DM (direct message), to the article author, or to the author of a public comment, or with a groupe visibility. And i love if the privacy policy is powered by asymetric encryption to ensure it will be respected.

> Visibility for blog post may be assumed to be public As default, perhaps, but as the only option, in my opinion, no. I would like to be able to comment as a DM (direct message), to the article author, or to the author of a public comment, or with a groupe visibility. And i love if the privacy policy is powered by asymetric encryption to ensure it will be respected.

trinity-1686a commented

2018-10-18 08:23:16 +00:00

Author

Owner

I would love privacy to be enforced by cryptography, however federation is based on ActivityPub, which to my knowledge does not support non-clear text transactions. We would need to either use another protocol or to extend AP for that to be possible

1000i100 commented

2018-10-18 09:56:50 +00:00

(Migrated from github.com)

AP support text, encrypted text can be stored as text, but yes, if AP can be extended to handle encryption natively, it's better.

trinity-1686a commented

2018-10-18 12:02:33 +00:00

Author

Owner

You can store encrypted text as content, but you will loose mentions (which is how receivers are detected for private messages), or it will end up using nasty tricks to get mentions in plaintext alongside encrypted content. Frankly I don't think Plume is where such protocol improvement should be made first, we don't have a user base big enough to extend AP, this should be made by either Mastodon or Pleroma if we want this to be adopted. There are some long-going discussions about that on Mastodon's issue tracker, mainly https://github.com/tootsuite/mastodon/issues/1093, but judging from the priority level it's in, this don't seems to be an issue which will be solved any time soon

👍 2

No milestone

No project

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Plume/Plume#217

No description provided.

Rows
Columns