Sender | Message | Time |
---|---|---|
9 Dec 2022 | ||
Mark Edworthy | *
JoshFuhs, Anyway, from what I have been seeing over the last year and a half+, I have come to the conclusion that Synapse (ie. the server framework) handles federated Matrix based services in quite a messy way. As an example, back in April / May of last year, I decided to assign the :minds.com address to several :matrix.org rooms and while I was successful for some of the rooms, I couldn't assign the new address to rooms such as the Minds Community Open Source Initiative (MCOSI) public viewable meeting room (which we were mainly using up to April 2020 to host the MCOSI's meetings). Both myself and #MindsGaming spent some time on attempting to resolve this issue, and failed due to (what I presume) was related to the time of creating those rooms (which was in the mid-2018 and early 2019). | 18:34:44 |
Mark Edworthy | *
JoshFuhs, Anyway, from what I have been seeing over the last year and a half+, I have come to the conclusion that Synapse (ie. the server framework) handles federated Matrix based services in quite a messy way. As an example, back in April / May of last year, I decided to assign the :minds.com address to several :matrix.org rooms and while I was successful for some of the rooms, I couldn't assign the new address to rooms such as the Minds Community Open Source Initiative (MCOSI) public viewable meeting room (which we were mainly using up to April 2020 to host the MCOSI's meetings). Both myself and #MindsGaming spent some time on attempting to resolve this issue, and failed due to (what I presume) was related to the time of creating those rooms (which was in the mid-2018 and early 2019). | 18:35:55 |
Mark Edworthy | *
JoshFuhs, Anyway, from what I have been seeing over the last year and a half+, I have come to the conclusion that Synapse (ie. the server framework) handles federated Matrix based services in quite a messy way. As an example, back in April / May of last year, I decided to assign the :minds.com address to several :matrix.org rooms and while I was successful for some of the rooms, I couldn't assign the new address to rooms such as the Minds Community Open Source Initiative (MCOSI) public viewable meeting room (which we were mainly using up to April 2020 to host the MCOSI's meetings). Both myself and #MindsGaming spent some time on attempting to resolve this issue, and failed due to (what I presume) was related to the time of creating those rooms (which was in the mid-2018 and early 2019). | 18:36:40 |
Mark Edworthy | *
JoshFuhs, Anyway, from what I have been seeing over the last year and a half+, I have come to the conclusion that Synapse (ie. the server framework) handles federated Matrix based services in quite a messy way. As an example, back in April / May of last year, I decided to assign the :minds.com address to several :matrix.org rooms and while I was successful for some of the rooms, I couldn't assign the new address to rooms such as the Minds Community Open Source Initiative (MCOSI) public viewable meeting room (which we were mainly using up to April 2020 to host the MCOSI meetings). Both myself and #MindsGaming spent some time on attempting to resolve this issue, and failed due to (what I presume) was related to the time of creating those rooms (which was in the mid-2018 and early 2019). | 19:46:35 |
Mark Edworthy | *
JoshFuhs, Anyway, from what I have been seeing over the last year and a half+, I have come to the conclusion that Synapse (ie. the server framework) handles federated Matrix based services in quite a messy way. As an example, back in April / May of last year, I decided to assign the :minds.com address to several :matrix.org rooms and while I was successful for some of the rooms, I couldn't assign the new addresses to rooms such as the Minds Community Open Source Initiative (MCOSI) public viewable meeting room (which we were mainly using up to April 2020 to host the MCOSI meetings). Both myself and #MindsGaming spent some time on attempting to resolve this issue, and failed due to (what I presume) was related to the time of creating those rooms (which was in the mid-2018 and early 2019). | 19:47:42 |
Mark Edworthy | *
JoshFuhs, Anyway, from what I have been seeing over the last year and a half+, I have come to the conclusion that Synapse (ie. the server framework) handles federated Matrix based services in quite a messy way. As an example, back in April / May of last year, I decided to assign the :minds.com address to several :matrix.org rooms and while I was successful for some of the rooms, I wasn't able to assign the new addresses to rooms such as the Minds Community Open Source Initiative (MCOSI) public viewable meeting room (which we were mainly using up to April 2020 to host the MCOSI meetings). Both myself and #MindsGaming spent some time on attempting to resolve this issue, and failed due to (what I presume) was related to the time of creating those rooms (which was in the mid-2018 and early 2019). | 19:48:03 |
Mark Edworthy | *
JoshFuhs, Anyway, from what I have been seeing over the last year and a half+, I have come to the conclusion that Synapse (ie. the server framework) handles federated Matrix based services in quite a messy way. As an example, back in April / May of last year, I decided to assign the :minds.com address to several :matrix.org rooms and while I was successful for some of the rooms, I wasn't able to assign the new addresses to rooms such as the Minds Community Open Source Initiative (MCOSI) public viewable meeting room (which we were mainly using up to April 2020 to host the MCOSI meetings). Both myself and #MindsGaming spent some time on attempting to resolve this issue, and failed due to (what I presume) was related to the time of creating those rooms (which was in mid-2018 and early 2019). | 19:54:29 |
Mark Edworthy | *
JoshFuhs, Anyway, from what I have been seeing over the last year and a half+, I have come to the conclusion that Synapse (ie. the server framework) handles federated Matrix based services in quite a messy way. As an example, back in April / May of last year, I decided to assign the :minds.com address to several :matrix.org rooms and while I was successful for some of the rooms, I wasn't able to assign the new addresses to rooms such as the Minds Community Open Source Initiative (MCOSI) public viewable meeting room (which we were mainly using up to April 2020 to host the MCOSI meetings). Both myself and #MindsGaming spent some time on attempting to resolve this issue, and failed due to (what I presume) was related to the time of creating those rooms (which was in mid-2018 and early-2019). | 20:11:43 |
10 Dec 2022 | ||
amazingtimes joined the room. | 01:35:56 | |
11 Dec 2022 | ||
ashley19 joined the room. | 10:59:53 | |
Haileyxx joined the room. | 13:39:59 | |
12 Dec 2022 | ||
CarmineBlood joined the room. | 04:09:10 | |
13 Dec 2022 | ||
Robert_M_Mchenry joined the room. | 18:28:03 | |
14 Dec 2022 | ||
bikos_gr joined the room. | 11:07:49 | |
Sophie_Nia joined the room. | 14:32:27 | |
JoshFuhs | Mark Edworthy: thx | 19:25:40 |
dimop | Hello | 19:32:25 |
Mark Edworthy joined the room. | 20:17:49 | |
15 Dec 2022 | ||
@dayana2353:minds.com joined the room. | 01:35:45 | |
@dayana2353:minds.com | Redacted or Malformed Event | 01:39:21 |
Danzilla_White | In reply to @dayana2353:minds.comBegone bot | 01:41:48 |
XxPrettyLittleThingxX banned @dayana2353:minds.com (Irrelevant Content / Spamming ). | 01:44:31 | |
Merrellmarie199999 joined the room. | 14:40:57 | |
DooBetter changed their profile picture. | 16:58:39 | |
Mark Edworthy changed their profile picture. | 17:21:00 | |
Mark Edworthy changed their profile picture. | 18:29:16 | |
16 Dec 2022 | ||
Merrellmarie199999 | Hi | 08:56:05 |
zero0 joined the room. | 10:09:22 | |
22 Dec 2022 | ||
zero0 changed their profile picture. | 12:48:48 | |
zero0 changed their profile picture. | 12:53:05 |