 | đź“ŁAnnouncements | 32 Members |
| Very important community announcements.. | 6 Servers |
| đź“ŁAnnouncements | 32 Members |
| Very important community announcements.. | 6 Servers |
| Sender | Message | Time |
|---|---|---|
| 15 May 2023 | ||
 u | The room tombstone works from element's room state -> custom event iirc. But the room creation says to use curl and custom json... I've got the authorization for curl figured out at least, but a room creation doesn't seem to work, at least PUT'ing it to 'nerdsin.space/_matrix/client/v3/createRoom' complains M_UNRECOGNIZED | 12:33:35 |
| u | * The room tombstone works from element's room state -> custom event iirc. But the room creation says to use curl and custom json... I've got the authorization for curl figured out at least, but a room creation doesn't seem to work, at least PUT'ing it to 'https:// nerdsin.space /_matrix/client/v3/createRoom' complains M_UNRECOGNIZED | 12:34:08 |
| u | * The room tombstone works from element's room state -> custom event iirc. But the room creation says to use curl and custom json... I've got the authorization for curl figured out at least, but a room creation doesn't seem to work, at least PUT'ing it to 'https:// nerdsin.space /_matrix/client/v3/createRoom' complains M_UNRECOGNIZED (I mangled the url a little with spaces here on purpose, probably don't need every client trying to load it) | 12:35:21 |
| u | * The room tombstone works from element's room state -> custom event iirc. But the room creation says to use curl and custom json... I've got the authorization for curl figured out at least, but a room creation doesn't seem to work, at least PUT'ing it to 'https://nerdsin.space/_matrix/client/v3/createRoom' complains M_UNRECOGNIZED | 12:39:05 |
| u | Actually, just going to the url with a browser, or curl with no headers or data gives the same error, same for trying a different word or createaRoom, so I think I've got the wrong url, even though that one's listed in https://spec.matrix.org/v1.6/client-server-api/#creation | 12:42:24 |
| u | I'm pretty sure nerds is running synapse 1.82, it must support the v1.6 specs... or maybe the data in my json file just isn'' working, and the generic error message is useless | 13:03:21 |
| u | Or know a way to send the room creation from within element? Only custom sends in the devtools seem to be a couple inside a specific room, or send custom account data event (that didn't work) | 13:05:50 |
| u | Redacted or Malformed Event | 14:49:35 |
| u | Anyway, getting things figured out a little more now, using curl's -X PUT wasn't working for creating rooms, while -X POST seems good. And might've had some json comma placements messing things up too. On the right track now, would probably still be a lot easier if element could send the custom create events | 15:34:17 |
 FF777 | u i might be able to help you with what ever you need, but i'm more familiar with the bot API, but i've done room creation before with referencing the old room, and i can do tombstoning too.. and i figured out a way to make the power level higher than 100 in the new room if you want.. i have a test room where the max power level is 1488 hehehe.. | 16:01:35 |
| FF777 | but i'm not sure why you would need to tombstone room first and then edit the tombstone after you create new room.......... it is simpler just to create the new room first, then when you tombstone the original room you reference the old room..... but i haven't experimented with it tons yet.. any way i have to go out for a bit.. | 16:03:45 |
| FF777 | * but i'm not sure why you would need to tombstone room first and then edit the tombstone after you create new room.......... it is simpler just to create the new room first, then when you tombstone the original room you reference the new room..... but i haven't experimented with it tons yet.. any way i have to go out for a bit.. | 16:03:58 |
| u | I think the guide I read thought a continued/upgraded room had to reference the tombstone event from the old room, they even called it circular, but reading more of the matrix docs that doesn’t seem necessary (and a regular upgrade just creates a new room first too) | 17:58:10 |
| u | I did get curl working eventually and tested with some empty rooms. I’m not sure why the new create needs to reference a specific event in the old room, maybe to give a place to jump to when going back to read the old messages? Seemed fine referencing an older message though. | 18:02:54 |
| u | The tombstone looks like element ignores whatever text/message you give it anyway, so that’s fairly basic | 18:09:45 |
| u | If you get crazy power levels, do the “moderator” and “admin” presets & settings still stay at 50 & 100, so it’s just fun having a 999 or 1488 admin? Or the whole scale gets adjusted to whatever you want, and mod becomes 700, admin 1488? Must be in the createRoom event, I’m not sure if it’s editable, so probably stuck with the decision | 18:16:34 |
| FF777 | you set the weird power levels in the create-room event.. the room security tab or what ever is where you set which level is required for certain action.. so, as far as matrix protocol is concerned there really is no "mod" or "admin", it is just "do you have the required power number to do action X?" but by convention of most clients, the clients will show any one that is 50+ as mod and any one that is 100+ as admin..... but it isn't expecting custom levels...... so if you have like 1488 for top-level actions and 777 for some other lower-level things, the client is still just going to show 50+ as mod and 100+ as admin (probably) even though maybe in the custom room power 100 can't even do any thing special.. | 19:02:25 |
| FF777 | but any way, if you need me to figure out how to help you do some thing i can probably do it even though i've been busy lately.. just let me know what you need done.. | 19:02:45 |
| FF777 | i can experiment with tombstoning and creating room if i need to here in a bit.. | 19:03:14 |
| u | That’s ok thanks. I think mimicking the upgrade process should go:
And that’s it? I should be able to manage those ok. The test I tried seemed smooth enough for element (desktop & mobile) And you don’t need to invite any old members to the new room do you? The client should just join automatically (and hide the old room)? | 19:40:31 |
| FF777 | i don't think clients just join the new room automatically..... and i think some clients invite the old members and some don't.. but so when i am upgrading a room i usually do an @ room to ping every one in the old room right before i upgrade the room, because otherwise the old room can sit there with no new messages and users won't realize there is a new room that people are talking in now, and they won't ever check the old room because they don't see any new notifications on it | 19:44:02 |
| u | I probably shouldn’t change the power level max, seems like a lot of clients are barely useable with defaults, and technically it’s someone else’s room (but they ragequit & admin’d a handful of others). But what’s the command for create anyway? | 19:44:54 |
| FF777 | and, when you tombstone a room you aren't really supposed to be able to send messages to it any more, but i think you still actually can but it's just the client doesn't usually let you (i think)... but if you send a message through API/curl then i think you can still send messages to it..... but any way.. i'll try some experiments here in a bit.. | 19:45:12 |
| FF777 | i don't know curl commands, i only know the bot API stuff..... i'm making some internal bot commands to test room creation.. | 19:45:58 |
| u | I don’t think the spec guides had all the details right, that post/put was almost trial & error to figure out, and the url’s seem to use r0 & v3 interchangeably. I did get a 500 server error somehow, didn’t note how though (trying to send a basic message?), but that wasn’t one of the standard errors, maybe a bug even | 19:52:56 |
| FF777 | u okay i tested it....... when you create a new room you can just arbitrarily link to any old room you want, even if it isn't tombstoned....... and i think you provide the "final" event_id to it so that it knows which message to jump to when you click on the "go to old room" link or what ever.. | 20:40:56 |
| FF777 | so yeah, i would recommend creating the new room first (and link to old room in the same atomic step), and then after that is created then you can tombstone the old room.. meaning, there is a short period in there where both rooms are open (before you tombstone the old one) | 20:41:59 |
| FF777 |  Download 2023-05-16 05-42-37.webp | 20:42:56 |
| FF777 | ^ this is some new test room i made....... and like i said, i linked to some still-active room for the "old" room and put in whatever event_id of the "old" room, and so now when i click that ^ blue "view older messages" link on the new room info, it takes me to the """""old"" room, but the old room is just actually some unrelated normal room and it isn't even tombstoned at all | 20:44:26 |
| FF777 | i wish i could tell you which curl commands to use, but i'm not familiar with the curl aspect of it..... i just use the nio APIs and code it in python.. | 20:46:51 |