Skip to content

Conversation

@Antreesy
Copy link
Contributor

☑️ Resolves

  • Ref discussion from Talk dashboard follow up #15114
    • As mentioned in the issue, skipping lastMessage brings more issues than benefits. A lot of components relies on this data:
      • Dashboard content
      • Message polling logic
      • New messages asterisk
      • Messages processing
    • Server-wide, it doubles request size that is made with 30-sec interval (IMO, modified since should be optimized instead)

🖌️ UI Checklist

🖼️ Screenshots / Screencasts

🏚️ Before 🏡 After
2025-08-20_10h29_36 2025-08-20_10h29_57
16.4 kB transferred for 160 rooms 34.9 kB transferred for 160 rooms

🏁 Checklist

  • 🌏 Tested with different browsers / clients:
    • Chromium (Chrome / Edge / Opera / Brave)
    • Firefox
    • Safari
    • Talk Desktop
    • Integrations with Files sidebar and other apps
    • Not risky to browser differences / client

@Antreesy
Copy link
Contributor Author

/backport to stable31

@Antreesy Antreesy merged commit f3435de into main Aug 20, 2025
53 checks passed
@Antreesy Antreesy deleted the fix/15114/always-fetch-last-message branch August 20, 2025 09:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants