62 Discourse fixes and opt-in features from JTech Forums

סיכום מבוסס בינה מלאכותית

TripleU from JTech Forums announced a batch of 62 pull requests and opt-in features addressing issues they encountered as admins and users. The proposals aim to enhance Discourse while preserving current defaults, inviting the community to review specific changes via GitHub. Notable contributions include gamification improvements, such as scoring only active likes to prevent points from lingering after unlikes PR #46543, and adding daily caps on reply points and likes to curb score inflation and rapid replying PR #46566, PR #46567, PR #46568).

Additional user experience enhancements include an optional feature to disable likes in specific categories while keeping existing counts intact, code block improvements like synchronized line number gutters PR #46593, explicit language labels even when copy controls are disabled PR #46592, and a selection toolbar button to search for highlighted text PR #46595). The list also includes UI tweaks like external link indicators PR #46594 and better handling of same-origin links to avoid client-side 404s PR #46563.

In response, mcwumbly expressed surprise at the volume of concurrent pull requests. While appreciating direct contributions, he noted that the Discourse team typically encourages discussing ideas on the forum before submitting code to ensure they are a good fit. He highlighted that processing large batches of PRs consumes significant machine time and maintainer attention. Mcwumbly explained that the team needs to determine appropriate

We run JTech Forums on Discourse. These changes come from problems we ran into as forum admins or users. New options preserve the current defaults.

Open a group and then a pull request to see what changes, where it applies, and why we proposed it.

Gamification, likes and badges (11)
PR #46543 · Score only active likes

What — Adds pa.deleted_at IS NULL to DiscourseGamification::LikeReceived and DiscourseGamification::LikeGiven.

Where — The Gamification leaderboard.

Why — Unliking a post can leave leaderboard points behind.

View PR #46543

PR #46566 · Cap reply points

What — Adds a site-wide daily limit on how many eligible replies earn cheers per user.

Where — The bundled Gamification plugin.

Why — An optional daily cap limits points from rapid replying.

View PR #46566

PR #46567 · Cap points from the same liker

What — Adds a daily cap applied separately to each liker and author pair.

Where — The bundled Gamification plugin.

Why — A daily cap limits score inflation between the same two users.

View PR #46567

PR #46568 · Cap points for giving likes

What — Adds a daily limit on how many eligible likes a person can give for cheers.

Where — The bundled Gamification plugin.

Why — A daily cap limits score gains from high-volume liking.

View PR #46568

PR #46576 · Disable likes by category

What — Add a site setting that blocks new likes and reactions in the selected categories while preserving existing counts and the usual undo window.

Where — Like and reaction controls in selected categories.

Why — Sites can turn off new likes in selected categories.

View PR #46576

PR #46577 · Restrict likes by group

What — Add a group allowlist for new likes and reactions. Members who lose access can still remove their existing reactions within the usual undo window.

Where — Site settings and post like permissions.

Why — Sites can limit new likes to trusted or verified groups.

View PR #46577

PR #46578 · Quiet likes by category

What — Add a category list that suppresses new like and reaction notifications and hides corresponding likes from profile activity. Reactions and counts remain available on posts.

Where — Like alerts and profile activity for selected categories.

Why — Members can react without sending alerts in busy categories.

View PR #46578

PR #46579 · Exclude likes from totals

What — Let admins exclude selected categories from user and directory like totals and related trust-level calculations. Existing totals update in the background after settings or category changes.

Where — User totals, the directory, and trust-level calculations.

Why — Off-topic likes can stay on posts without affecting member totals.

View PR #46579

PR #46580 · Automatic trust-level flair

What — Add a setting that displays the highest configured trust level flair for members without a selected flair, using current trust level and group visibility.

Where — Avatars on sites with configured trust-level flair.

Why — Display configured flair when members have chosen none.

View PR #46580

PR #46581 · Configurable badge thresholds

What — Add a list of count overrides for selected seeded badge ladders. The effective grant queries and badge descriptions use the selected counts.

Where — Admin badge settings for built-in badges.

Why — Adjust built-in badge goals through a setting.

View PR #46581

PR #46582 · Configurable Solved thresholds

What — Add a count setting for Guidance Counsellor, Know-it-All, and Solution Institution. Grants and badge descriptions use the selected counts.

Where — Badge settings in the bundled Solved plugin.

Why — Sites can choose targets for the higher Solved badges.

View PR #46582

Notifications and staff tools (11)
PR #46544 · Filter paginated notifications

What — Applies the parsed notification_types filter in the paginated branch too and keeps filter_by_types in load_more_notifications.

Where — The paginated notification history API.

Why — Apply the type filter when loading older notifications.

View PR #46544

PR #46598 · User note creation event

What — Triggers DiscourseEvent.trigger(:user_note_created, record, user, created_by, opts) in DiscourseUserNotes.add_note.

Where — The bundled User Notes plugin.

Why — Plugins can listen for new notes without patching the model.

View PR #46598

PR #46583 · Filter notifications in the UI

What — Add a notification type dropdown that works with the read status filter and keeps the selection when loading more notifications.

Where — The full notification history page.

Why — Find older alerts by type alongside read and unread filters.

View PR #46583

PR #46596 · Alerts for deleted replies

What — Add an optional group list for in-app deletion notifications. Deliver the action and topic to eligible staff who can view the discussion.

Where — Staff notification history for ordinary topic replies.

Why — Notify selected staff who can see the affected topic.

View PR #46596

PR #46584 · PM badge holders

What — An opt-in staff composer picker adds active, distinct badge holders to the current draft while preserving existing recipients and the normal send step.

Where — The staff personal message composer.

Why — Staff can add badge holders to an ordinary PM draft.

View PR #46584

PR #46585 · Staff post-reader report

What — An optional post admin action shows up to 200 signed-in readers with recorded viewing time and their last visit to the topic, restricted to staff who can see the post.

Where — The post action menu on ordinary topics.

Why — Check recorded reads for an ordinary post or announcement.

View PR #46585

PR #46604 · Desktop notification toasts

What — An optional toast displays new unread notifications in the visible desktop tab. People opt in from preferences, and the site sets duration, stack size, and excluded types. Do Not Disturb is respected.

Where — The desktop browser and user notification preferences.

Why — Offer in-page alerts that respect user settings and Do Not Disturb.

View PR #46604

PR #46591 · Dismissible global notices

What — An optional close button remembers the dismissal in the browser for the exact text that was displayed. Changes to the notice show again.

Where — The global notice at the top of the site.

Why — Readers can dismiss a notice and still see the next one.

View PR #46591

PR #46597 · Queued-post outcome alerts

What — Configure separate recipient groups for approval and rejection notices. Only staff with access to the review item receive a notice.

Where — Approvals and rejections in the review queue.

Why — Configure recipients separately for approvals and rejections.

View PR #46597

PR #46599 · User note alerts

What — Configure staff recipient groups in User Notes. The notice links to the user’s profile and is hidden when staff access is lost or User Notes is disabled.

Where — The bundled User Notes plugin and staff notification history.

Why — Notify selected staff about new notes without including note text.

View PR #46599

PR #46600 · Review note alerts

What — Configure a staff recipient group for review notes. The alert links to the item, observes review access and scoped API permissions, and skips recipients who already received an explicit mention.

Where — Notes in the review queue.

Why — Notify eligible reviewers and avoid duplicating mentions.

View PR #46600

Moderation and posting (12)
PR #46569 · TL4 replies in closed topics

What — Adds a site setting that controls whether trust level 4 users can reply in closed topics.

Where — Trust Level 4 reply permissions.

Why — Sites can turn off the TL4 exception for closed replies.

View PR #46569

PR #46570 · TL4 topic reopening

What — Adds a site setting for the reopen permission. The topic menu, direct status updates and topic timers respect it.

Where — The topic status menu and timers for Trust Level 4.

Why — Sites can reserve reopening and reopen timers for staff.

View PR #46570

PR #46571 · Category moderator replies

What — Adds a setting that controls closed-topic replies in the categories a group moderates.

Where — Reply permissions in group-moderated categories.

Why — Choose whether category moderators can reply in closed topics.

View PR #46571

PR #46572 · Category moderator reopening

What — Adds a setting for reopening topics in moderated categories. The menu, status changes and topic timers respect it.

Where — Topic status and timers in group-moderated categories.

Why — Choose whether category moderators can reopen topics.

View PR #46572

PR #46573 · Category moderator topic moves

What — Adds an option to move existing topics into visible categories the group moderates, subject to source edit permissions and destination review requirements.

Where — The topic move dialog for category group moderators.

Why — Allow moves into moderated categories under existing access rules.

View PR #46573

PR #46574 · Category moderator settings

What — Adds an option for a scoped category editor. The server permits only a defined set of general and appearance fields and topic template settings.

Where — Settings of group-moderated categories.

Why — Delegate ordinary settings edits while protecting permissions.

View PR #46574

PR #46575 · Category moderator subcategories

What — Adds a Create subcategory action on eligible parent categories. The child inherits the parent access rules, moderation groups and posting review requirements.

Where — Subcategory creation under group-moderated categories.

Why — Let moderators create children that inherit parent access rules.

View PR #46575

PR #46601 · Approval for replies in one topic

What — Allow moderators to require approval of new replies in a single topic from the topic actions menu. Replies go to the existing review queue and staff can audit changes to the setting.

Where — The topic moderation menu and review queue.

Why — Queue new replies without closing the discussion.

View PR #46601

PR #46602 · Per-user slow mode

What — Let staff set a posting interval and optional expiry on a user’s admin page. The interval applies across category topics and replies, and changes are recorded in the staff action log.

Where — Staff user controls and ordinary topic posting.

Why — Slow down one member without slowing down the entire topic.

View PR #46602

PR #46603 · Category confirmation prompts

What — Category editors can set a plain-text confirmation without changing moderator approval or permissions, with an optional inclusive trust-level cap.

Where — Category settings and the new-topic composer.

Why — Remind authors of category rules before they submit a topic.

View PR #46603

PR #46586 · Topic footer notices

What — An optional staff action adds, edits, or clears a plain-text footer notice visible to users who can already read the topic. Updates appear in the staff log.

Where — The staff action menu and topic footer.

Why — Let staff put instructions near the Reply button.

View PR #46586

PR #46587 · Pin a post to the footer

What — An optional post admin action pins one ordinary post as a copy in the topic footer, with a link to the original. The copy is loaded independently of the post stream and is omitted if the viewer cannot see the post.

Where — The post action menu and topic footer.

Why — Keep a useful answer easy to find at the end of a topic.

View PR #46587

Mobile layout and keyboard access (14)
PR #46549 · Empty profile controls

What — Hides > li:empty in .user-main .about .controls ul, matching .user-card .usercard-controls.

Where — The user profile actions row.

Why — Plugin slots with no content can leave gaps between controls.

View PR #46549

PR #46550 · Empty profile location row

What — Hides the empty row while preserving locations, websites, and content supplied by the plugin outlet.

Where — The user profile header.

Why — Remove blank space when the location and website are both empty.

View PR #46550

PR #46551 · iPad slide-in menus

What — Starts the menu at the lower edge of the bar and reduces the menu height so it fits on screen.

Where — The iPad navigation bar and slide-in menus.

Why — Keep the navigation bar from covering menu rows.

View PR #46551

PR #46552 · Narrow post history dialogs

What — Lets the counter shrink so all four arrows fit inside the footer.

Where — Post revision history dialogs.

Why — Keep revision arrows inside the dialog on small screens.

View PR #46552

PR #46553 · Mobile PM tags

What — Lets the picker wrap below the title and fit within the composer.

Where — The mobile personal message composer.

Why — Let tags wrap below the title to prevent horizontal overflow.

View PR #46553

PR #46554 · Mobile preferences pickers

What — Lets preference fieldsets shrink and caps the picker at the width of its container.

Where — Preferences on narrow screens.

Why — Let narrow forms shrink enough to fit their multiselects.

View PR #46554

PR #46555 · Sidebar keyboard hints

What — Uses the same keyboard capability check as other shortcut hints. The help can appear once keyboard use is detected.

Where — The desktop sidebar.

Why — Wait for keyboard detection before showing shortcut help.

View PR #46555

PR #46556 · Mobile code copy spacing

What — Puts the extra padding on the inline end of the code block, where the button sits.

Where — Code blocks on phones in right-to-left interfaces.

Why — Keep padding beside the copy button in either text direction.

View PR #46556

PR #46557 · Mixed-direction quote borders

What — Uses the quote’s own inline start for its border.

Where — Quotes in posts with mixed text directions.

Why — Put the quote bar on the start side of the quoted text.

View PR #46557

PR #46558 · Full-width printed topics

What — Hides the sidebar and skip links in print and gives the content a single full-width column.

Where — The topic print layout.

Why — Use the page width for posts when printing a topic.

View PR #46558

PR #46559 · Image-link focus outlines

What — Draws the focus outline inside the image when the link receives keyboard focus.

Where — Keyboard navigation on linked post images.

Why — Restore the keyboard focus indicator removed by the lightbox.

View PR #46559

PR #46560 · Topic-map avatar focus

What — Fits each link to its avatar and draws the outline inside the link.

Where — The avatar row in the topic map.

Why — Keep keyboard outlines visible inside the clipped avatar row.

View PR #46560

PR #46561 · Post author focus

What — Keeps the link inside the row, truncates the name, and draws the outline inside the link.

Where — Author names in the header of a post.

Why — Keep long names and their focus outlines inside narrow rows.

View PR #46561

PR #46562 · Sticky header focus

What — Draws both outlines inside their links.

Where — Topic and category links in the sticky header.

Why — Keep focus visible on clipped topic and category links.

View PR #46562

Themes and appearance (5)
PR #46545 · Theme default palette

What — Adds a Theme default choice alongside the named palettes when the picker is visible.

Where — Preferences → Interface → Color schemes.

Why — Show the default choice when the theme limits the palette list.

View PR #46545

PR #46546 · Color preview mode switching

What — Updates link#cs-preview-light and link#cs-preview-dark media attributes when loading a preview and when switching between light, dark, and auto modes.

Where — Preferences → Interface and the light/dark switch.

Why — Keep an old preview from overriding the selected color mode.

View PR #46546

PR #46548 · Disabled period picker caret

What — Hides .angle-icon when this.selectKit.options.disabled is true and uses cursor: default on .period-chooser.is-disabled .period-chooser-header.

Where — The period picker on Gamification leaderboards.

Why — A fixed leaderboard range should look like a fixed range.

View PR #46548

PR #46564 · Small logo on mobile

What — Adds a switch in Appearance → Logo to use the small logo on mobile when no mobile logo is uploaded. Explicit mobile logos take priority.

Where — Admin → Appearance → Logo.

Why — Let sites reuse the small logo when no mobile logo is set.

View PR #46564

PR #46565 · Separate maskable icon

What — Adds an optional maskable icon upload in Appearance → Logo and uses it for the maskable manifest entry.

Where — Admin → Appearance → Logo and the web app manifest.

Why — Let apps use an icon designed for launchers that mask it.

View PR #46565

Reading, search and navigation (9)
PR #46547 · Whispers in AI embeddings

What — Filters topic_truncation and post_truncation to regular, non-hidden posts and skips non-regular posts in Jobs::GenerateEmbeddings.

Where — Discourse AI semantic search.

Why — Keep staff whispers from influencing public semantic search.

View PR #46547

PR #46588 · Clickable desktop topic rows

What — An opt-in opens the topic from noninteractive row space with normal or new-tab gestures, while preserving links, text selection, and bulk actions.

Where — The desktop topic list.

Why — Open from row whitespace while preserving links and controls.

View PR #46588

PR #46589 · Latest reply previews

What — An optional field provides a plain-text preview and author metadata for the latest visible regular reply, with one batch query per list and no extra author query.

Where — Ordinary topic lists and their API payloads.

Why — Let themes show the latest visible reply and its author.

View PR #46589

PR #46590 · Emoji-free excerpts

What — The existing excerpt helpers accept an optional strip_emojis keyword that omits cooked emoji images while preserving other image handling.

Where — The Post.excerpt and PrettyText.excerpt helpers.

Why — Let compact previews omit emoji shortcodes on request.

View PR #46590

PR #46563 · Same-site links outside Discourse

What — The link interceptor leaves URLs with no matching Ember route to the browser. Known client routes and registered rewrites continue through the router.

Where — Same-origin links clicked in Discourse.

Why — Open standalone same-site pages without hitting a client 404.

View PR #46563

PR #46592 · Code language labels

What — An optional label uses the author’s explicit language, even when the code-block copy controls are disabled.

Where — Fenced code blocks in posts.

Why — Show the declared language even when copy controls are off.

View PR #46592

PR #46594 · External-link indicators

What — An optional icon and accessible description mark outbound HTTP links in posts. The site can treat additional exact hostnames as internal.

Where — External links in ordinary posts.

Why — Show when a link leaves the forum and its configured hosts.

View PR #46594

PR #46595 · Search selected text

What — An optional selection toolbar button opens forum search with the selected phrase as a query parameter for users with search access.

Where — The post text selection toolbar.

Why — Search directly from the post toolbar with punctuation intact.

View PR #46595

PR #46593 · Code line numbers

What — A separate, synchronized gutter shows logical line numbers beside code. It follows the code’s scroll position and typography and leaves the code text available for copying.

Where — Multiline code blocks in posts.

Why — Make lines easy to reference without changing copied code.

View PR #46593

Which of these would help your forum? I’d like to hear how you’d use it.

This giant batch of PRs came as a bit of a surprise. It’s great to see folks making direct contributions like this, but in the past, we’ve strongly encouraged discussing things here first, before encouraging people to put effort into things that may not be a great fit.

Our systems aren’t designed for this kind of thing. Pull requests do consume resources, both in terms of machine time and attention.

With the effort bar getting lower, I suppose we need to think about where to introduce some additional helpful friction into the process, without making it too much of a burden for contributors or maintainers.

It’s not something we’ve encountered before, so I’m not coming here with a clear set of guidelines yet (and I’m not really the right person to be establishing them). I’ll let someone on our team who is closer to problem share more of their thoughts on this in when they get a chance.

Some of these may be great, but we’ll need to figure out how best to evaluate that with you.

Just wanted to jump in first and share this first in case you see them get closed or labeled in advance of that and are wondering why.