| 26 May 2023 |
|  ╭∩╮( ͡⎚ ʖ̯ ͡⎚)╭∩╮ changed their display name from ㋡₱Ꭵㄩ爪¬_¬ to ╭∩╮( ͡⎚ ʖ̯ ͡⎚)╭∩╮. | 18:20:18 |
 nutomic | djangz: it looks like the html in content field is not properly escaped, but maybe thats just from the logging | 20:00:47 |
| nutomic | anyway this is normally working, are you using an official mastodon version or some fork/dev version? | 20:01:19 |
 djangz | official version | 20:01:36 |
| nutomic | it might also help if you can send the actual id instead of https://masto.qa.example.com/users/mastodon/statuses/110435994705014161 | 20:01:45 |
| djangz | mind if I send as DM? | 20:04:10 |
| djangz | Here is another example post which isn't private https://social.coop/@django/110436799068300163 tagging lemmy.ml | 20:12:17 |
| djangz | perhaps there is a regression, as I remember this working | 20:12:41 |
| nutomic | no problem | 20:20:58 |
| nutomic | i just noticed you are using an older lemmy version, if you upgrade to 0.17.2 it should work | 20:27:57 |
|  xtex changed their display name from xtexChooser to xtex. | 21:21:06 |
| 27 May 2023 |
|  raver_ changed their display name from raver_ to raver. | 00:02:04 |
| raver_ changed their display name from raver to raver_. | 00:02:19 |
|  Agustín Haro changed their display name from Agustín Haro to agustinharo. | 04:53:28 |
| Agustín Haro left the room. | 04:53:28 |
| Agustín Haro joined the room. | 04:53:29 |
|  @helgek:matrix.org left the room. | 06:11:19 |
| raver_ changed their display name from raver_ to raver. | 10:03:24 |
| raver_ changed their display name from raver to raver_. | 10:03:26 |
| raver_ changed their display name from raver_ to raver. | 10:05:35 |
| raver_ changed their display name from raver to raver_. | 10:05:37 |
| raver_ changed their display name from raver_ to raver. | 10:07:09 |
| raver_ changed their display name from raver to raver_. | 10:07:11 |
| raver_ changed their display name from raver_ to raver. | 10:08:47 |
| raver_ changed their display name from raver to raver_. | 10:08:48 |
| Agustín Haro changed their display name from Agustín Haro to agustinharo. | 16:36:01 |
| Agustín Haro left the room. | 16:36:02 |
| Agustín Haro joined the room. | 16:36:02 |
|  futomes joined the room. | 22:30:19 |
| futomes | Hey, I'm trying to configure lemmy to make its postgres connections with SSL and I'm seeing this in the logs on startup (it was working previously without SSL)
-lemmy-1 | 2023-05-27T22:34:58.448478Z INFO lemmy_db_schema::utils: Running Database migrations (This may take a long time)...
-lemmy-1 | 2023-05-27T22:34:58.458792Z INFO lemmy_db_schema::utils: Database migrations complete.
-lemmy-1 | Error: LemmyError { message: None, inner: Error occurred while creating a new object: error performing TLS handshake: no TLS implementation configured, context: SpanTrace [] }
I changed from using lemmy.hjson to configure the connection parameters to specifying them using the LEMMY_DATABASE_URL environment variable (so that I could add ?sslmode=require). The only value left in the database section of lemmy.hjson is pool_size.
Has anyone else gotten this to work or have any ideas? I'm not 100% sure how/if diesel even supports it. | 22:48:01 |
