Mikaela/mikaela.github.io
1
0
Fork 0
mirror of https://github.com/mikaela/mikaela.github.io/ synced 2024-11-22 03:59:31 +01:00
Code Issues Projects Releases Wiki Activity

pages/matrix: Clarify the text about ghosts and puppets (#346)

Browse Source
This commit is contained in:
Mikko Rasa 2023-12-19 12:34:26 +02:00 committed by GitHub
parent 6bacd17ca4
commit c818e64dfa
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
pages/matrix.markdown
View File

@ -134,11 +134,11 @@ They are implemented by multiple clients other than Element. In FluffyChat, Gomu
### What are ghost and puppets?
They are related to bringing Matrix to other protocols or vice versa.
They are related to bridging Matrix with other protocols.
- A ghost is a Matrix account controlled from another protocol such as IRC or XMPP (the controller being the user there).
- A puppet is the opposite, a Matrix account on another protocol like IRC or XMPP (controlled from Matrix who is the puppetmaster).
- A double-puppet is when you are using both protocols and have connected them to each other such as a message from Discord appears as your real Matrix account and message from Matrixx appears as your real Discord account instead of something virtual only existing due to the bridge.
- A ghost is a virtual user account created by a bridge service to represent a user from another protocol (controlled by the actions of that user). They appear when an entire room is bridged. Some protocols like Discord or Slack have no native support for ghosts but can approximate them by changing the display name and avatar of the messages sent by the bridge.
- A puppet is a real user account controlled by a bridge service (based on their actions on another protocol). They may arise from personal bridging but also from room-level bridging when the target protocol does not support ghosts (such as IRC). Unlike a ghost, it's possible to log in to a puppet account using a normal client application so it's impossible to tell at a glance if the controller is a human or a bridge service (however message contents may provide hints).
- Double puppeting is when a user bridges their real accounts from two protocols so their actions on either side are mirrored on the other.
### What does the public history visibility mean? I don't want to appear in search engines