新增問題

Support for comment visibility #217

已關閉

建立於由 trinity-1686a · 4 則留言

trinity-1686a 已留言

擁有者

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 已留言 (已從 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 已留言

發布者

擁有者

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 已留言 (已從 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 已留言

發布者

擁有者

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

登入才能加入這對話。

未選擇里程碑

沒有負責人

2 參與者

通知

截止日期

截止日期無效或超出範圍，請使用「yyyy-mm-dd」的格式。

未設定截止日期。

先決條件

未設定先決條件。

載入中…

尚未有任何內容

標籤 里程碑

Support for comment visibility #217

標籤里程碑