| 30 Apr 2024 |
 Roelant | Redacted or Malformed Event | 08:00:12 |
| Roelant | [Matthew](https://matrix.to/#/!pcfWjiETvnVuspPLPl:mozilla.org/$f9eQQglcEIFS0njhsJWtr98eUZqBYXcp06-6SHan4iE?via=mozilla.org&via=matrix.org&via=matrix.devinlab.com)
there isn't.
GDPR means that when we deactivate them, we have to delete the PII which could be used to recover them
(and we haven't hooked up a fancy "here's a one-time code that the deactivator can use to undeactivate in future")
| 08:02:50 |
| Roelant | *
Matthew
there isn't.
GDPR means that when we deactivate them, we have to delete the PII which could be used to recover them
(and we haven't hooked up a fancy "here's a one-time code that the deactivator can use to undeactivate in future")
| 08:03:01 |
| Roelant | That's the source for the above, Fallen (thanks to Element desktop that can search a room 😋). | 08:03:32 |
| Roelant | *
Matthew
there isn't.
GDPR means that when we deactivate them, we have to delete the PII which could be used to recover them
(and we haven't hooked up a fancy "here's a one-time code that the deactivator can use to undeactivate in future")
| 08:04:14 |
| Roelant | *
Matthew
there isn't.
GDPR means that when we deactivate them, we have to delete the PII which could be used to recover them
(and we haven't hooked up a fancy "here's a one-time code that the deactivator can use to undeactivate in future")
Original message here: https://matrix.to/#/!pcfWjiETvnVuspPLPl:mozilla.org/$f9eQQglcEIFS0njhsJWtr98eUZqBYXcp06-6SHan4iE?via=mozilla.org&via=matrix.org&via=matrix.devinlab.com
| 08:05:02 |
| Roelant | *
Matthew:
there isn't.
GDPR means that when we deactivate them, we have to delete the PII which could be used to recover them
(and we haven't hooked up a fancy "here's a one-time code that the deactivator can use to undeactivate in future")
Original message here: https://matrix.to/#/!pcfWjiETvnVuspPLPl:mozilla.org/$f9eQQglcEIFS0njhsJWtr98eUZqBYXcp06-6SHan4iE?via=mozilla.org&via=matrix.org&via=matrix.devinlab.com
| 08:06:39 |
 Fallen | I'm aware it doesn't work by default, I was just hoping there is some hack-around. It looks like there are admin API commands to re-activate user accounts, and the admin API users endpoint would allow changing external_ids. This would allow swapping the oidc user ids, and associate a new account's external id with the mxid of the old account.
| 08:11:13 |
| Fallen | I'm not sure how deactivation works (or if it was even deactivated), but this isn't a GDPR case so it might be slightly different. | 08:12:03 |
 rlnt | Ok, yeah, that makes sense.
I don't know if the answer I referenced to was about the technical implementation and/or possibilities, or just the process in general. But given that Matthew is "the" Matthew from Matrix, it's the most authoritative I've seen on the subject here and I assume it at least applies as default for most situations.
And even if you feel GDPR doesn't apply to this situation, it might be how GDPR is implemented in the software (on deactivation, delete x). That's how it read to me. If you run your own server (given your host/handle), you might be able to rollback, restore from a backup, fiddle with the database or do something else in ways that aren't officially supported - idk about that. 🙂 | 08:28:43 |
| Fallen | Yeah, certainly possible that deactivation basically triggers the gdpr workflow. If this is possible via admin api instead of fiddling with the database then it might be a viable try. Who admins the mozilla instance? Is it EMS, or moco folks? | 08:44:21 |
 KaiRo | I think it's all at Element | 10:10:43 |
| KaiRo | and they are working on "native" OIDC support in Matrix/Element (I think there's parts even on the protocol level and parts on the client side) and if/when this server will be switched to that, it may be easier to do all those things | 10:12:13 |
| rlnt | In reply to @fallen:kewis.ch
Yeah, certainly possible that deactivation basically triggers the gdpr workflow. If this is possible via admin api instead of fiddling with the database then it might be a viable try. Who admins the mozilla instance? Is it EMS, or moco folks? If you mean it who runs it in terms of server hosting/administration, than it probably helps to know that it runs mozilla.modular.im (as can be seen on chat.mozilla.org) - and chat.mozilla.org is an DNS CNAME (alias) for mozilla.element.io. In other words, a hosted-by-Element solution. It uses SSO which in turn is actually Okta (auth.mozilla.auth0.com/). Other forms of administration might still be done by Mozilla themselves. | 14:34:03 |
| Fallen | I mean running in terms of who has admin API access and can decide if it would be ok to try this out :) | 15:13:24 |
|  CosminS changed their display name from CosminS to CosminS|sheriffduty. | 17:05:52 |
| rlnt | I really wouldn't be able to say. 🙂 | 17:52:52 |
|  mjf changed their display name from mjf to mjf|bbiab. | 19:07:11 |
 jesup | Nope. "Element", version 1.6.10, per info for the app on my old phone which shows the bar | 19:16:02 |
| jesup | Element - Secure Messenger - New Vector Limited. | 19:17:16 |
| jesup | Version on my new phone is 1.6.14, so a bit newer, but not much | 19:18:55 |
| mjf changed their display name from mjf|bbiab to mjf. | 19:59:01 |
| mjf changed their display name from mjf to mjf|afk. | 22:53:02 |
| 1 May 2024 |
| CosminS changed their display name from CosminS|sheriffduty to CosminS. | 05:05:57 |
| rlnt | And both are Android phones, I assume?
Just checking that, because the versioning numbers are a bit confusing: 1.6.x is the Element X versioning number on iOS (current iOS version being 1.6.3). The "regular" Element is on version 1.11.10 for iOS.
But based on Github, the regular Element Android is actually on version 1.6.14 and Element X is on version 0.4.10 - so that more closely matches your version numbers.
| 11:37:41 |
| rlnt | I suspect for the regular Element client on Android it might be a setting, but iOS doesn't have it (I've found more differences in the past between the versions, such as being able to display a timestamp for every message on Android which iOS lacks).
I'm on iOS so can't help you, the iOS version only has it in Element X. | 11:39:37 |
| mjf changed their display name from mjf|afk to mjf. | 12:44:04 |
|  Kimiblock Moe changed their profile picture. | 13:10:32 |
|  kriswright changed their display name from kriswright | sick to kriswright. | 14:27:10 |
| rlnt changed their display name from Roelant to rlnt. | 15:56:30 |
