| 8 May 2025 |
|  freedbeats joined the room. | 14:20:31 |
|  morguldir joined the room. | 17:10:43 |
|  vestibule joined the room. | 17:22:09 |
|  rainer joined the room. | 18:05:22 |
|  PiRath joined the room. | 19:16:35 |
|  Jade joined the room. | 19:43:49 |
|  chris joined the room. | 21:44:55 |
|  Aurelia Hüll joined the room. | 22:17:23 |
|  dust joined the room. | 23:04:10 |
| 9 May 2025 |
|  bernhard joined the room. | 09:13:26 |
|  Patrick Asmus joined the room. | 11:56:02 |
| Patrick Asmus | Hello everyone.
I was wondering if, when using this plugin:
https://github.com/maubot/rss/
Whether you can also create a standard template here, which can then be used for all Sebscriptions.
I am specifically interested in the following line:
# Default post notification template for new subscriptions
notification_template: ‘New post in $feed_title: [$title]($link)’
I would have liked to feed several lines with variables here. But every time I try to do this, I get an internal server error.
Does anyone happen to know this? Thank you!
| 11:58:26 |
| Patrick Asmus | * Hello everyone.
I was wondering if, when using this plugin:
https://github.com/maubot/rss/
Whether you can also create a standard template here, which can then be used for all Subscriptions.
I am specifically interested in the following line:
# Default post notification template for new subscriptions
notification_template: ‘New post in $feed_title: [$title]($link)’
I would have liked to feed several lines with variables here. But every time I try to do this, I get an internal server error.
Does anyone happen to know this? Thank you!
| 11:58:46 |
 tulir | that only applies to new subscriptions, not existing ones | 12:00:57 |
| tulir | anyway if you use valid yaml syntax it should work | 12:01:07 |
| tulir | if you use invalid syntax it won't work | 12:01:22 |
| Patrick Asmus | The only important thing for me is to know that it actually works if you customise it. That means, if I customise this line for myself, then I subscribe to RSS feeds and then it should probably work? | 12:02:25 |
| Patrick Asmus | Okay, thank you very much :) | 12:02:41 |
|  Sucre15 joined the room. | 16:16:35 |
| Sucre15 left the room. | 16:19:26 |
 wreck | question about the mbc auth command... it supports SSO flows, but do those flows follow a legacy implementation that assumes generated tokens will live forever, or is it smart enough to renew tokens and all that jazz? | 16:44:17 |
| tulir | generated tokens do live forever | 16:44:28 |
| wreck | even if MAS is in use on the homeserver in question? | 16:53:57 |
| wreck | sorry, i forgot to add that part to my initial question... that's what kicked off this whole thought process | 16:54:26 |
| tulir | of course | 16:54:53 |
| wreck | cool cool | 16:55:16 |
| tulir | wouldn't be very backwards compatible if you could only log into old clients for 5 minutes | 16:55:18 |
| wreck | well yeah, i just know that sso native behavior is new on the scene so i wasn't sure how compliant all this stuff is. i mean i just tried to log into extera the other day and it just... doesn't work for my homeserver, because i don't have password-auth enabled in my mas deployment. | 16:56:43 |
| wreck | that's obviously unrelated, but an ecosystem of many disparate projects means lots of inconsistent levels of compliance | 16:57:37 |
| wreck | Redacted or Malformed Event | 16:59:33 |
