[01:33:01]
<Yunohost Git/Infra notifications> [mastodon_ynh] trendless [commented](https://github.com/YunoHost-Apps/mastodon_ynh/pull/568#issuecomment-4795052091) on [issue #568](https://github.com/YunoHost-Apps/mastodon_ynh/pull/568) Testing: Can confirm ldap works in this package with the latest upstream (4.6.1)
[06:22:49]
<Yunohost Git/Infra notifications> [mastodon_ynh] Thovi98 merged [pull request #569](https://github.com/YunoHost-Apps/mastodon_ynh/pull/569): Upgrade to v4.6.1
[06:22:51]
<Yunohost Git/Infra notifications> [mastodon_ynh] Thovi98 deleted branch ci-auto-update-4.6.1
[08:00:50]
<Yunohost Git/Infra notifications> [penpot_ynh] orhtej2 merged [pull request #210](https://github.com/YunoHost-Apps/penpot_ynh/pull/210): Upgrade to v2.16.1
[08:01:02]
<Yunohost Git/Infra notifications> [penpot_ynh] orhtej2 deleted branch ci-auto-update-2.16.1
[08:01:10]
<Yunohost Git/Infra notifications> [penpot_ynh] orhtej2 opened [pull request #211](https://github.com/YunoHost-Apps/penpot_ynh/pull/211): Testing
[08:01:27]
<Yunohost Git/Infra notifications> [penpot_ynh] orhtej2 merged [pull request #211](https://github.com/YunoHost-Apps/penpot_ynh/pull/211): Testing
[10:55:01]
<m606> ok sorry I didn't know about the Element thing. I'm using Cinny as well with options set to Ultra-Small message spacing and no URL previews, so it's quite packed and readable enough in my opinion (there is still a bit of noise but it's not too disturbing for me). In Cinny, threads don't add much to a message reply (at the point I actually wonder what they are used for - I just thought it was the intended way to do and that there are maybe some advanced feature in it that I have not spotted yet.
[10:59:01]
<m606> The problem I find with simple messages is that several topics are addressed at the same time by one or more people it can be difficult to get which message relates to which topic. Also with threads (like with "replies to message") you can click on the first line and the focus goes to the previous message which can be convenient.
[11:15:56]
<Aleks (he/him/il/lui)> I agree in theory
My experience is, in practice it only works if everybody is disciplined enough to use threads everytime it's needed, and plenty of time (if not the majority of the time), you don't know in advance that one message is gonna trigger a thread, discussions tend to shift topic in an organic fashion, and softwares typically do not allow to rearrange the conversation into a thread a-posteriori ... so in practice, it just becomes an ever bigger mess because some messages are threaded, some are not, some are threaded but only after the 15th message, or a thread starts but then the topic of the discussion shifts inside the thread itself, it's just a mess
[11:20:36]
<Aleks (he/him/il/lui)> We have a Mattermost for $dayjob, their thread system is ok-ish ... at least there's no ambiguity between "replying" and "replying-but-in-a-thread" like there is in Matrix. But even then it's not really game-changer and the fact that it really improves discussion is debatable (as opposed to e.g. creating dedicated channel for specific long-term topics)
[11:21:56]
<m606> I get you. in Cinny there is no big advantage with the thread for a collection of message (AFAIK you cannot filter all messages for a given thread, which would result in the mess you mention if not all related messages are actually marked as being part of the thread). So I guess there is not really the disadvantage either. The link between messages just helps a bit in case of doubt to understand what is the last message the current one is related with.
[15:50:12]
<Yunohost Git/Infra notifications> [synapse_ynh] CodeShakingSheep [commented](https://github.com/YunoHost-Apps/synapse_ynh/pull/628#issuecomment-4801360797) on [issue #628](https://github.com/YunoHost-Apps/synapse_ynh/pull/628) Update PHP to version 8.5: I havent tested SSO on my server but the PHP script is pretty straight forward and I dont see anything in there that c...
[16:08:01]
<Yunohost Git/Infra notifications> [synapse_ynh] Josue-T [commented](https://github.com/YunoHost-Apps/synapse_ynh/pull/628#issuecomment-4801620737) on [issue #628](https://github.com/YunoHost-Apps/synapse_ynh/pull/628) Update PHP to version 8.5: Thanks I know that following the complexity of this script there are no huge risk that something break. But from my ex...
[16:29:48]
<Yunohost Git/Infra notifications> [nextcloud_ynh] rodinux pushed to v33: branch for releases on 32 versions ([7d750d0d](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/7d750d0d43ca8b1b434a0bf76ca1d7cce5a6f9b4))
[16:32:22]
<Yunohost Git/Infra notifications> [nextcloud_ynh] rodinux pushed to v32: version 32.0.12 ([51427cd8](https://github.com/YunoHost-Apps/nextcloud_ynh/commit/51427cd8e564f7c657cee78527328b319102a620))
[17:55:19]
<Yunohost Git/Infra notifications> [my_webapp_ynh] Zenigata opened [issue #171](https://github.com/YunoHost-Apps/my_webapp_ynh/issues/171): Uninstalling my_webapp breaks Jellyfin
[21:24:44]
<Yunohost Git/Infra notifications> [my_webapp_ynh] alexAubin [commented](https://github.com/YunoHost-Apps/my_webapp_ynh/issues/171#issuecomment-4804289346) on [issue #171](https://github.com/YunoHost-Apps/my_webapp_ynh/issues/171) Uninstalling my_webapp breaks Jellyfin: Dont know what happens exactly but this is not strictly speaking my_webapp here. The scripts are just running a regular...
[22:18:55]
<Yunohost Git/Infra notifications> [mastodon_ynh] yunohost-bot opened [pull request #570](https://github.com/YunoHost-Apps/mastodon_ynh/pull/570): Upgrade to v4.6.2
[22:36:34]
<Yunohost Git/Infra notifications> Autoupdater just ran, here are the results:
- 93 pending update PRs
- 15 new apps PRs: ghost, gotosocial, grav, jackett, kresus, liberaforms, mastodon, ntfy, opencloud, seaweedfs, snowflake, tooljet, umami, workout-tracker, zwiicms
- 2 failed apps updates: dmarcguard, loki
See the full log here: https://paste.yunohost.org/raw/mihubegomu
Autoupdate dashboard: https://apps.yunohost.org/dash?filter=autoupdate