Skip to content

Talkyard v0.2025.001
Compare
Choose a tag to compare
@kajmagnus kajmagnus released this 09 Feb 05:20
· 108 commits to main since this release
tyse-v0.2025.001-b8a91e87a-regular
b8a91e8

Changes since tyse-v0.2024.011. Full changelog: tyse-v0.2024.011-1f1c92bc5-regular...tyse-v0.2025.001-b8a91e87a-regular

Features

  • Scrolling up in chats to read older messages. Finally Ty's chat channels start working more "for real", when at last you can scroll up and read old messages (instead of previously only the most recent 50 or so).

Fixes

  • Now talkyardSsoHow = 'RedirPage' (for blog comments Single Sign-On) disables may-compose-before-signup. Previously, this combination made the login popup window appear instead, resulting in a bad blog comments SSO user experience.
  • On the Inspect page, sort groups in the correct order.

Internal

  • Merge the bookmarks branch. (This is the major thing in this release.) But this feature disabled for now.
  • Merge a cache-pages-client-side branch. This disabled too, for now. Quite nice, though, together with bookmarks, since I think that if you use bookmarks, you'll tend to jump back and forth between different bookmarked pages, and then it's annoying if you need to wait 200 ms (or whatever the latency is) for a server roundtrip in between (or at least I think it is).
  • Minor performance improvements, probably mostly not noticeable. E.g. avoiding running React virtual DOM diffs in some cases.

License

Talkyard is licensed under the AGPL (excluding future enterprisey things like SCIM and SAML2). Each specific Talkyard version used to become GPLv2+ after 4 years, but we're changing that to 6 – 7 years. The reason: There's going to be (is the plan) long term stable Talkyard versions, and I want some years between a LTS version going end-of-life, and Talkyard becoming GPLv2+. But only 4 years isn't enough time for some gap year(s) in between.

(Technically this happens by no longer dual-licensing Talkyard under the Business Source License, BUSL — it requires at most 4 years until GPLv2+. Instead, there'll be a GPLv2+ license grant in the README file or in a license file, effective on a date 6 – 7 years into the future, for each specific version.)

Assets 2
Loading