Support for comment visibility #217
Etichette
Nessuna etichetta
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
Nessun progetto
Nessun assegnatario
2 partecipanti
Notifiche
Scadenza
Nessuna scadenza impostata.
Dipendenze
Nessuna dipendenza impostata.
Riferimento: Plume/Plume#217
Caricamento…
Add table
Crea riferimento in una nuova segnalazione
Descrizione non fornita.
Elimina ramo "%!s()"
L'eliminazione di un ramo è definitiva. Nonostante il ramo eliminato potrebbe continuare ad esistere per un breve periodo di tempo prima di essere realmente eliminato, l'eliminazione NON PUÒ essere annullata in molti casi. Continuare?
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
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
AP support text, encrypted text can be stored as text, but yes, if AP can be extended to handle encryption natively, it's better.
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