{"latest_posts":[{"id":2034587,"name":"","username":"Don","avatar_template":"/user_avatar/meta.discourse.org/don/{size}/228726_2.png","created_at":"2026-09-06T18:54:18.814Z","cooked":"

감사합니다 @Stephane_Roy! 수정 내용은 다음과 같습니다: FIX: post-voting topics crashing the topic preview modal · VaperinaDEV/discourse-topic-preview-modal@0be328e · GitHub

","post_number":74,"post_type":1,"posts_count":74,"updated_at":"2026-09-06T18:54:18.814Z","reply_count":0,"reply_to_post_number":73,"quote_count":0,"incoming_link_count":1,"reads":4,"readers_count":3,"score":5.6,"yours":false,"topic_id":409712,"topic_slug":"topic-preview-modal","topic_title":"토픽 미리보기 모달","topic_html_title":"토픽 미리보기 모달","category_id":120,"display_username":"","primary_group_name":"VolunteerMods","flair_name":"VolunteerMods","flair_url":"https://global.discourse-cdn.com/meta/original/4X/2/7/d/27de051915b8a604d176484cd260d10cfc956d42.svg","flair_bg_color":"","flair_color":"","flair_group_id":276,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Leader","title_is_group":false,"reply_to_user":{"id":98294,"username":"Stephane_Roy","name":"Stephane Roy","avatar_template":"/user_avatar/meta.discourse.org/stephane_roy/{size}/222598_2.png"},"bookmarked":false,"raw":"Thank you @Stephane_Roy! Here is the fix: https://github.com/VaperinaDEV/discourse-topic-preview-modal/commit/0be328ef1d0697032a1306341735efacc51d116d","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"group_moderator":true,"user_id":78445,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"감사합니다 @Stephane_Roy! 수정 내용은 다음과 같습니다: FIX: post-voting topics crashing the topic preview modal · VaperinaDEV/discourse-topic-preview-modal@0be328e · GitHub","truncated":true,"post_url":"/t/topic-preview-modal/409712/74","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034579,"name":"","username":"twofoursixeight","avatar_template":"/user_avatar/meta.discourse.org/twofoursixeight/{size}/574822_2.png","created_at":"2026-09-06T17:29:34.794Z","cooked":"

보통 등록한 상태에서는 이 페이지에 접근하지 못하도록 되어 있습니다. 하지만 게시물에 있는 링크를 클릭하면 접근할 수 있습니다. 보통 이 두 페이지를 클릭하면 홈 페이지로 되돌려집니다.

\n

이 버그를 재현하는 방법:

\n
    \n
  1. 포럼에서 /signup 또는 /login 링크가 포함된 게시물을 찾거나 작성합니다.
    2. \n
  2. 계정 상태에서도 이 링크 중 하나를 클릭하면 가입 또는 로그인 페이지로 이동합니다.
    3. \n
  3. 이 상태에서 계정을 만들려고 하면 아무 반응이 없어 보이지만, 아래 이미지와 같은 이메일이 전송됩니다.
    \n
    \"image\"
    image901×486 23.7 KB
    4. \n
  4. 이 상태에서 계정에 로그인하려고 하면 아무 반응이 없어 보이지만, 새로고침을 하자마자 다른 계정으로 로그인됩니다.
    5. \n
\n

동영상:

\n

\n

\n동영상 1: 로그인 페이지
\n
\n

\n동영상 2: 가입 페이지

","post_number":1,"post_type":1,"posts_count":1,"updated_at":"2026-09-06T17:31:09.607Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":2,"reads":10,"readers_count":9,"score":27.0,"yours":false,"topic_id":411756,"topic_slug":"you-can-open-the-sign-up-and-login-pages-on-discourse-forums-by-clicking-them-in-a-post-despite-being-a-registered-user","topic_title":"회원가입 및 로그인 페이지를 게시글에서 클릭하면 등록된 회원이라도 열립니다","topic_html_title":"회원가입 및 로그인 페이지를 게시글에서 클릭하면 등록된 회원이라도 열립니다","category_id":1,"display_username":"","primary_group_name":null,"flair_name":"theme_creator","flair_url":"palette","flair_bg_color":"ddd","flair_color":"111","flair_group_id":84,"badges_granted":[],"version":2,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Ghostwriter","title_is_group":false,"bookmarked":false,"raw":"Normally, you are not supposed to access these pages when registered. However you can when you click the link a post. Normally both pages kick you back to the home page when you click them.\n\nHow to reproduce this bug:\n1. Find or make a post on the forum that has either a /signup or a /login link.\n2. Clicking either of those will take you to the signup or login page even with an account.\n3. If you try to make an account in this state, nothing seems to happen, but it sends an email like the image below.\n![image|690x372](upload://wrQd4bGGJku5wNF9ZWKElH1n85o.png)\n4. If you try to log in to an account in this state, nothing seems to happen, but as soon as you refresh, the account logs you in to a different account.\n\n\nVideos:\n\n![2026-09-06 10-11-36|video](upload://7DP3M2cHYLDjZpntBfw7AgIWlUj.mp4)\nVideo 1: The login page\n![2026-09-06 10-28-42|video](upload://z5VNtatrWBs9WZkwwxJZlxnffJm.mp4)\nVideo 2: The signup page","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":120090,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"보통 등록한 상태에서는 이 페이지에 접근하지 못하도록 되어 있습니다. 하지만 게시물에 있는 링크를 클릭하면 접근할 수 있습니다. 보통 이 두 페이지를 클릭하면 홈 페이지로 되돌려집니다. \n이 버그를 재현하는 방법: \n\n포럼에서 /signup 또는 /login 링크가 포함된 게시물을 찾거나 작성합니다.\n계정 상태에서도 이 링크 중 하나를 클릭하면 가입 또는 로그인 페이지로 이동합니다.\n이 상태에서 계정을 만들려고 하면 아무 반응이 없어 보이지만, 아래 이미지와 같은 이메일이 전송됩니다. \n[image]\n이 상태에서 계정에 로그인하려고…","truncated":true,"post_url":"/t/you-can-open-the-sign-up-and-login-pages-on-discourse-forums-by-clicking-them-in-a-post-despite-being-a-registered-user/411756/1","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"calendar_details":[],"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null,"can_vote":false},{"id":2034578,"name":"","username":"ducks","avatar_template":"/user_avatar/meta.discourse.org/ducks/{size}/518975_2.png","created_at":"2026-09-06T17:29:00.899Z","cooked":"

훌륭한 제안입니다. 이 문제를 수정해야 할 PR입니다.

\n

https://github.com/discourse/discourse/pull/43338

","post_number":3,"post_type":1,"posts_count":3,"updated_at":"2026-09-06T17:29:00.899Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":7,"readers_count":6,"score":36.4,"yours":false,"topic_id":411753,"topic_slug":"optimize-the-selection-of-the-month-for-an-event","topic_title":"이벤트용 월 선택 최적화","topic_html_title":"이벤트용 월 선택 최적화","category_id":2,"display_username":"","primary_group_name":"team","flair_name":"team","flair_url":"https://global.discourse-cdn.com/meta/original/3X/e/b/ebee30bd98aef20357e4a177a5a1e45b877ce088.svg","flair_bg_color":"","flair_color":"111","flair_group_id":47,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"team","title_is_group":true,"bookmarked":false,"raw":"great suggestion. PR here that should fix this.\n\nhttps://github.com/discourse/discourse/pull/43338","actions_summary":[{"id":2,"count":2}],"moderator":false,"admin":true,"staff":true,"user_id":176466,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"훌륭한 제안입니다. 이 문제를 수정해야 할 PR입니다. \nhttps://github.com/discourse/discourse/pull/43338","truncated":true,"post_url":"/t/optimize-the-selection-of-the-month-for-an-event/411753/3","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":2}],"current_user_reaction":null,"reaction_users_count":2,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034577,"name":"Stephane Roy","username":"Stephane_Roy","avatar_template":"/user_avatar/meta.discourse.org/stephane_roy/{size}/222598_2.png","created_at":"2026-09-06T17:04:08.642Z","cooked":"

안녕하세요,

\n

테마의 플로팅 버튼에서 텍스트 표시 문제가 발생하고 있습니다. “New topic” 텍스트가 표시되지 않습니다.

\n

\"image\"
image1121×431 47.1 KB

\n

이 문제는 “Customize new topic button text” 테마 구성 요소를 사용하여 “create topic” 버튼의 기본 텍스트를 사용자 지정한 카테고리에서만 발생합니다.

\n

예를 들어 이 카테고리에서 문제가 발생합니다:

\n\n

도와주셔서 감사합니다. 정말 멋진 테마네요 \":heart_eyes:\"

","post_number":420,"post_type":1,"posts_count":9,"updated_at":"2026-09-06T17:04:08.642Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":7,"readers_count":6,"score":6.4,"yours":false,"topic_id":47142,"topic_slug":"material-design-theme","topic_title":"Material Design Theme","topic_html_title":"Material Design Theme","category_id":61,"display_username":"Stephane Roy","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"Hello,\n\nI’m encountering a text display issue with the theme's floating button: \"New topic\" isn't showing up.\n\n![image|690x265](upload://adDNV1HfB0IJAdnaTilaaMrO9uX.png)\n\n\nThis problem only occurs in categories where I’ve customized the default text for the \"create topic\" button using the \"[Customize new topic button text](https://meta.discourse.org/t/customize-new-topic-button-text/269086)\" theme component.\n\nFor exemple in this category : \nhttps://forums.ffjdr.org/c/e-irl/14\n\n\n\nThanks for your help and for this wonderful theme :heart_eyes:","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":98294,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"안녕하세요, \n테마의 플로팅 버튼에서 텍스트 표시 문제가 발생하고 있습니다. “New topic” 텍스트가 표시되지 않습니다. \n [image] \n이 문제는 “Customize new topic button text” 테마 구성 요소를 사용하여 “create topic” 버튼의 기본 텍스트를 사용자 지정한 카테고리에서만 발생합니다. \n예를 들어 이 카테고리에서 문제가 발생합니다: \n\n도와주셔서 감사합니다. 정말 멋진 테마네요 :heart_eyes:","truncated":true,"post_url":"/t/material-design-theme/47142/420","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034575,"name":"Stephane Roy","username":"Stephane_Roy","avatar_template":"/user_avatar/meta.discourse.org/stephane_roy/{size}/222598_2.png","created_at":"2026-09-06T16:53:47.271Z","cooked":"

안녕하세요,

\n

“Events” 카테고리에서 두 가지 유형의 Discourse 템플릿 모두에서 버그를 겪고 있습니다.

\n\n

이 문제는 Form Templates와 Events가 모두 아직 개발 중이기 때문에 발생하는 것으로 추정됩니다 \":face_blowing_a_kiss:\"

\n
","post_number":632,"post_type":1,"posts_count":170,"updated_at":"2026-09-06T16:53:47.271Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":5,"readers_count":4,"score":1.0,"yours":false,"topic_id":97376,"topic_slug":"discourse-events","topic_title":"Discourse Events","topic_html_title":"Discourse Events","category_id":22,"display_username":"Stephane Roy","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"Hello,\n\nI’m encountering bugs with both types of Discourse templates in an \"Events\" category.\n\n- With the category template: it doesn't appear below the event in the composer.\n\n- With the form template:\nIt replaces the event that is normally created automatically in the composer.\nAlso, there is no \"Event\" type available in the form template elements.\n\nI assume the issue is likely caused by the fact that both Form Templates and Events are still under development :face_blowing_a_kiss:\n```","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":98294,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"안녕하세요, \n“Events” 카테고리에서 두 가지 유형의 Discourse 템플릿 모두에서 버그를 겪고 있습니다. \n\n\n카테고리 템플릿의 경우: 작성기(composer)에서 이벤트 아래에 표시되지 않습니다. \n\n\n폼 템플릿의 경우: \n작성기에서 자동으로 생성되는 이벤트를 대체합니다. \n또한, 폼 템플릿 요소에서 “Event” 유형을 사용할 수 없습니다. \n\n\n이 문제는 Form Templates와 Events가 모두 아직 개발 중이기 때문에 발생하는 것으로 추정됩니다 :face_blowing_a_kiss:","truncated":true,"post_url":"/t/discourse-events/97376/632","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034574,"name":"","username":"satonotdead","avatar_template":"/user_avatar/meta.discourse.org/satonotdead/{size}/447830_2.png","created_at":"2026-09-06T16:51:15.144Z","cooked":"

이벤트 뷰의 재구성 및 재편성에 동의합니다. 선택기를 비활성화하고 월간 이벤트 표시만 유지하여, 나머지 기능을 제거하면서 사용자에게 단순한 UI/UX를 제공했습니다.

","post_number":2,"post_type":1,"posts_count":3,"updated_at":"2026-09-06T16:51:15.144Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":7,"readers_count":6,"score":21.4,"yours":false,"topic_id":411753,"topic_slug":"optimize-the-selection-of-the-month-for-an-event","topic_title":"이벤트용 월 선택 최적화","topic_html_title":"이벤트용 월 선택 최적화","category_id":2,"display_username":"","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","bookmarked":false,"raw":"I agree with a restructure and reorganization of these event views. I just disabled the selector and let the monthly event display to give a simple UI/UX to users while dropping the rest.","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":71041,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"이벤트 뷰의 재구성 및 재편성에 동의합니다. 선택기를 비활성화하고 월간 이벤트 표시만 유지하여, 나머지 기능을 제거하면서 사용자에게 단순한 UI/UX를 제공했습니다.","truncated":true,"post_url":"/t/optimize-the-selection-of-the-month-for-an-event/411753/2","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034573,"name":"Stephane Roy","username":"Stephane_Roy","avatar_template":"/user_avatar/meta.discourse.org/stephane_roy/{size}/222598_2.png","created_at":"2026-09-06T16:32:26.867Z","cooked":"

안녕하세요,

\n

관리자가 특정 카테고리에 대해 사용 가능한 필드를 구성하거나 기본 설정을 지정할 수 있을까요?

\n

예를 들어:

\n

위치 필드를 제거하거나 필수로 설정하는 것.

\n

리마인더의 시간 범위를 설정하는 것.

\n

이벤트 필드를 켜거나 끌 수 있거나(또는 필수로 지정할 수 있다면), 이벤트 기능을 매우 높은 수준으로 커스터마이징할 수 있을 것입니다.

\n

이벤트 기능에 대한 모든 작업에 감사드립니다! \":slight_smile:\"

","post_number":1,"post_type":1,"posts_count":1,"updated_at":"2026-09-06T16:32:26.867Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":2,"reads":6,"readers_count":5,"score":26.2,"yours":false,"topic_id":411755,"topic_slug":"make-event-fields-disabled-or-mandatory","topic_title":"이벤트 필드를 비활성화하거나 필수로 설정하기","topic_html_title":"이벤트 필드를 비활성화하거나 필수로 설정하기","category_id":2,"display_username":"Stephane Roy","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"Hello,\n\nWould it be possible for the administrator to configure the available fields—or set defaults configurations—for a specific category ?\n\n\nFor example:\n\nTo remove or mandate the location field.\n\nTo set the timeframe for reminders.\n\nIf event fields could be toggled on or off (or made mandatory), it would allow for a high level of customization of the Events feature.\n\n\n \nThanks for all the work on Events! :-)","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":98294,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"안녕하세요, \n관리자가 특정 카테고리에 대해 사용 가능한 필드를 구성하거나 기본 설정을 지정할 수 있을까요? \n예를 들어: \n위치 필드를 제거하거나 필수로 설정하는 것. \n리마인더의 시간 범위를 설정하는 것. \n이벤트 필드를 켜거나 끌 수 있거나(또는 필수로 지정할 수 있다면), 이벤트 기능을 매우 높은 수준으로 커스터마이징할 수 있을 것입니다. \n이벤트 기능에 대한 모든 작업에 감사드립니다! :slight_smile:","truncated":true,"post_url":"/t/make-event-fields-disabled-or-mandatory/411755/1","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"calendar_details":[],"reactions":[{"id":"eyes","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null,"can_vote":true},{"id":2034570,"name":"Stephane Roy","username":"Stephane_Roy","avatar_template":"/user_avatar/meta.discourse.org/stephane_roy/{size}/222598_2.png","created_at":"2026-09-06T16:19:09.174Z","cooked":"

안녕하세요,

\n

이 시나리오에 대한 사용성 개선 사항을 제안드리고자 합니다.

\n

컴포저를 사용하여 2일짜리 이벤트를 생성할 때,

\n

시작 날짜가 몇 달 후라면—

\n

예를 들어 2027년 7월 14일—

\n

날짜 선택기가 자동으로 7월로 설정되도록 할 수 있을까요?

\n

이렇게 하면 사용자가 날짜 선택기에서 월을 넘겨보며 찾을 필요가 없어집니다.

\n

감사합니다.

","post_number":1,"post_type":1,"posts_count":3,"updated_at":"2026-09-06T16:19:09.174Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":2,"reads":9,"readers_count":8,"score":86.8,"yours":false,"topic_id":411753,"topic_slug":"optimize-the-selection-of-the-month-for-an-event","topic_title":"이벤트용 월 선택 최적화","topic_html_title":"이벤트용 월 선택 최적화","category_id":2,"display_username":"Stephane Roy","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"Hello,\n\nI’d like to suggest a usability improvement for this scenario:\n\nWhen creating a 2-day event using the composer,\n\nif the start date is several months away—\n\nfor example, July 14, 2027—\n\nwould it be possible for the date picker to automatically default to the month of July?\n\nThis would save the user from having to scroll through the months in the picker.\n\nThanks.","actions_summary":[{"id":2,"count":3}],"moderator":false,"admin":false,"staff":false,"user_id":98294,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"안녕하세요, \n이 시나리오에 대한 사용성 개선 사항을 제안드리고자 합니다. \n컴포저를 사용하여 2일짜리 이벤트를 생성할 때, \n시작 날짜가 몇 달 후라면— \n예를 들어 2027년 7월 14일— \n날짜 선택기가 자동으로 7월로 설정되도록 할 수 있을까요? \n이렇게 하면 사용자가 날짜 선택기에서 월을 넘겨보며 찾을 필요가 없어집니다. \n감사합니다.","truncated":true,"post_url":"/t/optimize-the-selection-of-the-month-for-an-event/411753/1","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"calendar_details":[],"reactions":[{"id":"heart","type":"emoji","count":2},{"id":"eyes","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":3,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null,"can_vote":true},{"id":2034567,"name":"Ethan ","username":"Ethsim2","avatar_template":"/user_avatar/meta.discourse.org/ethsim2/{size}/522255_2.png","created_at":"2026-09-06T15:52:22.609Z","cooked":"

이 PR이 카테고리별 설정의 이벤트 시작일 기준으로 주제 정렬 옵션에 영향을 미치는지 확인하는 것도 가치가 있을 수 있습니다:

\n\n\n

해당 PR은 카테고리 정렬을 위해 특별히 작성된 것은 아니지만, 업데이트된 이벤트 날짜가 기존 주제 모델에 어떻게 전파되는지를 변경하고, 반복 이벤트가 다음 발생 시점으로 넘어갈 때 최신 주제 업데이트를 발행합니다.

\n

이벤트 시작일 기준으로 주제 정렬 기능을 사용 중인 사용자들이 이벤트 날짜가 변경될 때 주제가 올바르게 업데이트/재정렬되지 않는 문제를 목격했다면, PR 헤드(최신 커밋) 기준으로 해당 문제가 여전히 재현되는지 알려주시면 유용할 것입니다.

","post_number":631,"post_type":1,"posts_count":170,"updated_at":"2026-09-06T15:52:22.609Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":8,"readers_count":7,"score":16.6,"yours":false,"topic_id":97376,"topic_slug":"discourse-events","topic_title":"Discourse Events","topic_html_title":"Discourse Events","category_id":22,"display_username":"Ethan ","primary_group_name":null,"flair_name":"theme_authors","flair_url":"paintbrush","flair_bg_color":"ddd","flair_color":"111","flair_group_id":73,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Tester","title_is_group":false,"bookmarked":false,"raw":"It may also be worth checking whether this PR has any effect on the **Sort topics by event start date** option in the per-category settings:\n\nhttps://github.com/discourse/discourse/pull/43285\n\nThe PR wasn’t written specifically for category sorting, but it does change how updated event dates are propagated to existing topic models, and publishes a latest-topic update when a recurring event advances to its next occurrence.\n\nIf anyone using **Sort topics by event start date** has seen topics fail to update/re-sort correctly as event dates change, it would be useful to know whether that still reproduces against the PR head.","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":160471,"hidden":false,"trust_level":1,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"이 PR이 카테고리별 설정의 이벤트 시작일 기준으로 주제 정렬 옵션에 영향을 미치는지 확인하는 것도 가치가 있을 수 있습니다: \n\n\n해당 PR은 카테고리 정렬을 위해 특별히 작성된 것은 아니지만, 업데이트된 이벤트 날짜가 기존 주제 모델에 어떻게 전파되는지를 변경하고, 반복 이벤트가 다음 발생 시점으로 넘어갈 때 최신 주제 업데이트를 발행합니다. \n이벤트 시작일 기준으로 주제 정렬 기능을 사용 중인 사용자들이 이벤트 날짜가 변경될 때 주제가 올바르게 업데이트/재정렬되지 않는 문제를 목격했다면, PR 헤드(최신 커밋) 기준으로 해당 …","truncated":true,"post_url":"/t/discourse-events/97376/631","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034566,"name":"Stephane Roy","username":"Stephane_Roy","avatar_template":"/user_avatar/meta.discourse.org/stephane_roy/{size}/222598_2.png","created_at":"2026-09-06T15:25:26.336Z","cooked":"

안녕하세요,

\n

다양한 기능이 추가되어 사용하게 되었습니다… 감사합니다!

\n

다음 시나리오에서 버그를 발견했습니다:

\n

예를 들어 2일간 지속되는 이벤트를 생각해 보세요.

\n

이벤트가 이벤트 시작일 기준으로 정렬된 토픽 목록 상단에서 너무 일찍 사라집니다.
\n이벤트의 첫날이 시작되는 순간 바로 사라집니다.

\n

이벤트가 끝날 때까지 유지되어야 하지 않을까요?

\n

그리고 토픽 제목 옆에 상태가 단순히 \"진행 중\"으로 변경되어야 하지 않을까요?

\n

감사합니다.

","post_number":630,"post_type":1,"posts_count":170,"updated_at":"2026-09-06T15:25:26.336Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":9,"readers_count":8,"score":21.8,"yours":false,"topic_id":97376,"topic_slug":"discourse-events","topic_title":"Discourse Events","topic_html_title":"Discourse Events","category_id":22,"display_username":"Stephane Roy","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"Hello,\n\nThe addition of numerous features convinced me to use it... thanks!\n\nI've run into a bug in this scenario:\n\nTake an event that lasts, for example, 2 days.\n\nThe event disappears from the top of the topic list (sorted by event start date) too early.\nIt vanishes right at the start of the event's first day.\n\nShouldn't it disappear only when the event ends?\n\nAnd shouldn't its status simply change to \"in progress\" next to the topic title?\n\nThanks.","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":98294,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"안녕하세요, \n다양한 기능이 추가되어 사용하게 되었습니다… 감사합니다! \n다음 시나리오에서 버그를 발견했습니다: \n예를 들어 2일간 지속되는 이벤트를 생각해 보세요. \n이벤트가 이벤트 시작일 기준으로 정렬된 토픽 목록 상단에서 너무 일찍 사라집니다. \n이벤트의 첫날이 시작되는 순간 바로 사라집니다. \n이벤트가 끝날 때까지 유지되어야 하지 않을까요? \n그리고 토픽 제목 옆에 상태가 단순히 "진행 중"으로 변경되어야 하지 않을까요? \n감사합니다.","truncated":true,"post_url":"/t/discourse-events/97376/630","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034564,"name":"","username":"satonotdead","avatar_template":"/user_avatar/meta.discourse.org/satonotdead/{size}/447830_2.png","created_at":"2026-09-06T14:59:59.203Z","cooked":"

Discourse AI에서 프롬프트/에이전트를 설계하고 구조화한 후, 현재 ask.discourse.com에서 확인되는 대화형 채팅에 현재 글로벌 표준으로 자리 잡은 기능들을 업데이트할 좋은 시점이라고 생각합니다.

\n

아래 목록은 포괄적이지는 않지만, 가장 가치 있고 유용한 사용 사례를 다루고 있습니다:

\n\n

현재 AI 채팅 패널은 이러한 기능을 지원하지 않으며, 해당 패널에 제공되는 정보를 검색하거나 찾는 데 어려움을 겪고 있습니다.

","post_number":1,"post_type":1,"posts_count":1,"updated_at":"2026-09-06T14:59:59.203Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":4,"reads":12,"readers_count":11,"score":22.4,"yours":false,"topic_id":411751,"topic_slug":"add-groups-rename-and-remove-to-ai-conversations","topic_title":"AI 대화에 그룹 추가, 이름 변경 및 삭제 기능 추가","topic_html_title":"AI 대화에 그룹 추가, 이름 변경 및 삭제 기능 추가","category_id":2,"display_username":"","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","bookmarked":false,"raw":"After designing and structuring my prompts/agents in Discourse AI, I think it's a good time to update the conversation chat (the same one we see on ask.discourse.com) with functionalities that are currently the global standard.\n\nThe list is not exhaustive, although it covers the most valued and useful use cases:\n\n- **Ability to rename chats:** allows finding them based on personal conventions.\n- **Ability to generate and organize groups:** allows defining organization parameters according to different agents/functions.\n- **Ability to delete chats:** I think this is indispensable to respect user privacy.\n\nCurrently, the AI chat panel does not allow any of these functions, and I am having trouble searching for/finding the information that is provided there.","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":71041,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Discourse AI에서 프롬프트/에이전트를 설계하고 구조화한 후, 현재 ask.discourse.com에서 확인되는 대화형 채팅에 현재 글로벌 표준으로 자리 잡은 기능들을 업데이트할 좋은 시점이라고 생각합니다. \n아래 목록은 포괄적이지는 않지만, 가장 가치 있고 유용한 사용 사례를 다루고 있습니다: \n\n채팅 이름 변경 기능: 개인적인 관례에 따라 채팅을 쉽게 찾을 수 있도록 합니다.\n그룹 생성 및 조직화 기능: 다양한 에이전트/기능에 따라 조직화 매개변수를 정의할 수 있도록 합니다.\n채팅 삭제 기능: 사용자 프라이버시를 존중하기…","truncated":true,"post_url":"/t/add-groups-rename-and-remove-to-ai-conversations/411751/1","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"calendar_details":[],"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null,"can_vote":true},{"id":2034563,"name":"Stephane Roy","username":"Stephane_Roy","avatar_template":"/user_avatar/meta.discourse.org/stephane_roy/{size}/222598_2.png","created_at":"2026-09-06T14:57:06.086Z","cooked":"

안녕하세요,

\n

와, 이 컴포넌트는 정말 멋지고 특히 스마트폰에서 뛰어난 사용성을 제공하는 것 같습니다!

\n

막히는 버그를 발견했습니다:

\n

\"Post Voting 플러그인\"이 적용된 토픽에서 모달이 로드되지 않습니다.

\n

이 문제는 스마트폰과 PC 모두에서 발생합니다.
\n최신 버전에서도 동일한 현상이 나타납니다.

\n

필요하시면 제 포럼에서 해당 컴포넌트를 다시 활성화하고 버그 링크를 DM으로 보내드리겠습니다.

\n

감사합니다.

","post_number":73,"post_type":1,"posts_count":74,"updated_at":"2026-09-06T14:57:26.036Z","reply_count":1,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":8,"readers_count":7,"score":36.6,"yours":false,"topic_id":409712,"topic_slug":"topic-preview-modal","topic_title":"토픽 미리보기 모달","topic_html_title":"토픽 미리보기 모달","category_id":120,"display_username":"Stephane Roy","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"Hello,\n\nWow, this component looks great and offers excellent usability, especially on smartphones!\n\nI’ve run into a blocking bug:\n\nOn a topic using the \"[Post Voting plugin](https://meta.discourse.org/t/discourse-post-voting/227808)\", the modal doesn't load.\n\nThis issue occurs on both smartphones and PCs.\nIt happens with the latest versions.\n\nIf needed, I can reactivate the component on my forum and send you a link to the bug via PM.\n\nThanks.","actions_summary":[{"id":2,"count":2}],"moderator":false,"admin":false,"staff":false,"user_id":98294,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"안녕하세요, \n와, 이 컴포넌트는 정말 멋지고 특히 스마트폰에서 뛰어난 사용성을 제공하는 것 같습니다! \n막히는 버그를 발견했습니다: \n"Post Voting 플러그인"이 적용된 토픽에서 모달이 로드되지 않습니다. \n이 문제는 스마트폰과 PC 모두에서 발생합니다. \n최신 버전에서도 동일한 현상이 나타납니다. \n필요하시면 제 포럼에서 해당 컴포넌트를 다시 활성화하고 버그 링크를 DM으로 보내드리겠습니다. \n감사합니다.","truncated":true,"post_url":"/t/topic-preview-modal/409712/73","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":2}],"current_user_reaction":null,"reaction_users_count":2,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034545,"name":"system","username":"system","avatar_template":"/user_avatar/meta.discourse.org/system/{size}/443519_2.png","created_at":"2026-09-06T13:01:59.552Z","cooked":"

Today on meta.discourse.org…

\n

Key Stats

\n\n

Top users by posts and likes

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
UserPostsLikes
Moin715
Ethsim295
Don25
Ed_S44
Mcwumbly23
Sterretje13
Jagster42
Satonotdead42
Emilio32
Scavin22
\n

Interesting Topics

\n

#Announcements

\n\n

#Plugin

\n\n

#Theme component

\n\n

#Feature

\n\n

bug

\n\n

Support

\n\n

Activity by the Team Group

\n\n
\n

Yesterday’s mix of spam-fighting, permanent-deletion PRs, and Discord-style voice rooms proved that even a forum platform knows how to throw a party.

","post_number":941,"post_type":1,"posts_count":714,"updated_at":"2026-09-06T13:01:59.552Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":1,"readers_count":0,"score":0.2,"yours":false,"topic_id":291852,"topic_slug":"daily-summary-1pm-utc","topic_title":"일일 요약 (UTC 오후 1시)","topic_html_title":"일일 요약 (UTC 오후 1시)","category_id":157,"display_username":"system","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"# Today on meta.discourse.org...\n\n## Key Stats\n\n- **63 posts** were created across **23 topics** in the last 24 hours.\n- **58 likes** were given on posts returned in this window.\n\n### Top users by posts and likes\n\n| User | Posts | Likes |\n|---|---|---|\n| Moin | 7 | 15 |\n| Ethsim2 | 9 | 5 |\n| Don | 2 | 5 |\n| Ed_S | 4 | 4 |\n| Mcwumbly | 2 | 3 |\n| Sterretje | 1 | 3 |\n| Jagster | 4 | 2 |\n| Satonotdead | 4 | 2 |\n| Emilio | 3 | 2 |\n| Scavin | 2 | 2 |\n\n## Interesting Topics\n\n### #Announcements\n\n- [**Easier account signup using email codes**](https://meta.discourse.org/t/easier-account-signup-using-email-codes/407068/29?silent=true) – On the #signup announcement, Thisisjoshjones asked whether the new email-code flow could also be applied to the invitations landing page, and Mcwumbly replied that [work is already in progress in discourse/discourse#43138](https://github.com/discourse/discourse/pull/43138). [read more](https://meta.discourse.org/t/easier-account-signup-using-email-codes/407068/30?silent=true)\n\n- [**Introducing Upcoming Changes**](https://meta.discourse.org/t/introducing-upcoming-changes-a-system-to-manage-new-features-and-changes-to-existing-functionality-in-your-community/392894/50?silent=true) – Ethsim2 asked if opting out of `Dashboard improvements` still preserves the legacy admin dashboard and its old update-status faces; Mcwumbly [confirmed](https://meta.discourse.org/t/introducing-upcoming-changes-a-system-to-manage-new-features-and-changes-to-existing-functionality-in-your-community/392894/52?silent=true) the legacy dashboard is on its way out once the new one becomes permanent, pointing to the new System section for self-hosters. [read more](https://meta.discourse.org/t/introducing-upcoming-changes-a-system-to-manage-new-features-and-changes-to-existing-functionality-in-your-community/392894/51?silent=true)\n\n- [**PostgreSQL 18 update for self-hosters**](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/85?silent=true) – AstonJ shared that Lilly's advice about checking disk space helped make the upgrade go smoothly on dual containers. [read more](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/85?silent=true)\n\n- [**Voice: Discord-style voice and video rooms, now bundled with Discourse**](https://meta.discourse.org/t/voice-discord-style-voice-and-video-rooms-now-bundled-with-discourse/411337/27?silent=true) – Jagster needed help finding how to remove rooms from the new #voice feature; Satonotdead explained the option lives in the plugin's room settings, not in the forum GUI, and Jagster eventually found it. [read more](https://meta.discourse.org/t/voice-discord-style-voice-and-video-rooms-now-bundled-with-discourse/411337/29?silent=true)\n\n- [**A preview of the new Workflows feature**](https://meta.discourse.org/t/a-preview-of-the-new-workflows-feature/406990/28?silent=true) – Gilles suggested that when an event reaches \"full\" status, Workflows should be able to rename the event to add \"complet\" and perhaps show remaining spots in the year view. [read more](https://meta.discourse.org/t/a-preview-of-the-new-workflows-feature/406990/28?silent=true)\n\n### #Plugin\n\n- [**Discourse Boards**](https://meta.discourse.org/t/discourse-boards/411414/3?silent=true) – Mcwumbly's announcement that Boards is bundled with core drew a question from M_Terenui about self-hosted availability; Moin explained that the feature landed in the dev build only four days ago and can be enabled via Upcoming Changes. [read more](https://meta.discourse.org/t/discourse-boards/411414/3?silent=true)\n\n### #Theme component\n\n- [**External Link Shield – Exit Confirmation & Trust Gating**](https://meta.discourse.org/t/external-link-shield-exit-confirmation-trust-gating/392962/7?silent=true) – Don shipped v2.0 of this theme component with real SVG icons, new settings for icon position/colors, and an anonymous-blocking crash fix; Moin recommended switching those custom icon settings to the native `icon` setting type, which Don adopted. [read more](https://meta.discourse.org/t/external-link-shield-exit-confirmation-trust-gating/392962/8?silent=true)\n\n### #Feature\n\n- [**Allow user to delete their own topic at any time**](https://meta.discourse.org/t/allow-user-to-delete-their-own-topic-at-any-time/411689/1?silent=true) – Emilio reignited the debate about the hardcoded 24-hour deletion window; Moin [linked to the Guardian code](https://github.com/discourse/discourse/blob/5e9779d4cd418af07a6ed01005d558eda76f2f69/lib/guardian/topic_guardian.rb#L383-L385), Ed_S argued the conversational record matters, and Ecki raised GDPR as an argument for more user control. [read more](https://meta.discourse.org/t/allow-user-to-delete-their-own-topic-at-any-time/411689/10?silent=true)\n\n- [**Actually delete permanently without all the obstacles**](https://meta.discourse.org/t/actually-delete-permanently-without-all-the-obstacles/411687/4?silent=true) – Ethsim2 has been working on a [PR that adds a per-admin opt-in](https://github.com/discourse/discourse/pull/43323) to permanently delete a topic and all replies in one action, with a preference under Preferences → Interface, Staff Action Log entries, and a clearer irreversible confirmation. [read more](https://meta.discourse.org/t/actually-delete-permanently-without-all-the-obstacles/411687/3?silent=true)\n\n- [**Combining Category types**](https://meta.discourse.org/t/combining-category-types/409045/8?silent=true) – Ecki asked whether solved status could work from a tag, and Satonotdead agreed that topics should be able to combine \"Me too\" and voting; Moin noted `enable_solved_tags` exists but may not support the \"Me too\" button. [read more](https://meta.discourse.org/t/combining-category-types/409045/6?silent=true)\n\n### #Bug\n\n- [**Discourse/mail-receiver:release Docker image appears to be outdated**](https://meta.discourse.org/t/discourse-mail-receiver-release-docker-image-appears-to-be-outdated/411734/1?silent=true) – Scavin found the published #mail-receiver image is nearly two years old and still runs removed fast-rejection code, breaking `RCPT TO`; Ethsim2 [independently confirmed](https://meta.discourse.org/t/discourse-mail-receiver-release-docker-image-appears-to-be-outdated/411734/3?silent=true) that a merged `email_encoded` change never made it into the published image. [read more](https://meta.discourse.org/t/discourse-mail-receiver-release-docker-image-appears-to-be-outdated/411734/2?silent=true)\n\n- [**Discourse-events can cause 500 when deleting a topic in development**](https://meta.discourse.org/t/discourse-events-can-cause-500-when-deleting-a-topic-in-development-uninitialized-calendar-extractor/411731/1?silent=true) – Ethsim2 traced a `DELETE /t/35` 500 to an `uninitialized constant DiscourseEvents::Calendar::Extractor` in the `:post_destroyed` callback, and wondered whether dev-mode reloading or the #events plugin's callback loading is responsible. [read more](https://meta.discourse.org/t/discourse-events-can-cause-500-when-deleting-a-topic-in-development-uninitialized-calendar-extractor/411731/1?silent=true)\n\n- [**Regression: new check_username rate limit can block normal signup flow**](https://meta.discourse.org/t/regression-new-check-username-rate-limit-can-block-normal-signup-flow/411646/4?silent=true) – Southpaw thanked HBP for the detailed repro and said a fix is in the works for the new #signup rate limit. [read more](https://meta.discourse.org/t/regression-new-check-username-rate-limit-can-block-normal-signup-flow/411646/4?silent=true)\n\n### #Support\n\n- [**Is anyone experiencing an odd spam user attack? Any way to block?**](https://meta.discourse.org/t/is-anyone-experiencing-an-odd-spam-user-attack-any-way-to-block/404427/16?silent=true) – LordOfBikes described blocking cloud-provider networks after a wave of registrations, One1 said hCaptcha eliminated the exact spam pattern, Ed_S added an \"Interests\" user field to help human reviewers, and Moin suggested checking `moderators_view_ips` / `moderators_view_emails`. [read more](https://meta.discourse.org/t/is-anyone-experiencing-an-odd-spam-user-attack-any-way-to-block/404427/21?silent=true)\n\n- [**Randomly attached tags**](https://meta.discourse.org/t/randomly-attached-tags/411729/1?silent=true) – Ecki asked where a mysterious third #tag keeps coming from on hand-tagged posts; Moin asked whether it was a required parent tag in a tag group, but Ecki ruled that out. [read more](https://meta.discourse.org/t/randomly-attached-tags/411729/3?silent=true)\n\n## Activity by the Team Group\n\n- Mcwumbly [announced Discourse Boards](https://meta.discourse.org/t/discourse-boards/411414/1?silent=true), noting that the plugin is bundled with Discourse core and can be previewed via Upcoming Changes.\n\n- Mcwumbly [shared a WIP pull request](https://meta.discourse.org/t/easier-account-signup-using-email-codes/407068/30?silent=true) to bring the new email-code signup experience to invitations, following Thisisjoshjones's request.\n\n- Mcwumbly [confirmed that the legacy admin dashboard will be removed](https://meta.discourse.org/t/introducing-upcoming-changes-a-system-to-manage-new-features-and-changes-to-existing-functionality-in-your-community/392894/52?silent=true) once Dashboard improvements become permanent.\n\n- Southpaw [responded to the check_username regression report](https://meta.discourse.org/t/regression-new-check-username-rate-limit-can-block-normal-signup-flow/411646/4?silent=true), thanking HBP for the detailed write-up and confirming a fix is in the works.\n\n---\nYesterday's mix of spam-fighting, permanent-deletion PRs, and Discord-style voice rooms proved that even a forum platform knows how to throw a party.","actions_summary":[],"moderator":true,"admin":true,"staff":true,"user_id":-1,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Today on meta.discourse.org…\nKey Stats\n\n63 posts were created across 23 topics in the last 24 hours.\n58 likes were given on posts returned in this window.\n\nTop users by posts and likes\n\n\n\n\nUser\nPosts\nLikes\n\n\n\n\nMoin\n7\n15\n\n\nEthsim2\n9\n5\n\n\nDon\n2\n5\n\n\nEd_S\n4\n4\n\n\nMcwumbly\n2\n3\n\n\nSterretje\n1\n3\n\n\nJagster\n4\n2\n\n…","truncated":true,"post_url":"/t/daily-summary-1pm-utc/291852/941","locale":null,"is_localized":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034539,"name":"","username":"satonotdead","avatar_template":"/user_avatar/meta.discourse.org/satonotdead/{size}/447830_2.png","created_at":"2026-09-06T12:36:54.617Z","cooked":"

정말 훌륭하네요, 니콜스. 저도 보통 생일에 프로젝트를 진행하거나 발표하곤 해요.

\n

우리가 하는 일과 삶을 일치시키는 건 건강한 방법이라고 생각해요. 그리고 우리가 세상에 나누는 것에 얼마나 많은 에너지와 품질을 쏟고 있는지를 말해 주는 것이기도 하죠. 상황이 허락하지 않을 때도, 의도와 노력이야말로 남아 있는 진정한 가치입니다.

\n

생일 축하해요!

","post_number":33,"post_type":1,"posts_count":31,"updated_at":"2026-09-06T12:36:54.617Z","reply_count":0,"reply_to_post_number":31,"quote_count":0,"incoming_link_count":5,"reads":18,"readers_count":17,"score":58.6,"yours":false,"topic_id":408132,"topic_slug":"a-social-mobile-desktop-client-for-communities-2","topic_title":"커뮤니티용 소셜 모바일 및 데스크톱 클라이언트 (2)","topic_html_title":"커뮤니티용 소셜 모바일 및 데스크톱 클라이언트 (2)","category_id":124,"display_username":"","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","reply_to_user":{"id":189150,"username":"nicolsdennis","name":"Nicols Dennis","avatar_template":"/user_avatar/meta.discourse.org/nicolsdennis/{size}/545883_2.png"},"bookmarked":false,"raw":"This is great, Nicols. I also usually work on or announce projects on my birthday.\n\nI believe it's a healthy way to align what we do with our lives and speaks volumes about the energy and quality we put into what we share with the world. Even if times don't allow for it, the intention and effort is the real value that remains.\n\nHappy birthday!","actions_summary":[{"id":2,"count":2}],"moderator":false,"admin":false,"staff":false,"user_id":71041,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"정말 훌륭하네요, 니콜스. 저도 보통 생일에 프로젝트를 진행하거나 발표하곤 해요. \n우리가 하는 일과 삶을 일치시키는 건 건강한 방법이라고 생각해요. 그리고 우리가 세상에 나누는 것에 얼마나 많은 에너지와 품질을 쏟고 있는지를 말해 주는 것이기도 하죠. 상황이 허락하지 않을 때도, 의도와 노력이야말로 남아 있는 진정한 가치입니다. \n생일 축하해요!","truncated":true,"post_url":"/t/a-social-mobile-desktop-client-for-communities-2/408132/33","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":2}],"current_user_reaction":null,"reaction_users_count":2,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034531,"name":"Sammy","username":"eisammy","avatar_template":"/user_avatar/meta.discourse.org/eisammy/{size}/528804_2.png","created_at":"2026-09-06T12:20:38.798Z","cooked":"

이 컴포넌트의 존재를 제가 어떻게 알았을까요? 유지보수를 해주셔서 정말 감사합니다. 테스트해 보겠습니다. \":heart_eyes:\"

","post_number":10,"post_type":1,"posts_count":10,"updated_at":"2026-09-06T12:20:38.798Z","reply_count":0,"reply_to_post_number":7,"quote_count":0,"incoming_link_count":1,"reads":9,"readers_count":8,"score":36.8,"yours":false,"topic_id":392962,"topic_slug":"external-link-shield-exit-confirmation-trust-gating","topic_title":"외부 링크 보호 – 종료 확인 및 신뢰 게이트","topic_html_title":"외부 링크 보호 – 종료 확인 및 신뢰 게이트","category_id":120,"display_username":"Sammy","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Bug Reporter","title_is_group":false,"reply_to_user":{"id":78445,"username":"Don","name":"","avatar_template":"/user_avatar/meta.discourse.org/don/{size}/228726_2.png"},"bookmarked":false,"raw":"Como eu não sabia da existência desse componente? Muito obrigado por fazer a manutenção, irei testa-lo :heart_eyes:","actions_summary":[{"id":2,"count":2}],"moderator":false,"admin":false,"staff":false,"user_id":146973,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"이 컴포넌트의 존재를 제가 어떻게 알았을까요? 유지보수를 해주셔서 정말 감사합니다. 테스트해 보겠습니다. :heart_eyes:","truncated":true,"post_url":"/t/external-link-shield-exit-confirmation-trust-gating/392962/10","locale":"pt_BR","is_localized":true,"language":"pt_BR","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"chefs_kiss","type":"emoji","count":1},{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":2,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034524,"name":"","username":"Don","avatar_template":"/user_avatar/meta.discourse.org/don/{size}/228726_2.png","created_at":"2026-09-06T11:32:28.217Z","cooked":"

좋아요, 고맙습니다. 수정했습니다. \":slightly_smiling_face:\"

","post_number":9,"post_type":1,"posts_count":10,"updated_at":"2026-09-06T11:32:28.217Z","reply_count":0,"reply_to_post_number":8,"quote_count":0,"incoming_link_count":1,"reads":10,"readers_count":9,"score":52.0,"yours":false,"topic_id":392962,"topic_slug":"external-link-shield-exit-confirmation-trust-gating","topic_title":"외부 링크 보호 – 종료 확인 및 신뢰 게이트","topic_html_title":"외부 링크 보호 – 종료 확인 및 신뢰 게이트","category_id":120,"display_username":"","primary_group_name":"VolunteerMods","flair_name":"VolunteerMods","flair_url":"https://global.discourse-cdn.com/meta/original/4X/2/7/d/27de051915b8a604d176484cd260d10cfc956d42.svg","flair_bg_color":"","flair_color":"","flair_group_id":276,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Leader","title_is_group":false,"reply_to_user":{"id":95552,"username":"Moin","name":"","avatar_template":"/user_avatar/meta.discourse.org/moin/{size}/554653_2.png"},"bookmarked":false,"raw":"Cool, thanks changed it. :slightly_smiling_face:","actions_summary":[{"id":2,"count":3}],"moderator":false,"admin":false,"staff":false,"group_moderator":true,"user_id":78445,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"좋아요, 고맙습니다. 수정했습니다. :slightly_smiling_face:","truncated":true,"post_url":"/t/external-link-shield-exit-confirmation-trust-gating/392962/9","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":3}],"current_user_reaction":null,"reaction_users_count":3,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034523,"name":"","username":"elmuerte","avatar_template":"/user_avatar/meta.discourse.org/elmuerte/{size}/456517_2.png","created_at":"2026-09-06T11:26:02.226Z","cooked":"

이 비추천(deprecation) 알림을 우회하면서 user_field에 여전히 접근할 수 있는 방법을 찾았습니다:

\n
api.getCurrentUser().findDetails().then((user) => { ... });\n
\n

다만, findDetails는 항상 서버에 요청을 보냅니다. 캐싱은 이루어지지 않습니다. 한 번 호출되면 현재 사용자의 user_fields가 채워지게 됩니다.

\n

따라서 로직을 다음과 같이 조금 최적화할 수 있습니다:

\n
\nfunction withUserFields(user, callback) {\n  if (user.user_fields === undefined) {\n    user.findDetails().then(callback);\n  } else {\n    callback(user);\n  }\n}\n\nwithUserFields(api.getCurrentUser(), (user) => {\n  // user.user_fields[]를 사용하여 무언가를 수행\n});\n\n\n
","post_number":2,"post_type":1,"posts_count":2,"updated_at":"2026-09-06T11:26:02.226Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":9,"readers_count":8,"score":6.8,"yours":false,"topic_id":411227,"topic_slug":"deprecation-notice-getting-timezone-property-of-user-object-is-deprecated-use-user-option-object-instead","topic_title":"비추천 공지: 사용자 객체의 timezone 속성을 가져오는 기능은 비추천되었습니다. 대신 user_option 객체를 사용하세요","topic_html_title":"비추천 공지: 사용자 객체의 timezone 속성을 가져오는 기능은 비추천되었습니다. 대신 user_option 객체를 사용하세요","category_id":7,"display_username":"","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Plugin Author","title_is_group":false,"bookmarked":false,"raw":"I found a away around getting this deprecation notice, and still getting access to the `user_field`:\n\n```javascript\napi.getCurrentUser().findDetails().then((user) => { ... });\n```\n\nHowever, `findDetails` will *always* send a request to the server. Nothing is cached. Once it is called, the current user will have a populated user_fields.\n\nSo you can optimize the logic a bit like:\n\n```javascript\n\nfunction withUserFields(user, callback) {\n if (user.user_fields === undefined) {\n user.findDetails().then(callback);\n } else {\n callback(user);\n }\n}\n\nwithUserFields(api.getCurrentUser(), (user) => {\n // do something with user.user_fields[]\n});\n\n\n```","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":119375,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"이 비추천(deprecation) 알림을 우회하면서 user_field에 여전히 접근할 수 있는 방법을 찾았습니다: \napi.getCurrentUser().findDetails().then((user) => { ... });\n\n다만, findDetails는 항상 서버에 요청을 보냅니다. 캐싱은 이루어지지 않습니다. 한 번 호출되면 현재 사용자의 user_fields가 채워지게 됩니다. \n따라서 로직을 다음과 같이 조금 최적화할 수 있습니다: \n\nfunction withUserFields(user, callback) {\n if (u…","truncated":true,"post_url":"/t/deprecation-notice-getting-timezone-property-of-user-object-is-deprecated-use-user-option-object-instead/411227/2","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034521,"name":"","username":"Moin","avatar_template":"/user_avatar/meta.discourse.org/moin/{size}/554653_2.png","created_at":"2026-09-06T11:09:30.171Z","cooked":"\n\n

업데이트 감사합니다. 정말 감사드립니다!

","post_number":2,"post_type":1,"posts_count":2,"updated_at":"2026-09-06T11:09:30.171Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":7,"readers_count":6,"score":21.4,"yours":false,"topic_id":410092,"topic_slug":"icon-type-theme-setting-in-objects-type-settings","topic_title":"오브젝트 유형 설정에서 아이콘 유형 테마 설정","topic_html_title":"오브젝트 유형 설정에서 아이콘 유형 테마 설정","category_id":2,"display_username":"","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Kluges Köpfchen","title_is_group":false,"bookmarked":false,"raw":"https://github.com/discourse/discourse/pull/42632\n\nThanks for the update, much appreciated!","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":95552,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"업데이트 감사합니다. 정말 감사드립니다!","truncated":true,"post_url":"/t/icon-type-theme-setting-in-objects-type-settings/410092/2","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034520,"name":"","username":"Moin","avatar_template":"/user_avatar/meta.discourse.org/moin/{size}/554653_2.png","created_at":"2026-09-06T11:05:16.352Z","cooked":"\n

v2.1에 대한 제안: 아이콘 설정 유형 사용

\n","post_number":8,"post_type":1,"posts_count":10,"updated_at":"2026-09-06T11:05:16.352Z","reply_count":1,"reply_to_post_number":7,"quote_count":1,"incoming_link_count":1,"reads":12,"readers_count":11,"score":72.4,"yours":false,"topic_id":392962,"topic_slug":"external-link-shield-exit-confirmation-trust-gating","topic_title":"외부 링크 보호 – 종료 확인 및 신뢰 게이트","topic_html_title":"외부 링크 보호 – 종료 확인 및 신뢰 게이트","category_id":120,"display_username":"","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Kluges Köpfchen","title_is_group":false,"bookmarked":false,"raw":"[quote=\"Don, post:7, topic:392962\"]\n* external_link_icon\n[/quote]\nSuggestion for v2.1: Using the icon setting type\n\n[quote=\"Discourse, post:1, topic:82557\"]\n**Icon Setting:**\n\n```\nbanner_icon:\n default: bullhorn\n type: icon\n\n```\n\nIcon settings give site owners a searchable icon picker, and the value is the icon name. Discourse adds the selected icon to the sprite sheet, so you can render it in your theme without registering it separately.\n[/quote]","actions_summary":[{"id":2,"count":4}],"moderator":false,"admin":false,"staff":false,"user_id":95552,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"v2.1에 대한 제안: 아이콘 설정 유형 사용","truncated":true,"post_url":"/t/external-link-shield-exit-confirmation-trust-gating/392962/8","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":4}],"current_user_reaction":null,"reaction_users_count":4,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034518,"name":"","username":"Don","avatar_template":"/user_avatar/meta.discourse.org/don/{size}/228726_2.png","created_at":"2026-09-06T10:40:16.610Z","cooked":"

안녕하세요 \":waving_hand:\"

\n

테마 컴포넌트를 v2.0으로 업데이트했습니다 \":tada:\": DEV: Replace CSS-drawn link icons with configurable d-icon rendering; fix anonymous blocking crashAdd files via upload - Pull Request #1 - VaperinaDEV/external-link-shield - GitHub

\n

이번 업데이트에는 다음 내용이 포함되어 있습니다:

\n\n
\n

> ./support --coffee \":heart:\"

","post_number":7,"post_type":1,"posts_count":10,"updated_at":"2026-09-06T10:43:55.502Z","reply_count":2,"reply_to_post_number":6,"quote_count":0,"incoming_link_count":1,"reads":12,"readers_count":11,"score":47.4,"yours":false,"topic_id":392962,"topic_slug":"external-link-shield-exit-confirmation-trust-gating","topic_title":"외부 링크 보호 – 종료 확인 및 신뢰 게이트","topic_html_title":"외부 링크 보호 – 종료 확인 및 신뢰 게이트","category_id":120,"display_username":"","primary_group_name":"VolunteerMods","flair_name":"VolunteerMods","flair_url":"https://global.discourse-cdn.com/meta/original/4X/2/7/d/27de051915b8a604d176484cd260d10cfc956d42.svg","flair_bg_color":"","flair_color":"","flair_group_id":276,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Leader","title_is_group":false,"reply_to_user":{"id":71041,"username":"satonotdead","name":"","avatar_template":"/user_avatar/meta.discourse.org/satonotdead/{size}/447830_2.png"},"bookmarked":false,"raw":"Hello :waving_hand: \n\nI've updated the theme component to **v2.0** :tada:: https://github.com/VaperinaDEV/external-link-shield/pull/1\n\nThis update contains:\n\n- Swap the hand-maintained SVG `mask-image` icons for real `` elements rendered via `iconHTML()`, inserted next to links by secure-links.js\n- Add settings: \n - `exit_confirmation_continue_icon`\n - `external_link_icon`,\n - `trusted_link_icon`,\n - `external_link_icon_color`,\n - `trusted_link_icon_color`,\n - `link_icon_position` (before/after)\n\n- Fix crash when `enable_anonymous_blocking` is disabled: `currentUser.trust_level` was read for anonymous users (null), throwing and silently leaving the original `` unprocessed/unprotected; anonymous visitors now get a well-defined pass-through (icon + optional confirmation modal, no TL gating)\n\n---\n\n[> ./support --coffee](https://meta.discourse.org/u/don) :heart:","actions_summary":[{"id":2,"count":2}],"moderator":false,"admin":false,"staff":false,"group_moderator":true,"user_id":78445,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"안녕하세요 :waving_hand: \n테마 컴포넌트를 v2.0으로 업데이트했습니다 :tada:: DEV: Replace CSS-drawn link icons with configurable d-icon rendering; fix anonymous blocking crashAdd files via upload - Pull Request #1 - VaperinaDEV/external-link-shield - GitHub \n이번 업데이트에는 다음 내용이 포함되어 있습니다: \n\n\n수동으로 관리하던 SVG mask-image 아이콘을 ico…","truncated":true,"post_url":"/t/external-link-shield-exit-confirmation-trust-gating/392962/7","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"100","type":"emoji","count":1},{"id":"exploding_head","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":2,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034516,"name":null,"username":"gilles","avatar_template":"/user_avatar/meta.discourse.org/gilles/{size}/549022_2.png","created_at":"2026-09-06T10:13:06.212Z","cooked":"

생일 축하해 @nicolsdennis \":partying_face:\"

","post_number":32,"post_type":1,"posts_count":31,"updated_at":"2026-09-06T10:13:06.212Z","reply_count":0,"reply_to_post_number":31,"quote_count":0,"incoming_link_count":1,"reads":21,"readers_count":20,"score":39.2,"yours":false,"topic_id":408132,"topic_slug":"a-social-mobile-desktop-client-for-communities-2","topic_title":"커뮤니티용 소셜 모바일 및 데스크톱 클라이언트 (2)","topic_html_title":"커뮤니티용 소셜 모바일 및 데스크톱 클라이언트 (2)","category_id":124,"display_username":null,"primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"reply_to_user":{"id":189150,"username":"nicolsdennis","name":"Nicols Dennis","avatar_template":"/user_avatar/meta.discourse.org/nicolsdennis/{size}/545883_2.png"},"bookmarked":false,"raw":"Bon Anniversaire @nicolsdennis :partying_face:","actions_summary":[{"id":2,"count":2}],"moderator":false,"admin":false,"staff":false,"user_id":173218,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"생일 축하해 @nicolsdennis :partying_face:","truncated":true,"post_url":"/t/a-social-mobile-desktop-client-for-communities-2/408132/32","locale":"fr","is_localized":true,"language":"fr","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":2}],"current_user_reaction":null,"reaction_users_count":2,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034513,"name":null,"username":"gilles","avatar_template":"/user_avatar/meta.discourse.org/gilles/{size}/549022_2.png","created_at":"2026-09-06T10:00:52.600Z","cooked":"

이벤트 상태가 '정원’으로 변경되면 이벤트 이름에 \"정원\"이라는 문구가 자동으로 추가되는 기능이 가능한지 궁금합니다. 이렇게 하면 사용자가 연도별 미리보기에서 정원 마감된 이벤트를 바로 확인할 수 있어, 이벤트에 들어와 자리가 남아 있는지 확인해야 하는 번거로움을 줄일 수 있습니다. 더 나아가 이벤트 이름에 남은 좌석 수를 표시하는 것도 고려해 볼 수 있겠습니다. 제 사용자분들의 이용 경험을 개선하기 위한 제 의견입니다. \":sweat_smile:\"

","post_number":28,"post_type":1,"posts_count":20,"updated_at":"2026-09-06T10:00:52.600Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":10,"readers_count":9,"score":7.0,"yours":false,"topic_id":406990,"topic_slug":"a-preview-of-the-new-workflows-feature","topic_title":"새로운 워크플로 기능 미리보기","topic_html_title":"새로운 워크플로 기능 미리보기","category_id":67,"display_username":null,"primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"J'aimerais savoir si c'est possible lorsque le statuts événement est complet il renomme automatiquement le nom de l'événement en ajoutant \"complet\". Cela permettrait aux utilisateurs de voir directement les événements complet dans l'aperçu année par exemple cela évite de cliquer sur l'événement pour savoir si il reste des places. Sinon pour aller plus loin afficher le nombre de places dans le nom de l'événement. Après c'est mon ressenti pour améliorer l'utilisation auprès de mes utilisateurs :sweat_smile:","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":173218,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"이벤트 상태가 '정원’으로 변경되면 이벤트 이름에 "정원"이라는 문구가 자동으로 추가되는 기능이 가능한지 궁금합니다. 이렇게 하면 사용자가 연도별 미리보기에서 정원 마감된 이벤트를 바로 확인할 수 있어, 이벤트에 들어와 자리가 남아 있는지 확인해야 하는 번거로움을 줄일 수 있습니다. 더 나아가 이벤트 이름에 남은 좌석 수를 표시하는 것도 고려해 볼 수 있겠습니다. 제 사용자분들의 이용 경험을 개선하기 위한 제 의견입니다. :sweat_smile:","truncated":true,"post_url":"/t/a-preview-of-the-new-workflows-feature/406990/28","locale":"fr","is_localized":true,"language":"fr","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034504,"name":"Ethan ","username":"Ethsim2","avatar_template":"/user_avatar/meta.discourse.org/ethsim2/{size}/522255_2.png","created_at":"2026-09-06T07:01:50.420Z","cooked":"

#mail-receiver의 다른 변경 사항에서 오래된 릴리스 이미지를 확인할 수 있습니다.

\n

8월 11일에 병합된 이 PR을 열었습니다:

\n\n\n

이 PR은 메일 리시버를 다음과 같이 변경합니다:

\n

post.set_form_data(email: @mail)

\n

Discourse에서 기대하는 새로운 email_encoded 매개변수로 변경됩니다.

\n

PR이 병합된 후 8월 17일에 mail-receiver를 다시 빌드했지만, 새로 빌드된 컨테이너에는 여전히 다음 코드가 포함되어 있었습니다:

\n

post.set_form_data(email: @mail)

\n

병합된 PR에 세부 정보를 여기에 추가했습니다:

\n\n\n

8월 22일에 다시 빌드했으며 ./launcher rebuild mail-receiver 명령은 게시된 릴리스 이미지가 최신 상태라고 보고했고, 다이제스트는 다음과 같았습니다:

\n

sha256:2a0d45bb92a783c846a821e635413764eeadb3441ef6190085545a4bf054cb1e

\n

제 설치 환경에서는 수신 메일이 여전히 정상 작동하지만, 수신된 각 메일은 게시된 이미지에 병합된 #37 변경 사항이 포함되어 있지 않기 때문에 Discourse의 다음 경고를 계속 트리거합니다:

\n

the email parameter is deprecated

\n

따라서 이는 여러분이 발견한 첫 번째 문제를 독립적으로 확인하는 것으로 보입니다: mail-receiver 저장소에 병합된 변경 사항이 게시된 discourse/mail-receiver:release 이미지에 반영되지 않고 있습니다.

","post_number":3,"post_type":1,"posts_count":3,"updated_at":"2026-09-06T07:12:42.419Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":13,"readers_count":12,"score":37.6,"yours":false,"topic_id":411734,"topic_slug":"discourse-mail-receiver-release-docker-image-appears-to-be-outdated","topic_title":"Discourse/mail-receiver:release Docker 이미지가 오래된 것으로 보입니다","topic_html_title":"Discourse/mail-receiver:release Docker 이미지가 오래된 것으로 보입니다","category_id":1,"display_username":"Ethan ","primary_group_name":null,"flair_name":"theme_authors","flair_url":"paintbrush","flair_bg_color":"ddd","flair_color":"111","flair_group_id":73,"badges_granted":[],"version":4,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Tester","title_is_group":false,"bookmarked":false,"raw":"I can confirm the outdated release image from another change in #mail-receiver.\n\nI opened this PR, which was merged on 11 August: https://github.com/discourse/mail-receiver/pull/37\n\nIt changes the mail receiver from:\n\n`post.set_form_data(email: @mail)`\n\nto the newer `email_encoded` parameter expected by Discourse.\n\nAfter the PR was merged, I rebuilt mail-receiver on 17 August, but the freshly rebuilt container still contained:\n\n`post.set_form_data(email: @mail)`\n\nI added the details to the merged PR here:\n\n\nhttps://github.com/discourse/mail-receiver/pull/37#issuecomment-5316800475\n\nI rebuilt again on 22 August and `./launcher rebuild mail-receiver` reported the published release image as up to date, with digest:\n\n`sha256:2a0d45bb92a783c846a821e635413764eeadb3441ef6190085545a4bf054cb1e`\n\nIncoming mail still works on my installation, but each received email continues to trigger Discourse’s:\n\n`the email parameter is deprecated`\n\nwarning because the published image does not contain the merged [#37](https://github.com/discourse/mail-receiver/pull/37) change.\n\nSo this appears to independently confirm the first issue you’ve found: changes merged into the #mail-receiver repository have not been making it into the published `discourse/mail-receiver:release` image.","actions_summary":[{"id":2,"count":2}],"moderator":false,"admin":false,"staff":false,"user_id":160471,"hidden":false,"trust_level":1,"deleted_at":null,"user_deleted":false,"edit_reason":"the first onebox was consuming too much height","can_view_edit_history":true,"wiki":false,"excerpt":"#mail-receiver의 다른 변경 사항에서 오래된 릴리스 이미지를 확인할 수 있습니다. \n8월 11일에 병합된 이 PR을 열었습니다: \n\n\n이 PR은 메일 리시버를 다음과 같이 변경합니다: \npost.set_form_data(email: @mail) \nDiscourse에서 기대하는 새로운 email_encoded 매개변수로 변경됩니다. \nPR이 병합된 후 8월 17일에 mail-receiver를 다시 빌드했지만, 새로 빌드된 컨테이너에는 여전히 다음 코드가 포함되어 있었습니다: \npost.set_form_data(email: …","truncated":true,"post_url":"/t/discourse-mail-receiver-release-docker-image-appears-to-be-outdated/411734/3","locale":"en","is_localized":true,"language":"en","localization_outdated":true,"customer_flair_customer":null,"event":null,"reactions":[{"id":"+1","type":"emoji","count":1},{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":2,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034502,"name":"scavin","username":"scavin","avatar_template":"/user_avatar/meta.discourse.org/scavin/{size}/115938_2.png","created_at":"2026-09-06T05:04:44.080Z","cooked":"

업데이트: 현재 main 브랜치 테스트

\n

현재 main 브랜치를 로컬에서 빌드하여 또 다른 문제를 발견했습니다.

\n

기존 Docker Hub의 release 이미지는 여전히旧的 빠른 거부(fast-rejection) 코드를 실행하며, RCPT 단계에서 다음과 같은 오류로 실패합니다:

\n
450 4.7.1 Recipient address rejected: Internal error, API request failed\n
\n

그러나 현재 main 브랜치에서는 이미 smtp_should_reject / 빠른 거부 구현이 제거되었습니다. main을 빌드한 후 Postfix는 다음과 같이 실패합니다:

\n
warning: connect to private/policy: No such file or directory\n451 4.3.5 Recipient address rejected: Server configuration problem\n
\n

이 문제를 Dockerfile의 두 가지 남은 참조로 추적했습니다:

\n
check_policy_service unix:private/policy\n
\n

정책 서비스 자체는 제거되었지만, smtpd_recipient_restrictions에는 여전히 해당 소켓이 참조되고 있습니다.

\n

smtpd_recipient_restrictions에서 unix:private/policy를 제거하고 이미지를 다시 빌드한 후, 수신 SMTP 메일이 성공적으로 수락되었습니다.

\n

Global API Key로 전환한 후 Discourse로의 전달도 성공했습니다:

\n
dsn=2.0.0, status=sent (delivered via discourse service)\n
\n

따라서 두 가지 별개의 문제가 있는 것 같습니다:

\n
    \n
  1. 공개된 discourse/mail-receiver:release 이미지는 오래되었고 여전히旧的 빠른 거부 구현을 포함하고 있습니다.
    2. \n
  2. 현재 main 브랜치에서는 해당 구현이 제거되었지만, Dockerfile은 여전히 Postfix가 unix:private/policy를 사용하도록 구성하고 있습니다.
    3. \n
\n

또한 세분화된 API 키와 관련된 별도의 문제도 있을 수 있습니다: receive emails 범위로만 설정된 키는 /admin/email/handle_mail에서 HTTP 404를 반환한 반면, Global API Key는 HTTP 200을 반환했습니다.

\n

도움이 된다면 Dockerfile의 두 가지 오래된 private/policy 참조에 대한 PR을 제출할 수 있습니다.

","post_number":2,"post_type":1,"posts_count":3,"updated_at":"2026-09-06T05:04:44.080Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":16,"readers_count":15,"score":38.2,"yours":false,"topic_id":411734,"topic_slug":"discourse-mail-receiver-release-docker-image-appears-to-be-outdated","topic_title":"Discourse/mail-receiver:release Docker 이미지가 오래된 것으로 보입니다","topic_html_title":"Discourse/mail-receiver:release Docker 이미지가 오래된 것으로 보입니다","category_id":1,"display_username":"scavin","primary_group_name":null,"flair_name":"translators","flair_url":"globe","flair_bg_color":"ddd","flair_color":"111","flair_group_id":50,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Plugin Author","title_is_group":false,"bookmarked":false,"raw":"## Update: I tested the current `main` branch\n\nI built the current `main` branch locally and found another issue.\n\nThe old Docker Hub `release` image still runs the old fast-rejection code and fails during RCPT with:\n\n```text\n450 4.7.1 Recipient address rejected: Internal error, API request failed\n```\n\nHowever, the current `main` branch has already removed the `smtp_should_reject` / fast-rejection implementation. After building `main`, Postfix instead fails with:\n\n```text\nwarning: connect to private/policy: No such file or directory\n451 4.3.5 Recipient address rejected: Server configuration problem\n```\n\nI traced this to two remaining references in the `Dockerfile`:\n\n```text\ncheck_policy_service unix:private/policy\n```\n\nThe policy service itself has been removed, but `smtpd_recipient_restrictions` still references its socket.\n\nI removed `unix:private/policy` from `smtpd_recipient_restrictions`, rebuilt the image, and incoming SMTP mail was then accepted successfully.\n\nAfter switching to a Global API Key, delivery to Discourse also succeeded:\n\n```text\ndsn=2.0.0, status=sent (delivered via discourse service)\n```\n\nSo there seem to be two separate issues:\n\n1. The published `discourse/mail-receiver:release` image is outdated and still contains the old fast-rejection implementation.\n2. The current `main` branch removed that implementation, but the `Dockerfile` still configures Postfix to use `unix:private/policy`.\n\nThere may also be a separate issue with granular API keys: a key scoped only to `receive emails` returned HTTP 404 from `/admin/email/handle_mail`, while a Global API Key returned HTTP 200.\n\nI can submit a PR for the two stale `private/policy` references in the `Dockerfile` if that would be helpful.","actions_summary":[{"id":2,"count":2}],"moderator":false,"admin":false,"staff":false,"user_id":14617,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"업데이트: 현재 main 브랜치 테스트\n현재 main 브랜치를 로컬에서 빌드하여 또 다른 문제를 발견했습니다. \n기존 Docker Hub의 release 이미지는 여전히旧的 빠른 거부(fast-rejection) 코드를 실행하며, RCPT 단계에서 다음과 같은 오류로 실패합니다: \n450 4.7.1 Recipient address rejected: Internal error, API request failed\n\n그러나 현재 main 브랜치에서는 이미 smtp_should_reject / 빠른 거부 구현이 제거되었습니다. main을 …","truncated":true,"post_url":"/t/discourse-mail-receiver-release-docker-image-appears-to-be-outdated/411734/2","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":2}],"current_user_reaction":null,"reaction_users_count":2,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034501,"name":"system","username":"system","avatar_template":"/user_avatar/meta.discourse.org/system/{size}/443519_2.png","created_at":"2026-09-06T05:02:04.245Z","cooked":"

Today on meta.discourse.org…

\n

Key Stats

\n

In the last 24 hours, meta.discourse.org saw 54 posts across 20 topics, with 38 likes given out.

\n

Top users by activity:

\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
UserPostsLikes
Moin510
Ed_S44
Ethsim283
Mcwumbly23
Jagster42
Emilio32
LordOfBikes12
Sterretje12
Ecki41
NateDhaliwal31
\n

Interesting Topics

\n

#Feature

\n\n

Support

\n\n

#Plugin

\n\n

#Announcements

\n\n

ux

\n\n

bug

\n\n

#Theme component

\n\n

#Self-hosting

\n\n

Activity by the Team Group

\n

Members of the Team group were active across several discussions over the past 24 hours:

\n\n

With all the talk of permanent deletion, mysterious build tags, and 500-error ghosts, yesterday was a good reminder that even the most “gone forever” forum posts can still leave a trail of discussion behind them — so maybe think twice before asking for that delete button.

","post_number":949,"post_type":1,"posts_count":718,"updated_at":"2026-09-06T05:02:04.245Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":2,"readers_count":1,"score":0.4,"yours":false,"topic_id":291851,"topic_slug":"daily-summary-5am-utc","topic_title":"일일 요약 (UTC 오전 5시)","topic_html_title":"일일 요약 (UTC 오전 5시)","category_id":157,"display_username":"system","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"# Today on meta.discourse.org...\n\n## Key Stats\n\nIn the last 24 hours, meta.discourse.org saw **54 posts** across **20 topics**, with **38 likes** given out.\n\n**Top users by activity:**\n\n| User | Posts | Likes |\n|---|---|---|\n| Moin | 5 | 10 |\n| Ed_S | 4 | 4 |\n| Ethsim2 | 8 | 3 |\n| Mcwumbly | 2 | 3 |\n| Jagster | 4 | 2 |\n| Emilio | 3 | 2 |\n| LordOfBikes | 1 | 2 |\n| Sterretje | 1 | 2 |\n| Ecki | 4 | 1 |\n| NateDhaliwal | 3 | 1 |\n\n## Interesting Topics\n\n### #Feature\n\n- **Allow user to delete their own topic at any time** — Emilio [asked](https://meta.discourse.org/t/-/411689/1?silent=true) for an end to the arbitrary 24-hour self-deletion window, and Rubi [questioned the reasoning](https://meta.discourse.org/t/-/411689/2?silent=true) behind it. Moin [pointed to the hardcoded Guardian limit](https://meta.discourse.org/t/-/411689/10?silent=true), while Ethsim2 [suggested making the window configurable](https://meta.discourse.org/t/-/411689/12?silent=true) for unanswered topics. Jagster [also compared the idea to Facebook groups](https://meta.discourse.org/t/-/411689/6?silent=true), where deleting a thread can delete everyone's replies.\n\n- **Actually delete permanently without all the obstacles** — Ethsim2 [worked through](https://meta.discourse.org/t/-/411687/2?silent=true) the current permanent-deletion restrictions and eventually [submitted a ready-for-review PR](https://meta.discourse.org/t/-/411687/4?silent=true) adding a per-admin opt-in to permanently delete a topic and all remaining posts, including Staff Action Logging and an extra confirmation warning ([read more](https://meta.discourse.org/t/-/411687/3?silent=true)).\n\n- **Combining Category types** — A long-running #solved, #topic-voting, and #events discussion resurfaced as Ecki [asked whether solution types can be tag-based](https://meta.discourse.org/t/-/409045/6?silent=true), Moin [mentioned 0](https://meta.discourse.org/t/-/409045/8?silent=true), and Satonotdead [supported making the “Me too” button switchable](https://meta.discourse.org/t/-/409045/7?silent=true).\n\n### #Support\n\n- **Is anyone experiencing an odd spam user attack?** — LordOfBikes [detailed](https://meta.discourse.org/t/-/404427/16?silent=true) a rising wave of cloud-hosted spam registrations and started blocking /24 networks from providers. One1 [recommended hCaptcha](https://meta.discourse.org/t/-/404427/18?silent=true) after it eliminated the same spam pattern for their site, and Ed_S [experimented with a required user field](https://meta.discourse.org/t/-/404427/19?silent=true) to help moderators spot bad applications. Moin [suggested checking 1 and 2](https://meta.discourse.org/t/-/404427/21?silent=true) to give moderators better review tools ([read more](https://meta.discourse.org/t/-/404427/17?silent=true)).\n\n- **Randomly attached tags** — Ecki [reported](https://meta.discourse.org/t/-/411729/1?silent=true) an annoying mystery third tag being added to posts, seemingly without human action. Moin [asked whether a tag group requires a parent tag](https://meta.discourse.org/t/-/411729/2?silent=true), and Ecki [said that wasn't the case](https://meta.discourse.org/t/-/411729/3?silent=true), leaving the cause still unexplained.\n\n### #Plugin\n\n- **Discourse Boards** — A self-hosted user [couldn’t find the Boards plugin](https://meta.discourse.org/t/-/411414/3?silent=true) after updating to 2026.9. Moin [explained that Boards is bundled with core](https://meta.discourse.org/t/-/411414/4?silent=true) but only appears in builds after the merge, and that it can be enabled experimentally through **Upcoming Changes** ([read more](https://meta.discourse.org/t/-/411414/1?silent=true)).\n\n### #Announcements\n\n- **Easier account signup using email codes** — Thisisjoshjones [asked](https://meta.discourse.org/t/-/407068/29?silent=true) whether the email-code signup flow could also be applied to the invitation landing page, and Mcwumbly [linked to in-progress work](https://meta.discourse.org/t/-/407068/30?silent=true) on exactly that ([read more](https://meta.discourse.org/t/-/407068/1?silent=true)).\n\n- **Introducing Upcoming Changes** — Ethsim2 [asked](https://meta.discourse.org/t/-/392894/50?silent=true) whether opting out of **Dashboard improvements** would restore the old happy/neutral/sad status icons. Mcwumbly [confirmed the old dashboard is going away completely](https://meta.discourse.org/t/-/392894/52?silent=true) once the change becomes permanent, and pointed to a redesigned system section for self-hosters ([read more](https://meta.discourse.org/t/-/392894/51?silent=true)).\n\n- **Voice: Discord-style voice and video rooms** — Jagster [asked how to remove rooms](https://meta.discourse.org/t/-/411337/27?silent=true) from the new bundled voice feature. Satonotdead [pointed them toward the plugin’s rooms tab in settings](https://meta.discourse.org/t/-/411337/28?silent=true), and Jagster [confirmed that worked](https://meta.discourse.org/t/-/411337/29?silent=true) ([read more](https://meta.discourse.org/t/-/411337/1?silent=true)).\n\n- **PostgreSQL 18 update for self-hosters** — AstonJ [reported a successful upgrade](https://meta.discourse.org/t/-/406194/85?silent=true) on a dual-container server, following Lilly’s advice about upgrading and checking disk space first ([read more](https://meta.discourse.org/t/-/406194/1?silent=true)).\n\n### #UX\n\n- **Moderation yes button after suspending user** — Sterretje [reported](https://meta.discourse.org/t/-/411693/1?silent=true) a leftover “Yes” button remaining in the review queue after suspending a spam user. Per1234 [narrowed it down](https://meta.discourse.org/t/-/411693/3?silent=true) to the dedicated reviewable page, noting it does not appear on the general `/review` listing ([read more](https://meta.discourse.org/t/-/411693/2?silent=true)).\n\n### #Bug\n\n- **Discourse-events can cause 500 when deleting a topic** — Ethsim2 [encountered](https://meta.discourse.org/t/-/411731/1?silent=true) a `NameError` from `DiscourseEvents::Calendar::Extractor` while deleting a topic in a development instance, triggered by the plugin’s `:post_destroyed` callback and possibly related to development-mode reloading.\n\n- **Regression: new check_username rate limit can block signup** — Southpaw [thanked @HBP](https://meta.discourse.org/t/-/411646/4?silent=true) for a detailed report and confirmed “we have a fix in the works” ([read more](https://meta.discourse.org/t/-/411646/1?silent=true)).\n\n### #Theme component\n\n- **External Link Shield – Exit Confirmation & Trust Gating** — Satonotdead [praised the component](https://meta.discourse.org/t/-/392962/6?silent=true) for covering their external-link use cases, but questioned whether a lock icon is the right metaphor for *trusted* external links, and suggested moving the icons to the right as a common standard ([read more](https://meta.discourse.org/t/-/392962/1?silent=true)).\n\n### #Self-hosting\n\n- **Solving Gemini API key errors in Discourse** — Karthik_K1 [resolved](https://meta.discourse.org/t/-/411545/17?silent=true) their AI key configuration issue by switching to a lighter model, noting the LiteLLM workaround was good enough and that latency disappeared after the change ([read more](https://meta.discourse.org/t/-/411545/16?silent=true)).\n\n## Activity by the Team Group\n\nMembers of the Team group were active across several discussions over the past 24 hours:\n\n- Mcwumbly [clarified how the **Discourse Boards** plugin is bundled with core](https://meta.discourse.org/t/-/411414/4?silent=true), [confirmed the legacy admin dashboard will be removed](https://meta.discourse.org/t/-/392894/52?silent=true) once **Dashboard improvements** is permanent, and [linked to in-progress work](https://meta.discourse.org/t/-/407068/30?silent=true) on invitation landing pages using email codes.\n\n- Southpaw [acknowledged the check_username rate-limit regression](https://meta.discourse.org/t/-/411646/4?silent=true) and said a fix is already in the works.\n\n- Moin [cited the hardcoded topic-deletion limit in Guardian](https://meta.discourse.org/t/-/411689/10?silent=true), [helped clarify moderator access to email/IP data](https://meta.discourse.org/t/-/404427/21?silent=true), [explained the availability of Boards](https://meta.discourse.org/t/-/411414/4?silent=true), and [asked a useful question about tag groups](https://meta.discourse.org/t/-/411729/2?silent=true).\n\nWith all the talk of permanent deletion, mysterious build tags, and 500-error ghosts, yesterday was a good reminder that even the most “gone forever” forum posts can still leave a trail of discussion behind them — so maybe think twice before asking for that delete button.","actions_summary":[],"moderator":true,"admin":true,"staff":true,"user_id":-1,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Today on meta.discourse.org…\nKey Stats\nIn the last 24 hours, meta.discourse.org saw 54 posts across 20 topics, with 38 likes given out. \nTop users by activity: \n\n\n\n\nUser\nPosts\nLikes\n\n\n\n\nMoin\n5\n10\n\n\nEd_S\n4\n4\n\n\nEthsim2\n8\n3\n\n\nMcwumbly\n2\n3\n\n\nJagster\n4\n2\n\n\nEmilio\n3\n2\n\n\nLordOfBikes\n1\n2\n\n\nSterretje\n1\n2\n\n\nE…","truncated":true,"post_url":"/t/daily-summary-5am-utc/291851/949","locale":null,"is_localized":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034500,"name":"scavin","username":"scavin","avatar_template":"/user_avatar/meta.discourse.org/scavin/{size}/115938_2.png","created_at":"2026-09-06T04:30:12.962Z","cooked":"

안녕하세요,

\n

공식 discourse/mail-receiver:release Docker 이미지가 무시되어 꽤 오랜 시간 동안 재빌드되지 않은 것 같습니다.

\n

GitHub 저장소는 여전히 적극적으로 유지 관리되고 있습니다:

\n\n\n

그러나 공식 Docker 이미지는:

\n
discourse/mail-receiver:release\n
\n

거의 2년 전에 빌드된 것으로 보입니다.

\n

이것이 현재 버전의 Discourse와 호환성 문제를 일으키는 것 같습니다.

\n

제 경우, 수신 이메일은 메일 리시버에 성공적으로 도달하지만, RCPT TO 단계에서 다음과 같이 거부됩니다:

\n
450 4.7.1 Recipient address rejected: Internal error, API request failed\n
\n

오래된 Docker 이미지는 여전히 smtp_should_reject / 빠른 거부(fast-rejection) 메커니즘을 사용하고 있는 것으로 보입니다.

\n

그러나 현재 Discourse 소스에는 다음과 같은 주석이 포함되어 있습니다:

\n
# this endpoint has been broken for years\n# and was used only in the public mail-receiver's fast rejection code,\n# which is removed in https://github.com/discourse/mail-receiver/pull/33\n
\n

PR #33은 이미 mail-receiver에서 해당 빠른 거부 코드를 제거했지만, 이러한 변경 사항은 현재 공개된 discourse/mail-receiver:release 이미지에 포함되지 않은 것으로 보입니다.

\n

공식 메일 리시버 문서/README는 여전히 사용자에게 다음을 사용하도록 안내하고 있습니다:

\n
discourse/mail-receiver:release\n
\n

따라서 최근 변경 사항 이후 Docker 이미지 게시 과정이 단순히 누락되었는지 궁금합니다.

\n

새로운 discourse/mail-receiver:release 이미지가 빌드되고 게시되어야 하는지 확인해 주시겠습니까?

\n

감사합니다!

","post_number":1,"post_type":1,"posts_count":3,"updated_at":"2026-09-06T04:30:12.962Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":8,"reads":18,"readers_count":17,"score":43.6,"yours":false,"topic_id":411734,"topic_slug":"discourse-mail-receiver-release-docker-image-appears-to-be-outdated","topic_title":"Discourse/mail-receiver:release Docker 이미지가 오래된 것으로 보입니다","topic_html_title":"Discourse/mail-receiver:release Docker 이미지가 오래된 것으로 보입니다","category_id":1,"display_username":"scavin","primary_group_name":null,"flair_name":"translators","flair_url":"globe","flair_bg_color":"ddd","flair_color":"111","flair_group_id":50,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Plugin Author","title_is_group":false,"bookmarked":false,"raw":"Hi,\n\nI think the official `discourse/mail-receiver:release` Docker image may have been overlooked and has not been rebuilt for quite some time.\n\nThe GitHub repository is still actively maintained:\n\nhttps://github.com/discourse/mail-receiver\n\nHowever, the official Docker image:\n\n```text\ndiscourse/mail-receiver:release\n```\n\nappears to have been built almost **2 years ago**.\n\nThis seems to cause compatibility problems with current versions of Discourse.\n\nIn my case, incoming email reaches the mail receiver successfully, but it is rejected during `RCPT TO` with:\n\n```text\n450 4.7.1 Recipient address rejected: Internal error, API request failed\n```\n\nThe old Docker image still appears to use the `smtp_should_reject` / fast-rejection mechanism.\n\nHowever, the current Discourse source contains this comment:\n\n```ruby\n# this endpoint has been broken for years\n# and was used only in the public mail-receiver's fast rejection code,\n# which is removed in https://github.com/discourse/mail-receiver/pull/33\n```\n\nPR #33 has already removed that fast-rejection code from `mail-receiver`, but those changes do not appear to be included in the currently published `discourse/mail-receiver:release` image.\n\nThe official mail-receiver documentation/README still instructs users to use:\n\n```text\ndiscourse/mail-receiver:release\n```\n\nSo I wonder if the Docker image publishing process was simply missed after the recent changes.\n\nCould you please check whether a new `discourse/mail-receiver:release` image needs to be built and published?\n\nThanks!","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":14617,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"안녕하세요, \n공식 discourse/mail-receiver:release Docker 이미지가 무시되어 꽤 오랜 시간 동안 재빌드되지 않은 것 같습니다. \nGitHub 저장소는 여전히 적극적으로 유지 관리되고 있습니다: \n\n\n그러나 공식 Docker 이미지는: \ndiscourse/mail-receiver:release\n\n거의 2년 전에 빌드된 것으로 보입니다. \n이것이 현재 버전의 Discourse와 호환성 문제를 일으키는 것 같습니다. \n제 경우, 수신 이메일은 메일 리시버에 성공적으로 도달하지만, RCPT TO 단계에서 다음…","truncated":true,"post_url":"/t/discourse-mail-receiver-release-docker-image-appears-to-be-outdated/411734/1","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"calendar_details":[],"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null,"can_vote":false},{"id":2034498,"name":"AstonJ","username":"AstonJ","avatar_template":"/user_avatar/meta.discourse.org/astonj/{size}/215041_2.png","created_at":"2026-09-06T02:46:42.495Z","cooked":"\n

릴리 감사합니다. 조금 전에 업그레이드를 했는데 모두 잘 된 것 같습니다 \":+1:\"

","post_number":85,"post_type":1,"posts_count":83,"updated_at":"2026-09-06T02:46:42.495Z","reply_count":0,"reply_to_post_number":81,"quote_count":1,"incoming_link_count":1,"reads":20,"readers_count":19,"score":24.0,"yours":false,"topic_id":406194,"topic_slug":"postgresql-18-update-for-self-hosters","topic_title":"자체 호스팅 사용자를 위한 PostgreSQL 18 업데이트","topic_html_title":"자체 호스팅 사용자를 위한 PostgreSQL 18 업데이트","category_id":67,"display_username":"AstonJ","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","bookmarked":false,"raw":"[quote=\"Lilly, post:81, topic:406194, full:true\"]\nyes i did upgrades on dual containers on one server a couple of weeks ago (on a russian server too). no issues at all but make sure you have enough disk space first.\n[/quote]\n\nThanks Lilly, did the upgrade earlier and it all seems to have gone ok :+1:","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":704,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"릴리 감사합니다. 조금 전에 업그레이드를 했는데 모두 잘 된 것 같습니다 :+1:","truncated":true,"post_url":"/t/postgresql-18-update-for-self-hosters/406194/85","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034488,"name":"Ethan ","username":"Ethsim2","avatar_template":"/user_avatar/meta.discourse.org/ethsim2/{size}/522255_2.png","created_at":"2026-09-06T01:16:12.241Z","cooked":"

로컬 개발 인스턴스에서 무관한 토픽 삭제 관련 변경 사항을 테스트하던 중, 토픽을 삭제하려고 했더니 500 Internal Server Error가 반환되었습니다.

\n

해당 에러가 발생한 개발 인스턴스는 정확히 이 Discourse 커밋을 실행 중이었습니다:

\n\n\n

\"image\"
image2048×1060 449 KB

\n

요청은 다음과 같았습니다:

\n
DELETE /t/35\n
\n

그리고 예외는 discourse-events 플러그인의 :post_destroyed 콜백에서 발생했습니다:

\n
NameError (uninitialized constant DiscourseEvents::Calendar::Extractor)\n\nplugins/discourse-events/plugin.rb:639:in 'block (2 levels) in Plugin::Instance#activate!'\nlib/plugin/instance.rb:676:in 'block in Plugin::Instance#on'\nlib/discourse_event.rb:13:in 'block in DiscourseEvent.trigger'\nlib/discourse_event.rb:12:in 'DiscourseEvent.trigger'\nlib/post_destroyer.rb:91:in 'PostDestroyer#destroy'\napp/controllers/topics_controller.rb:818:in 'TopicsController#destroy'\n
\n

해당 콜백은 다음을 호출하려고 시도하는 것으로 보입니다:

\n
DiscourseEvents::Calendar::Extractor.destroy(post)\n
\n

전체 에러 페이지에는 다음과 같이 보고됩니다:

\n
NameError (uninitialized constant DiscourseEvents::Calendar::Extractor)\n
\n

브라우저는 PostDestroyer#destroy가 이미 :post_destroyed를 트리거하는 지점에 도달했음에도 불구하고 500 오류를 수신합니다. 따라서 콜백이 예외를 발생시키기 전에 삭제가 이미 적용되었을 수 있습니다.

\n

이것은 개발 환경에서 발생했습니다. DiscourseEvents::Calendar::Extractor는 일반적으로 events 플러그인에 의해 제공되므로, 구현 자체가 누락된 것이 아니라 개발 모드 리로딩/플러그인 상태와 관련이 있을 수 있는지 궁금합니다.

\n

당시 저는 무관한 토픽 삭제 코드 작업을 하고 있었지만, 예외 자체는 discourse-events의 :post_destroyed 핸들러 내부에서 완전히 발생하고 있습니다.

\n

혹시 다른 분들도 개발 인스턴스에서 DiscourseEvents::Calendar::Extractor가 정의되지 않는 상황을 경험해 보셨나요? 이것이 개발 리로딩/플러그인 상태와 관련이 있을 수 있으며, 아니면 :post_destroyed 콜백이 추출기를 다른 방식으로 로드해야 하는 것일까요?

","post_number":1,"post_type":1,"posts_count":1,"updated_at":"2026-09-06T01:25:30.579Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":6,"reads":10,"readers_count":9,"score":47.0,"yours":false,"topic_id":411731,"topic_slug":"discourse-events-can-cause-500-when-deleting-a-topic-in-development-uninitialized-calendar-extractor","topic_title":"개발 환경에서 토픽 삭제 시 discourse-events로 인해 500 오류 발생: Calendar::Extractor 초기화 안 됨","topic_html_title":"개발 환경에서 토픽 삭제 시 discourse-events로 인해 500 오류 발생: Calendar::Extractor 초기화 안 됨","category_id":1,"display_username":"Ethan ","primary_group_name":null,"flair_name":"theme_authors","flair_url":"paintbrush","flair_bg_color":"ddd","flair_color":"111","flair_group_id":73,"badges_granted":[],"version":2,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Tester","title_is_group":false,"bookmarked":false,"raw":"While testing some unrelated topic-deletion changes in a local development instance, deleting a topic returned a **500 Internal Server Error**.\n\nThe development instance which produced the error was running this exact Discourse commit:\n\nhttps://github.com/Ethsim12/discourse/commit/58070a6173a7ba162dbc8ec1165836043290d5ab\n\n![image|690x357](upload://pxAQ1bD98lguWosARW2VJIHgYFR.jpeg)\n\n\nThe request was:\n\n```text\nDELETE /t/35\n```\n\nand the exception is coming from the `discourse-events` `:post_destroyed` callback:\n\n```text\nNameError (uninitialized constant DiscourseEvents::Calendar::Extractor)\n\nplugins/discourse-events/plugin.rb:639:in 'block (2 levels) in Plugin::Instance#activate!'\nlib/plugin/instance.rb:676:in 'block in Plugin::Instance#on'\nlib/discourse_event.rb:13:in 'block in DiscourseEvent.trigger'\nlib/discourse_event.rb:12:in 'DiscourseEvent.trigger'\nlib/post_destroyer.rb:91:in 'PostDestroyer#destroy'\napp/controllers/topics_controller.rb:818:in 'TopicsController#destroy'\n```\n\nThe relevant callback appears to be attempting to call:\n\n```ruby\nDiscourseEvents::Calendar::Extractor.destroy(post)\n```\n\nThe full error page reports:\n\n```text\nNameError (uninitialized constant DiscourseEvents::Calendar::Extractor)\n```\n\nThe browser consequently receives a 500 even though `PostDestroyer#destroy` has already reached the point where it triggers `:post_destroyed`, so the deletion may already have been applied before the callback raises.\n\nThis occurred in development. `DiscourseEvents::Calendar::Extractor` is normally provided by #events, so I’m wondering whether this could be related to development-mode reloading/plugin state rather than the implementation itself being absent.\n\nI was working on unrelated topic-deletion code at the time, but the exception itself is entirely within the `discourse-events` `:post_destroyed` handler.\n\nHas anyone else encountered `DiscourseEvents::Calendar::Extractor` becoming undefined in a development instance? Could this be related to development reloading/plugin state, or should the `:post_destroyed` callback be loading the extractor differently?","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":160471,"hidden":false,"trust_level":1,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"로컬 개발 인스턴스에서 무관한 토픽 삭제 관련 변경 사항을 테스트하던 중, 토픽을 삭제하려고 했더니 500 Internal Server Error가 반환되었습니다. \n해당 에러가 발생한 개발 인스턴스는 정확히 이 Discourse 커밋을 실행 중이었습니다: \n\n\n [image] \n요청은 다음과 같았습니다: \nDELETE /t/35\n\n그리고 예외는 discourse-events 플러그인의 :post_destroyed 콜백에서 발생했습니다: \nNameError (uninitialized constant DiscourseEvents::C…","truncated":true,"post_url":"/t/discourse-events-can-cause-500-when-deleting-a-topic-in-development-uninitialized-calendar-extractor/411731/1","locale":"en","is_localized":true,"language":"en","localization_outdated":true,"customer_flair_customer":null,"event":null,"calendar_details":[],"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null,"can_vote":false},{"id":2034484,"name":"Ethan ","username":"Ethsim2","avatar_template":"/user_avatar/meta.discourse.org/ethsim2/{size}/522255_2.png","created_at":"2026-09-06T00:46:22.978Z","cooked":"\n

저는 이것이 여기서 중요한 구별점이라고 생각합니다. 기존 구현에서는 이미 일반 사용자가 답글이 없는 경우에만 자신의 주제를 삭제할 수 있도록 제한하고 있습니다:

\n\n\n

따라서 더 구체적인 기능 요청은 현재 하드코딩된 24.hours를 설정 가능하도록 하고, 기존 posts_count <= 1 제한을 유지하는 것으로 충분할 수 있습니다. 기본값은 24시간으로 유지하되, 관리자가 더 긴 기간을 선택하거나, 답이 없는 주제의 삭제를 무제한으로 허용할 수 있도록 할 수 있습니다.

\n\n

GDPR이 이 기능이 필요한 진정한 이유라고 생각하지 않습니다. 삭제권은 절대적이지 않으며, 사용자가 게시한 모든 콘텐츠에 대해 무제한의 셀프 서비스 삭제 옵션을 제공해야 한다는 것을 의미하지 않습니다.

\n

기존 24시간 제한의 설정 가능성은 이 기능 자체에 대한 충분한 논거로 보입니다.

","post_number":12,"post_type":1,"posts_count":12,"updated_at":"2026-09-06T00:47:03.155Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":13,"readers_count":12,"score":37.6,"yours":false,"topic_id":411689,"topic_slug":"allow-user-to-delete-their-own-topic-at-any-time","topic_title":"사용자가 언제든지 자신의 주제를 삭제할 수 있도록 허용","topic_html_title":"사용자가 언제든지 자신의 주제를 삭제할 수 있도록 허용","category_id":2,"display_username":"Ethan ","primary_group_name":null,"flair_name":"theme_authors","flair_url":"paintbrush","flair_bg_color":"ddd","flair_color":"111","flair_group_id":73,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Tester","title_is_group":false,"bookmarked":false,"raw":"[quote=“Ed_S, post:8, topic:411689”]\nStill, it might be clearer as a feature request that it’s unanswered topics which you’d like to make deletable.\n[/quote]\n\nI think that’s the important distinction here. The existing implementation already restricts ordinary users to deleting their own topic only when it has no replies:\n\nhttps://github.com/discourse/discourse/blob/5e9779d4cd418af07a6ed01005d558eda76f2f69/lib/guardian/topic_guardian.rb#L383-L385\n\nSo the narrower feature request could simply be to make the currently hardcoded `24.hours` configurable, while retaining the existing `posts_count <= 1` restriction. That could default to 24 hours but allow admins to choose a longer period, or potentially unlimited deletion of unanswered topics.\n\n[quote=“ecki, post:11, topic:411689”]\nIt’s much easier than to deal with GDPR sues later on - let’s have user their data soverenity\n[/quote]\n\nI don’t think GDPR is really the reason this feature is needed. The right to erasure is not absolute, and it doesn’t mean forum software has to provide an unlimited self-service option to delete any content a user has posted.\n\nThe configurability of the existing 24-hour restriction seems like a sufficient argument for the feature on its own.","actions_summary":[{"id":2,"count":2}],"moderator":false,"admin":false,"staff":false,"user_id":160471,"hidden":false,"trust_level":1,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"저는 이것이 여기서 중요한 구별점이라고 생각합니다. 기존 구현에서는 이미 일반 사용자가 답글이 없는 경우에만 자신의 주제를 삭제할 수 있도록 제한하고 있습니다: \n\n\n따라서 더 구체적인 기능 요청은 현재 하드코딩된 24.hours를 설정 가능하도록 하고, 기존 posts_count <= 1 제한을 유지하는 것으로 충분할 수 있습니다. 기본값은 24시간으로 유지하되, 관리자가 더 긴 기간을 선택하거나, 답이 없는 주제의 삭제를 무제한으로 허용할 수 있도록 할 수 있습니다. \n\nGDPR이 이 기능이 필요한 진정한 이유라고 생각하지 않…","truncated":true,"post_url":"/t/allow-user-to-delete-their-own-topic-at-any-time/411689/12","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":2}],"current_user_reaction":null,"reaction_users_count":2,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034481,"name":"","username":"satonotdead","avatar_template":"/user_avatar/meta.discourse.org/satonotdead/{size}/447830_2.png","created_at":"2026-09-06T00:11:44.355Z","cooked":"

Don, 정말 좋습니다. 만들어서 공유해 주셔서 감사합니다!

\n\n

신뢰할 수 있는 외부 링크에 왜 잠금 아이콘을 사용하는지 궁금합니다. 허용된 링크인데 '잠김’으로 해석될 수 있을 것 같아서요. \":sweat_smile:\"

\n

이 컴포넌트를 사용해 보겠습니다. 외부 링크에 대한 우리의 모든 사용 사례를 커버하는 것 같습니다. 또한, 일반적인 표준이 오른쪽에 아이콘을 배치하는 것임을 알고 있으므로 아이콘을 오른쪽으로 이동시키는 것도 시도해 보겠습니다.

\n

항상 그렇듯이 제 생각을 공유하는 것뿐이며, 이를 통해 TC가 개선되기를 바랍니다.

","post_number":6,"post_type":1,"posts_count":10,"updated_at":"2026-09-06T00:12:09.264Z","reply_count":1,"reply_to_post_number":null,"quote_count":1,"incoming_link_count":0,"reads":14,"readers_count":13,"score":37.8,"yours":false,"topic_id":392962,"topic_slug":"external-link-shield-exit-confirmation-trust-gating","topic_title":"외부 링크 보호 – 종료 확인 및 신뢰 게이트","topic_html_title":"외부 링크 보호 – 종료 확인 및 신뢰 게이트","category_id":120,"display_username":"","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","bookmarked":false,"raw":"This is great Don, thanks for building and sharing it!\n\n[quote=\"Don, post:1, topic:392962\"]\n* **Trusted external links** → lock icon (success color)\n[/quote]\nI wonder why the trusted external links uses a lock icon? I mean, it can be interpreted as \"locked\" 😅 when they are allowed.\n\nI will try this component; it seems to cover all our use cases for external links. I will also try moving the icons to the right because I understand it is the common standard.\n\nLike always, just sharing my thoughts and glad if the TC can be improved with them.","actions_summary":[{"id":2,"count":2}],"moderator":false,"admin":false,"staff":false,"user_id":71041,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Don, 정말 좋습니다. 만들어서 공유해 주셔서 감사합니다! \n\n신뢰할 수 있는 외부 링크에 왜 잠금 아이콘을 사용하는지 궁금합니다. 허용된 링크인데 '잠김’으로 해석될 수 있을 것 같아서요. :sweat_smile: \n이 컴포넌트를 사용해 보겠습니다. 외부 링크에 대한 우리의 모든 사용 사례를 커버하는 것 같습니다. 또한, 일반적인 표준이 오른쪽에 아이콘을 배치하는 것임을 알고 있으므로 아이콘을 오른쪽으로 이동시키는 것도 시도해 보겠습니다. \n항상 그렇듯이 제 생각을 공유하는 것뿐이며, 이를 통해 TC가 개선되기를 바랍니다.","truncated":true,"post_url":"/t/external-link-shield-exit-confirmation-trust-gating/392962/6","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":2}],"current_user_reaction":null,"reaction_users_count":2,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034480,"name":"","username":"Moin","avatar_template":"/user_avatar/meta.discourse.org/moin/{size}/554653_2.png","created_at":"2026-09-05T22:16:40.166Z","cooked":"

enable_solved_tags 설정이 있습니다. 하지만 이 설정이 “나도” 버튼을 지원하는지는 알 수 없습니다.

\n

새로운 보고 도구는 카테고리별로 설정된 solved 플러그인에 한정되어 있는 것 같습니다. 이로 인해 다른 최근 기능들도 영향을 받는 것일지 궁금해집니다.

\n","post_number":8,"post_type":1,"posts_count":8,"updated_at":"2026-09-05T22:16:40.166Z","reply_count":0,"reply_to_post_number":6,"quote_count":0,"incoming_link_count":0,"reads":10,"readers_count":9,"score":17.0,"yours":false,"topic_id":409045,"topic_slug":"combining-category-types","topic_title":"카테고리 유형 결합","topic_html_title":"카테고리 유형 결합","category_id":2,"display_username":"","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Kluges Köpfchen","title_is_group":false,"reply_to_user":{"id":117384,"username":"ecki","name":"Bernd","avatar_template":"/user_avatar/meta.discourse.org/ecki/{size}/264025_2.png"},"bookmarked":false,"raw":"There is the `enable_solved_tags` setting. But I don't know if that supports the \"me too\" button.\n\nThe new reporting tool seems to be limited to the solved plugin being set up by category. This makes me wonder if other recent features are affected too.\n[quote=\"lindsey, post:1, topic:411397\"]\n**Note:** The Accepted Solutions report and corresponding dashboard card are only shown in communities with at least one [support category](https://meta.discourse.org/t/easily-create-support-categories-using-the-discourse-solved-plugin/398338).\n[/quote]","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":95552,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"enable_solved_tags 설정이 있습니다. 하지만 이 설정이 “나도” 버튼을 지원하는지는 알 수 없습니다. \n새로운 보고 도구는 카테고리별로 설정된 solved 플러그인에 한정되어 있는 것 같습니다. 이로 인해 다른 최근 기능들도 영향을 받는 것일지 궁금해집니다.","truncated":true,"post_url":"/t/combining-category-types/409045/8","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034479,"name":"","username":"satonotdead","avatar_template":"/user_avatar/meta.discourse.org/satonotdead/{size}/447830_2.png","created_at":"2026-09-05T22:16:29.341Z","cooked":"

이 융합에 동의합니다. 일부 주제에는 ‘나도!’ 옵션과 투표 기능이 모두 있어야 합니다. 둘 다 활성화하거나, 하나만 활성화하거나, 또는 둘 다 비활성화할 수 있도록 전환 가능해야 한다고 생각합니다.

\n

정확한 처리 방법은 잘 모르겠지만, 이 목적은 여기에서 충분히 지지받고 있습니다.

","post_number":7,"post_type":1,"posts_count":8,"updated_at":"2026-09-05T22:16:29.341Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":10,"readers_count":9,"score":2.0,"yours":false,"topic_id":409045,"topic_slug":"combining-category-types","topic_title":"카테고리 유형 결합","topic_html_title":"카테고리 유형 결합","category_id":2,"display_username":"","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","bookmarked":false,"raw":"I am agree with this fusion, some topics should have the 'Me too' option and voting as well. I think it should be switchable for enabling both, one or none of them.\n\nNot sure how to properly handle it but the purpose is really supported here.","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":71041,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"이 융합에 동의합니다. 일부 주제에는 ‘나도!’ 옵션과 투표 기능이 모두 있어야 합니다. 둘 다 활성화하거나, 하나만 활성화하거나, 또는 둘 다 비활성화할 수 있도록 전환 가능해야 한다고 생각합니다. \n정확한 처리 방법은 잘 모르겠지만, 이 목적은 여기에서 충분히 지지받고 있습니다.","truncated":true,"post_url":"/t/combining-category-types/409045/7","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034478,"name":"Bernd","username":"ecki","avatar_template":"/user_avatar/meta.discourse.org/ecki/{size}/264025_2.png","created_at":"2026-09-05T22:12:47.607Z","cooked":"

아니, 적어도 나는 그런 것을 본 적이 없습니다(그리고 그것들은 사실 관련이 없습니다). 테스트 게시물에서도 그런 현상은 일어나지 않습니다. 누군가가 ‘유용하게’ 도와주려고 추가한 줄 알았는데, 가끔은 의외로 매우 빠르게 나타납니다.

","post_number":3,"post_type":1,"posts_count":3,"updated_at":"2026-09-05T22:13:13.474Z","reply_count":0,"reply_to_post_number":2,"quote_count":0,"incoming_link_count":1,"reads":15,"readers_count":14,"score":8.0,"yours":false,"topic_id":411729,"topic_slug":"randomly-attached-tags","topic_title":"무작위로 붙은 태그","topic_html_title":"무작위로 붙은 태그","category_id":6,"display_username":"Bernd","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","reply_to_user":{"id":95552,"username":"Moin","name":"","avatar_template":"/user_avatar/meta.discourse.org/moin/{size}/554653_2.png"},"bookmarked":false,"raw":"No, at least I haven’t seen that (and also they are not really related). It also does not happen on test posts. I already thought it’s someone „helpful“ adding it but it sometimes shows up surprisingly fast","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":117384,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"아니, 적어도 나는 그런 것을 본 적이 없습니다(그리고 그것들은 사실 관련이 없습니다). 테스트 게시물에서도 그런 현상은 일어나지 않습니다. 누군가가 ‘유용하게’ 도와주려고 추가한 줄 알았는데, 가끔은 의외로 매우 빠르게 나타납니다.","truncated":true,"post_url":"/t/randomly-attached-tags/411729/3","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034477,"name":"","username":"Moin","avatar_template":"/user_avatar/meta.discourse.org/moin/{size}/554653_2.png","created_at":"2026-09-05T22:10:36.984Z","cooked":"

해갈(Thirst) 태그를 부모 태그로 설정한 태그 그룹에서, 추가하는 태그 중 하나를 선택한 건가요?

","post_number":2,"post_type":1,"posts_count":3,"updated_at":"2026-09-05T22:10:36.984Z","reply_count":1,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":16,"readers_count":15,"score":8.2,"yours":false,"topic_id":411729,"topic_slug":"randomly-attached-tags","topic_title":"무작위로 붙은 태그","topic_html_title":"무작위로 붙은 태그","category_id":6,"display_username":"","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Kluges Köpfchen","title_is_group":false,"bookmarked":false,"raw":"Is one of the tags you add in a tag group where you configured that the thirst one is required as the parent tag?","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":95552,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"해갈(Thirst) 태그를 부모 태그로 설정한 태그 그룹에서, 추가하는 태그 중 하나를 선택한 건가요?","truncated":true,"post_url":"/t/randomly-attached-tags/411729/2","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034476,"name":"Bernd","username":"ecki","avatar_template":"/user_avatar/meta.discourse.org/ecki/{size}/264025_2.png","created_at":"2026-09-05T22:10:25.257Z","cooked":"

나중에 GDPR 소송을 처리하는 것보다 훨씬 쉽습니다. 사용자에게 데이터 주권을 돌려주도록 합시다.

","post_number":11,"post_type":1,"posts_count":12,"updated_at":"2026-09-05T22:10:25.257Z","reply_count":0,"reply_to_post_number":2,"quote_count":0,"incoming_link_count":0,"reads":15,"readers_count":14,"score":3.0,"yours":false,"topic_id":411689,"topic_slug":"allow-user-to-delete-their-own-topic-at-any-time","topic_title":"사용자가 언제든지 자신의 주제를 삭제할 수 있도록 허용","topic_html_title":"사용자가 언제든지 자신의 주제를 삭제할 수 있도록 허용","category_id":2,"display_username":"Bernd","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","reply_to_user":{"id":176316,"username":"Rubi","name":null,"avatar_template":"https://avatars.discourse-cdn.com/v4/letter/r/7ea924/{size}.png"},"bookmarked":false,"raw":"It’s much easier than to deal with GDPR sues later on - let’s have user their data soverenity","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":117384,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"나중에 GDPR 소송을 처리하는 것보다 훨씬 쉽습니다. 사용자에게 데이터 주권을 돌려주도록 합시다.","truncated":true,"post_url":"/t/allow-user-to-delete-their-own-topic-at-any-time/411689/11","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034475,"name":"Bernd","username":"ecki","avatar_template":"/user_avatar/meta.discourse.org/ecki/{size}/264025_2.png","created_at":"2026-09-05T22:05:49.190Z","cooked":"

아, 실제로 태그를 기반으로 솔루션 유형을 만들 수 있나요? 예를 들어 ‘지원 질문으로 표시’ 같은 거요? 그러면 토론 항목에 '나도’나 ‘해결됨’ 버튼이 없게 되니까 그게 좋겠네요.

","post_number":6,"post_type":1,"posts_count":8,"updated_at":"2026-09-05T22:05:49.190Z","reply_count":1,"reply_to_post_number":5,"quote_count":0,"incoming_link_count":1,"reads":11,"readers_count":10,"score":12.2,"yours":false,"topic_id":409045,"topic_slug":"combining-category-types","topic_title":"카테고리 유형 결합","topic_html_title":"카테고리 유형 결합","category_id":2,"display_username":"Bernd","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","reply_to_user":{"id":95552,"username":"Moin","name":"","avatar_template":"/user_avatar/meta.discourse.org/moin/{size}/554653_2.png"},"bookmarked":false,"raw":"Oh can you actually make solution types based on a tag? Something like „mark it a support question“? That would be cool so discussion entries have no „Me too“ or „mark solved“ buttons","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":117384,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"아, 실제로 태그를 기반으로 솔루션 유형을 만들 수 있나요? 예를 들어 ‘지원 질문으로 표시’ 같은 거요? 그러면 토론 항목에 '나도’나 ‘해결됨’ 버튼이 없게 되니까 그게 좋겠네요.","truncated":true,"post_url":"/t/combining-category-types/409045/6","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034474,"name":"Bernd","username":"ecki","avatar_template":"/user_avatar/meta.discourse.org/ecki/{size}/264025_2.png","created_at":"2026-09-05T22:02:43.298Z","cooked":"

제가 정기적으로 작성하는 게시물 중 일부에 내가 직접 고른 두 개의 태그를 붙여도, 나중에 특정 세 번째 태그가 자동으로 붙어 있는 문제가 있습니다. 해당 태그는 동의어가 아니며, 카테고리에도 설정되어 있지 않습니다. 이 태그가 어디서 오는 걸까요? 처음에는 내가 추가한 태그와 접두사가 같아서 실수로 선택한 줄 알았지만, 주의를 기울여 보니 그런 게 아니었습니다. 이 태그들이 어디서 유입되는지 확인할 수 있는 로그나 테이블이 있을까요?

","post_number":1,"post_type":1,"posts_count":3,"updated_at":"2026-09-05T22:02:43.298Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":2,"reads":16,"readers_count":15,"score":28.2,"yours":false,"topic_id":411729,"topic_slug":"randomly-attached-tags","topic_title":"무작위로 붙은 태그","topic_html_title":"무작위로 붙은 태그","category_id":6,"display_username":"Bernd","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","bookmarked":false,"raw":"I have this annoying problem that some posts I make regularly with 2 hand picked tags later show up with a specific third one. It’s not a synonym and not set on the category. Where can it come from? In the beginning I assumed it was an accidental selection since it has the same prefix as the one I added, but since I pay attention I can say that’s not it. Is there a lot or table where I can find out where they are coming from?","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":117384,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"제가 정기적으로 작성하는 게시물 중 일부에 내가 직접 고른 두 개의 태그를 붙여도, 나중에 특정 세 번째 태그가 자동으로 붙어 있는 문제가 있습니다. 해당 태그는 동의어가 아니며, 카테고리에도 설정되어 있지 않습니다. 이 태그가 어디서 오는 걸까요? 처음에는 내가 추가한 태그와 접두사가 같아서 실수로 선택한 줄 알았지만, 주의를 기울여 보니 그런 게 아니었습니다. 이 태그들이 어디서 유입되는지 확인할 수 있는 로그나 테이블이 있을까요?","truncated":true,"post_url":"/t/randomly-attached-tags/411729/1","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"calendar_details":[],"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null,"can_vote":false},{"id":2034470,"name":"Dave McClure","username":"mcwumbly","avatar_template":"/user_avatar/meta.discourse.org/mcwumbly/{size}/103861_2.png","created_at":"2026-09-05T21:02:59.534Z","cooked":"

우연히도, 그 부분에 대해 여기에서 진행 중인 작업이 있습니다:

\n\n","post_number":30,"post_type":1,"posts_count":19,"updated_at":"2026-09-05T21:02:59.534Z","reply_count":0,"reply_to_post_number":29,"quote_count":0,"incoming_link_count":1,"reads":10,"readers_count":9,"score":22.0,"yours":false,"topic_id":407068,"topic_slug":"easier-account-signup-using-email-codes","topic_title":"이메일 코드를 활용한 간편한 계정 가입","topic_html_title":"이메일 코드를 활용한 간편한 계정 가입","category_id":67,"display_username":"Dave McClure","primary_group_name":"team","flair_name":"team","flair_url":"https://global.discourse-cdn.com/meta/original/3X/e/b/ebee30bd98aef20357e4a177a5a1e45b877ce088.svg","flair_bg_color":"","flair_color":"111","flair_group_id":47,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Director of Product","title_is_group":false,"reply_to_user":{"id":132341,"username":"thisisjoshjones","name":"Joshua Jones","avatar_template":"/user_avatar/meta.discourse.org/thisisjoshjones/{size}/303241_2.png"},"bookmarked":false,"raw":"Coincidentally, there's some work in progress on that front here:\n\nhttps://github.com/discourse/discourse/pull/43138","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":true,"staff":true,"user_id":4263,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"우연히도, 그 부분에 대해 여기에서 진행 중인 작업이 있습니다:","truncated":true,"post_url":"/t/easier-account-signup-using-email-codes/407068/30","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034469,"name":"system","username":"system","avatar_template":"/user_avatar/meta.discourse.org/system/{size}/443519_2.png","created_at":"2026-09-05T21:02:13.771Z","cooked":"

Today on meta.discourse.org…

\n

Key Stats

\n

In the last 24 hours, the community produced 106 new posts across 33 new topics, collecting 85 likes along the way. The top contributors by likes were:

\n\n

Interesting Topics

\n

Support

\n

Apidevlab shared a frustrating Hetzner VPS bootstrap failure after successful installs on Layer7, and Lilly, Ed_S, and Jagster all asked for the full error log, with Lilly noting that unsupported Podman installs will be hard to get help for. read more

\n

In a more niche integration thread, Nicolsdennis explained how he exposed LiveKit status in a client app, building on earlier design comments from Pmusaraj and Falco. read more

\n

General

\n

Nicolsdennis showed off new native voice support in the “mesh” client and a companion app for live-streaming Discourse Voice conversations, complete with screenshots of the voice rooms and LiveKit integration. read more

\n

#Community Building

\n

Per1234 shared a ready-to-import Discourse Update Notifier workflow that automatically posts about new Discourse versions, giving members more transparency about UI changes. read more

\n

In a more philosophical thread, Eisammy celebrated Discourse and the Fediverse as alternatives to attention-driven social media, hoping to still be communicating the same way in ten years. read more

\n

#Feature

\n

Emilio asked for a less painful way to permanently delete topics, and Ethsim2 delivered a full implementation: a per-admin opt-in setting that permanently deletes the topic and all replies, with the PR now ready for review. read more

\n

Happyhappy received a helpful pointer from Heliosurge to the Category Restrictor plugin as a possible way to let category moderators manage user membership without full admin powers. read more

\n

#Announcements

\n

The new bundled Voice rooms continued to generate excitement, with Jagster finally figuring out that rooms are deleted from the settings tab rather than the forum GUI. read more

\n

A discussion about end dates for recurring calendar events led MiniForum to a related feature request: adding recurrence to the per-topic calendar workflow, not just separate Events. read more

\n

Thisisjoshjones asked whether the new email-code signup flow could also be used on the invitations landing page, calling it a big barrier-lowering improvement for communities. read more

\n

bug

\n

Ethsim2 opened a PR and shared a detailed screen recording showing how event date edits should update the topic title correctly.

\n

Stephen reported that expanded markdown tables only allow one checkbox interaction after expansion, flagging the regression for Sam. read more

\n

#Plugin

\n

ProxyTracer announced a new beta with CAPTCHA challenges, independent clearance tokens, and visual analytics for blocking or challenging proxy and VPN traffic. read more

\n

#Sysadmins

\n

Simonk corrected the AWS SES setup guide, warning that raw message delivery must be disabled for SNS bounce notifications to pass Discourse’s validation checks. read more

\n

development

\n

NateDhaliwal asked how to preset a value for FormKit’s composer field, then discovered that using @data={{hash content=...}} on the <Form> component solves it. read more

\n

Activity by the Team Group

\n

Members of the Team group were active across a wide range of threads:

\n\n
\n

From fighting spam bots to making permanent deletion one click easier, the community came out swinging yesterday — just don’t ask us to delete this summary! \":wink:\"

","post_number":975,"post_type":1,"posts_count":717,"updated_at":"2026-09-05T21:02:13.771Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":3,"readers_count":2,"score":0.6,"yours":false,"topic_id":291850,"topic_slug":"daily-summary-9pm-utc","topic_title":"일일 요약 (UTC 오후 9시)","topic_html_title":"일일 요약 (UTC 오후 9시)","category_id":157,"display_username":"system","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"# Today on meta.discourse.org...\n\n## Key Stats\n\nIn the last 24 hours, the community produced **106 new posts** across **33 new topics**, collecting **85 likes** along the way. The top contributors by likes were:\n\n- Ed_S — 9 likes, 5 posts\n- Nicolsdennis — 8 likes, 3 posts\n- Per1234 — 7 likes, 2 posts\n- Lilly — 5 likes, 9 posts\n- Moin — 5 likes, 3 posts\n- Nat — 5 likes, 2 posts\n- Falco — 5 likes, 1 post\n- Jagster — 4 likes, 6 posts\n- Ethsim2 — 3 likes, 11 posts\n- Satonotdead — 3 likes, 6 posts\n\n## Interesting Topics\n\n### #Support\n\nApidevlab shared a [frustrating Hetzner VPS bootstrap failure](https://meta.discourse.org/t/fresh-install-hetzner-vps-failing/411664/1?silent=true) after successful installs on Layer7, and Lilly, Ed_S, and Jagster all asked for the full error log, with Lilly noting that unsupported Podman installs will be hard to get help for. [read more](https://meta.discourse.org/t/fresh-install-hetzner-vps-failing/411664/6?silent=true)\n\nIn a more niche integration thread, Nicolsdennis explained [how he exposed LiveKit status in a client app](https://meta.discourse.org/t/exposing-livekit-status-in-site-settings-serializer/411428/13?silent=true), building on earlier design comments from Pmusaraj and Falco. [read more](https://meta.discourse.org/t/exposing-livekit-status-in-site-settings-serializer/411428/13?silent=true)\n\n### #General\n\nNicolsdennis showed off [new native voice support in the “mesh” client](https://meta.discourse.org/t/a-social-mobile-desktop-client-for-communities-2/408132/30?silent=true) and a companion app for live-streaming Discourse Voice conversations, complete with screenshots of the voice rooms and LiveKit integration. [read more](https://meta.discourse.org/t/a-social-mobile-desktop-client-for-communities-2/408132/30?silent=true)\n\n### #Community Building\n\nPer1234 shared a ready-to-import [Discourse Update Notifier workflow](https://meta.discourse.org/t/show-us-your-workflows/410589/13?silent=true) that automatically posts about new Discourse versions, giving members more transparency about UI changes. [read more](https://meta.discourse.org/t/show-us-your-workflows/410589/13?silent=true)\n\nIn a more philosophical thread, Eisammy celebrated [Discourse and the Fediverse as alternatives to attention-driven social media](https://meta.discourse.org/t/for-the-next-decade-of-the-internet-2026-edition/409454/8?silent=true), hoping to still be communicating the same way in ten years. [read more](https://meta.discourse.org/t/for-the-next-decade-of-the-internet-2026-edition/409454/8?silent=true)\n\n### #Feature\n\nEmilio asked for a less painful way to [permanently delete topics](https://meta.discourse.org/t/actually-delete-permanently-without-all-the-obstacles/411687/1?silent=true), and Ethsim2 delivered a full implementation: a per-admin opt-in setting that permanently deletes the topic and all replies, with [the PR now ready for review](https://meta.discourse.org/t/actually-delete-permanently-without-all-the-obstacles/411687/4?silent=true). [read more](https://meta.discourse.org/t/actually-delete-permanently-without-all-the-obstacles/411687/4?silent=true)\n\nHappyhappy received a helpful pointer from Heliosurge to the [Category Restrictor plugin](https://meta.discourse.org/t/allow-category-moderator-to-add-or-remove-users-from-that-category/411506/8?silent=true) as a possible way to let category moderators manage user membership without full admin powers. [read more](https://meta.discourse.org/t/allow-category-moderator-to-add-or-remove-users-from-that-category/411506/8?silent=true)\n\n### #Announcements\n\nThe new [bundled Voice rooms](https://meta.discourse.org/t/voice-discord-style-voice-and-video-rooms-now-bundled-with-discourse/411337/25?silent=true) continued to generate excitement, with Jagster finally figuring out that rooms are deleted from the settings tab rather than the forum GUI. [read more](https://meta.discourse.org/t/voice-discord-style-voice-and-video-rooms-now-bundled-with-discourse/411337/25?silent=true)\n\nA discussion about [end dates for recurring calendar events](https://meta.discourse.org/t/new-calendar-feature-end-date-for-recurring-events/368527/11?silent=true) led MiniForum to a related feature request: adding recurrence to the per-topic calendar workflow, not just separate Events. [read more](https://meta.discourse.org/t/new-calendar-feature-end-date-for-recurring-events/368527/11?silent=true)\n\nThisisjoshjones asked whether the new [email-code signup flow](https://meta.discourse.org/t/easier-account-signup-using-email-codes/407068/29?silent=true) could also be used on the invitations landing page, calling it a big barrier-lowering improvement for communities. [read more](https://meta.discourse.org/t/easier-account-signup-using-email-codes/407068/29?silent=true)\n\n### #Bug\n\nEthsim2 opened a PR and shared a [detailed screen recording](https://meta.discourse.org/t/editing-event-end-date-post-event-date-on-topic-title-not-updated-since-3-6-0-beta2-update/387466/4?silent=true) showing how event date edits should update the topic title correctly.\n\nStephen reported that [expanded markdown tables](https://meta.discourse.org/t/expanded-markdown-tables-cant-be-interacted-with/364439/4?silent=true) only allow one checkbox interaction after expansion, flagging the regression for Sam. [read more](https://meta.discourse.org/t/expanded-markdown-tables-cant-be-interacted-with/364439/4?silent=true)\n\n### #Plugin\n\nProxyTracer announced a new beta with [CAPTCHA challenges, independent clearance tokens, and visual analytics](https://meta.discourse.org/t/proxytracer-vpn-proxy-blocker/399958/23?silent=true) for blocking or challenging proxy and VPN traffic. [read more](https://meta.discourse.org/t/proxytracer-vpn-proxy-blocker/399958/23?silent=true)\n\n### #Sysadmins\n\nSimonk corrected the [AWS SES setup guide](https://meta.discourse.org/t/configuring-aws-ses-for-outgoing-bounce-and-incoming-email/263604/14?silent=true), warning that raw message delivery must be **disabled** for SNS bounce notifications to pass Discourse’s validation checks. [read more](https://meta.discourse.org/t/configuring-aws-ses-for-outgoing-bounce-and-incoming-email/263604/14?silent=true)\n\n### #Development\n\nNateDhaliwal asked how to [preset a value for FormKit’s composer field](https://meta.discourse.org/t/preset-value-for-composer-field-for-formkit/411695/1?silent=true), then discovered that using `@data={{hash content=...}}` on the `
` component solves it. [read more](https://meta.discourse.org/t/preset-value-for-composer-field-for-formkit/411695/2?silent=true)\n\n## Activity by the Team Group\n\nMembers of the Team group were active across a wide range of threads:\n\n- Moin helped with a [spam user attack thread](https://meta.discourse.org/t/is-anyone-experiencing-an-odd-spam-user-attack-any-way-to-block/404427/21?silent=true) by asking Ed_S about the `moderators_view_ips` and `moderators_view_emails` site settings, then pointed to the [hard-coded 24-hour deletion limit](https://meta.discourse.org/t/allow-user-to-delete-their-own-topic-at-any-time/411689/10?silent=true) in a separate feature request. He also clarified [when Discourse Boards appears](https://meta.discourse.org/t/discourse-boards/411414/4?silent=true) for self-hosted instances based on the 2026.9 development timeline.\n\n- Martin confirmed that a fix for [Discourse Events recurrence](https://meta.discourse.org/t/discourse-events/97376/629?silent=true) was already merged via PR #42852, and noted that hover cards for subcategory hashtags were next in [Can we make inline links to subcategories more concise?](https://meta.discourse.org/t/can-we-make-inline-links-to-subcategories-more-concise/397217/20?silent=true).\n\n- Mcwumbly supported the [anonymous search control PR](https://meta.discourse.org/t/option-to-enable-search-for-logged-in-users-only/256772/14?silent=true) and confirmed that the old admin dashboard will disappear completely once the new dashboard is permanent in [Introducing Upcoming Changes](https://meta.discourse.org/t/introducing-upcoming-changes-a-system-to-manage-new-features-and-changes-to-existing-functionality-in-your-community/392894/52?silent=true).\n\n- Nat proposed and implemented a PR for `allow_anonymous_search` in [Option to enable search for logged in users only?](https://meta.discourse.org/t/option-to-enable-search-for-logged-in-users-only/256772/12?silent=true), and also helped diagnose [blank Ask AI responses](https://meta.discourse.org/t/how-to-fix-the-blank-ask-ai-response/411572/3?silent=true) by pointing at timeout issues.\n\n- Southpaw thanked HBP for a thorough report and confirmed that a fix is in the works for the [check_username rate-limit signup regression](https://meta.discourse.org/t/regression-new-check-username-rate-limit-can-block-normal-signup-flow/411646/4?silent=true).\n\n- Falco shared a ready PR for [granular permissions for cameras and screen sharing](https://meta.discourse.org/t/granular-permissions-for-cameras-and-screen-sharing/411477/4?silent=true) in Voice rooms.\n\n---\n\nFrom fighting spam bots to making permanent deletion one click easier, the community came out swinging yesterday — just don’t ask us to delete *this* summary! 😉","actions_summary":[],"moderator":true,"admin":true,"staff":true,"user_id":-1,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Today on meta.discourse.org…\nKey Stats\nIn the last 24 hours, the community produced 106 new posts across 33 new topics, collecting 85 likes along the way. The top contributors by likes were: \n\nEd_S — 9 likes, 5 posts\nNicolsdennis — 8 likes, 3 posts\nPer1234 — 7 likes, 2 posts\nLilly — 5 likes, 9 posts\n…","truncated":true,"post_url":"/t/daily-summary-9pm-utc/291850/975","locale":null,"is_localized":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034465,"name":"Joshua Jones","username":"thisisjoshjones","avatar_template":"/user_avatar/meta.discourse.org/thisisjoshjones/{size}/303241_2.png","created_at":"2026-09-05T20:48:31.240Z","cooked":"

이 가입 플로우를 초대 랜딩 페이지에도 구현할 수 있을까요? 아마도 이 알파 단계에서는 범위를 벗어난 내용일 테지만, 기능이 안정화되면 해당 구현이 매우 유용할 것입니다. 제 커뮤니티 멤버들의 진입 장벽을 확실히 낮춰 주니 정말 감사합니다!

","post_number":29,"post_type":1,"posts_count":19,"updated_at":"2026-09-05T20:48:31.240Z","reply_count":1,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":10,"readers_count":9,"score":57.0,"yours":false,"topic_id":407068,"topic_slug":"easier-account-signup-using-email-codes","topic_title":"이메일 코드를 활용한 간편한 계정 가입","topic_html_title":"이메일 코드를 활용한 간편한 계정 가입","category_id":67,"display_username":"Joshua Jones","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"Could this signup flow be implemented in the invitations landing page, too? I'm sure that's beyond the scope of this alpha stage, but that implementation would be very useful after the feature is stable. This really lowers the barrier to entry for my community members, so thank you!","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":132341,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"이 가입 플로우를 초대 랜딩 페이지에도 구현할 수 있을까요? 아마도 이 알파 단계에서는 범위를 벗어난 내용일 테지만, 기능이 안정화되면 해당 구현이 매우 유용할 것입니다. 제 커뮤니티 멤버들의 진입 장벽을 확실히 낮춰 주니 정말 감사합니다!","truncated":true,"post_url":"/t/easier-account-signup-using-email-codes/407068/29","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034459,"name":"","username":"Moin","avatar_template":"/user_avatar/meta.discourse.org/moin/{size}/554653_2.png","created_at":"2026-09-05T18:14:54.249Z","cooked":"

공지 이후 업데이트를 했나요? 2026.9 버전 개발은 11일 전에 시작되었지만, 보드(Boards) 기능은 4일 전에 추가되었습니다. 따라서 보드 기능이 없는 2026.9 버전의 버전을 사용 중일 수 있습니다. 최근 업데이트를 했다면, 예정된 변경 사항(upcoming changes)에서 해당 기능을 찾을 수 있을 것입니다.

\n","post_number":4,"post_type":1,"posts_count":3,"updated_at":"2026-09-05T18:14:54.249Z","reply_count":0,"reply_to_post_number":3,"quote_count":0,"incoming_link_count":1,"reads":23,"readers_count":22,"score":99.6,"yours":false,"topic_id":411414,"topic_slug":"discourse-boards","topic_title":"Discourse 게시판","topic_html_title":"Discourse 게시판","category_id":22,"display_username":"","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Kluges Köpfchen","title_is_group":false,"reply_to_user":{"id":186884,"username":"m_terenui","name":"Terenui","avatar_template":"/user_avatar/meta.discourse.org/m_terenui/{size}/537133_2.png"},"bookmarked":false,"raw":"Did you update after the announcement? The development of 2026.9 started 11 days ago, but boards was added 4 days ago. So there is a chance you are on a version of 2026.9 without boards. If you updated recently, you should be able to find it in the upcoming changes.\n\n[quote=\"mcwumbly, post:1, topic:411418\"]\n## Previewing Boards\n\n**For now, this is considered an experimental feature!** We’re welcoming your feedback, which will help us make improvements and roll this out further.\n\nTo try it out, go to **[Upcoming changes](https://meta.discourse.org/t/introducing-upcoming-changes-a-system-to-manage-new-features-and-changes-to-existing-functionality-in-your-community/392894)** at `/admin/config/upcoming-changes`, find the **Boards enabled** item, and update the **Enabled for…** field to **Everyone** opt your site in.\n\n![image|690x129](upload://vfirhiwsrvqN1RaqMR6vnJKcsUv.png)\n[/quote]","actions_summary":[{"id":2,"count":4}],"moderator":false,"admin":false,"staff":false,"user_id":95552,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"공지 이후 업데이트를 했나요? 2026.9 버전 개발은 11일 전에 시작되었지만, 보드(Boards) 기능은 4일 전에 추가되었습니다. 따라서 보드 기능이 없는 2026.9 버전의 버전을 사용 중일 수 있습니다. 최근 업데이트를 했다면, 예정된 변경 사항(upcoming changes)에서 해당 기능을 찾을 수 있을 것입니다.","truncated":true,"post_url":"/t/discourse-boards/411414/4","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":4}],"current_user_reaction":null,"reaction_users_count":4,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034458,"name":"Terenui","username":"m_terenui","avatar_template":"/user_avatar/meta.discourse.org/m_terenui/{size}/537133_2.png","created_at":"2026-09-05T17:55:18.576Z","cooked":"\n

안녕하세요! 2026.9.0-latest 버전으로 업데이트된 셀프 호스팅 인스턴스를 운영 중인데, 플러그인 목록에서 Discourse Board를 찾을 수 없습니다.

\n

셀프 호스팅 인스턴스에서도 이 플러그인을 사용할 수 있나요? 수동으로 추가해야 하나요?

\n

도와주셔서 감사합니다.
\n감사합니다!

","post_number":3,"post_type":1,"posts_count":3,"updated_at":"2026-09-05T17:55:18.576Z","reply_count":1,"reply_to_post_number":null,"quote_count":1,"incoming_link_count":0,"reads":25,"readers_count":24,"score":10.0,"yours":false,"topic_id":411414,"topic_slug":"discourse-boards","topic_title":"Discourse 게시판","topic_html_title":"Discourse 게시판","category_id":22,"display_username":"Terenui","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"\n[quote=\"mcwumbly, post:1, topic:411414\"]\n**This plugin is bundled with Discourse core.** There is no need to install the plugin separately.\n[/quote]\n\nHey ! I have a self hosted instance updated with 2026.9.0-latest version but I cannot find Discourse Board in my list of plugins. \n\nIs the plugin available for self hosted instance ? Should we add it manually ? \n\nThanks for your help and support. \nCheers !","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":186884,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"안녕하세요! 2026.9.0-latest 버전으로 업데이트된 셀프 호스팅 인스턴스를 운영 중인데, 플러그인 목록에서 Discourse Board를 찾을 수 없습니다. \n셀프 호스팅 인스턴스에서도 이 플러그인을 사용할 수 있나요? 수동으로 추가해야 하나요? \n도와주셔서 감사합니다. \n감사합니다!","truncated":true,"post_url":"/t/discourse-boards/411414/3","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034456,"name":"","username":"Moin","avatar_template":"/user_avatar/meta.discourse.org/moin/{size}/554653_2.png","created_at":"2026-09-05T17:30:36.008Z","cooked":"

그렇지 않다고 생각합니다. 특별한 권한이 없는 사용자는 자신의 주제를 삭제할 수 있는 시간이 24시간으로 하드코딩되어 있습니다.

\n\n

그 이후로는 삭제 요청을 할 수 있는 것이 유일한 선택지입니다.
\n

\"image\"
image589×222 3.13 KB

","post_number":10,"post_type":1,"posts_count":12,"updated_at":"2026-09-05T17:34:06.624Z","reply_count":0,"reply_to_post_number":9,"quote_count":0,"incoming_link_count":1,"reads":21,"readers_count":20,"score":99.2,"yours":false,"topic_id":411689,"topic_slug":"allow-user-to-delete-their-own-topic-at-any-time","topic_title":"사용자가 언제든지 자신의 주제를 삭제할 수 있도록 허용","topic_html_title":"사용자가 언제든지 자신의 주제를 삭제할 수 있도록 허용","category_id":2,"display_username":"","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Kluges Köpfchen","title_is_group":false,"reply_to_user":{"id":3,"username":"supermathie","name":"Michael Brown","avatar_template":"/user_avatar/meta.discourse.org/supermathie/{size}/507518_2.png"},"bookmarked":false,"raw":"I don't think so. There is a hardcoded limit for users without special permissions which limits deleting their own topic to 24 hours. \nhttps://github.com/discourse/discourse/blob/5e9779d4cd418af07a6ed01005d558eda76f2f69/lib/guardian/topic_guardian.rb#L383-L385\n\n\nAfter that, their only option is to flag it for deletion.\n![image|589x222, 75%](upload://nkCrPewh6iK2SsHNigYtaSQwsK.png)","actions_summary":[{"id":2,"count":4}],"moderator":false,"admin":false,"staff":false,"user_id":95552,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"그렇지 않다고 생각합니다. 특별한 권한이 없는 사용자는 자신의 주제를 삭제할 수 있는 시간이 24시간으로 하드코딩되어 있습니다. \n\n그 이후로는 삭제 요청을 할 수 있는 것이 유일한 선택지입니다. \n [image]","truncated":true,"post_url":"/t/allow-user-to-delete-their-own-topic-at-any-time/411689/10","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":4}],"current_user_reaction":null,"reaction_users_count":4,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034453,"name":"Michael Brown","username":"supermathie","avatar_template":"/user_avatar/meta.discourse.org/supermathie/{size}/507518_2.png","created_at":"2026-09-05T17:06:19.177Z","cooked":"\n

말씀하신 것이

\n
\n

(게시글이 작성자에 의해 삭제되었습니다. 24시간 후 제거됩니다.)

\n
\n

라는 표시인가요?

","post_number":9,"post_type":1,"posts_count":12,"updated_at":"2026-09-05T17:06:58.258Z","reply_count":1,"reply_to_post_number":3,"quote_count":1,"incoming_link_count":1,"reads":21,"readers_count":20,"score":14.2,"yours":false,"topic_id":411689,"topic_slug":"allow-user-to-delete-their-own-topic-at-any-time","topic_title":"사용자가 언제든지 자신의 주제를 삭제할 수 있도록 허용","topic_html_title":"사용자가 언제든지 자신의 주제를 삭제할 수 있도록 허용","category_id":2,"display_username":"Michael Brown","primary_group_name":"team","flair_name":"team","flair_url":"https://global.discourse-cdn.com/meta/original/3X/e/b/ebee30bd98aef20357e4a177a5a1e45b877ce088.svg","flair_bg_color":"","flair_color":"111","flair_group_id":47,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"team","title_is_group":true,"bookmarked":false,"raw":"[quote=\"emilio, post:3, topic:411689\"]\nSo they can delete after 24 hours.\n[/quote]\n\nDo you mean the\n\n> (topic deleted by author, will be removed after 24h)\n\nmarker?","actions_summary":[],"moderator":false,"admin":true,"staff":true,"user_id":3,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"말씀하신 것이 \n\n(게시글이 작성자에 의해 삭제되었습니다. 24시간 후 제거됩니다.) \n\n라는 표시인가요?","truncated":true,"post_url":"/t/allow-user-to-delete-their-own-topic-at-any-time/411689/9","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034444,"name":"Ethan ","username":"Ethsim2","avatar_template":"/user_avatar/meta.discourse.org/ethsim2/{size}/522255_2.png","created_at":"2026-09-05T16:46:05.609Z","cooked":"

최종 업데이트: 구현이 이제 검토를 위한 PR으로 업로드되었습니다:

\n\n\n

최종 설계는 이전에 제안했던 사이트 전체 범위의 열거형(enum)이 아니라, 위에서 설명한 대로 관리자별 옵트인(opt-in) 방식입니다.

\n

최종 점검 과정에서 몇 가지 UX 세부 사항이 추가되었습니다:

\n\n

저는 또한 2개의 답변이 있는 일회용 토픽에서 옵트인된 전체 경로를 수동으로 테스트하고, 이후 데이터베이스에서 해당 토픽과 모든 게시물이 삭제되었는지 확인했습니다.

\n

주요 GitHub 테스트/린트 체크는 통과했으며, 이 글 작성 시점에는 보안 스캔이 대기 중이므로 PR은 현재 검토를 기다리고 있습니다.

","post_number":4,"post_type":1,"posts_count":4,"updated_at":"2026-09-05T16:46:05.609Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":2,"reads":17,"readers_count":16,"score":28.4,"yours":false,"topic_id":411687,"topic_slug":"actually-delete-permanently-without-all-the-obstacles","topic_title":"다양한 장애물 없이 실제로 영구 삭제하기","topic_html_title":"다양한 장애물 없이 실제로 영구 삭제하기","category_id":2,"display_username":"Ethan ","primary_group_name":null,"flair_name":"theme_authors","flair_url":"paintbrush","flair_bg_color":"ddd","flair_color":"111","flair_group_id":73,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Tester","title_is_group":false,"bookmarked":false,"raw":"A final update: the implementation is now up as a ready-for-review PR:\n\nhttps://github.com/discourse/discourse/pull/43323\n\nThe final design is the per-admin opt-in approach described above rather than the site-wide enum I originally suggested.\n\nA couple of UX details were added during the final pass:\n\n- the per-admin preference is shown under Preferences → Interface when the site-level gates allow it\n- when an opted-in admin permanently deletes the first post/topic, the irreversible confirmation now explicitly says that it will permanently delete the **topic and all replies**\n- when the admin is not opted in, the existing behaviour and wording remain unchanged\n- the existing same-admin permanent-delete cooldown is still enforced\n- preference changes are recorded in Staff Action Logs\n\nI also manually tested the complete opted-in path on a disposable topic with two replies and verified afterward that the topic and all of its posts had been removed from the database.\n\nThe main GitHub test/lint checks have passed; the PR is now waiting for review, with the security scan still queued at the time of writing.","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":160471,"hidden":false,"trust_level":1,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"최종 업데이트: 구현이 이제 검토를 위한 PR으로 업로드되었습니다: \n\n\n최종 설계는 이전에 제안했던 사이트 전체 범위의 열거형(enum)이 아니라, 위에서 설명한 대로 관리자별 옵트인(opt-in) 방식입니다. \n최종 점검 과정에서 몇 가지 UX 세부 사항이 추가되었습니다: \n\n사이트 수준의 게이트가 허용하는 경우, 관리자별 설정은 설정 → 인터페이스 메뉴 아래에 표시됩니다.\n옵트인한 관리자가 첫 번째 게시물/토픽을 영구 삭제할 때, 되돌릴 수 없는 확인 메시지에 토픽과 모든 답변이 영구 삭제됨이 명시적으로 표시됩니다.\n관리자가 …","truncated":true,"post_url":"/t/actually-delete-permanently-without-all-the-obstacles/411687/4","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034437,"name":"Jakke Flemming","username":"Jagster","avatar_template":"/user_avatar/meta.discourse.org/jagster/{size}/192154_2.png","created_at":"2026-09-05T14:28:40.113Z","cooked":"

감사합니다. 설정의 방 탭에서 할 수 있네요. 포럼 GUI만 보고 있었어요 \":man_facepalming:\"

","post_number":29,"post_type":1,"posts_count":25,"updated_at":"2026-09-05T14:29:02.253Z","reply_count":0,"reply_to_post_number":28,"quote_count":0,"incoming_link_count":0,"reads":24,"readers_count":23,"score":19.8,"yours":false,"topic_id":411337,"topic_slug":"voice-discord-style-voice-and-video-rooms-now-bundled-with-discourse","topic_title":"Voice: Discord 스타일 음성 및 비디오 방, 이제 Discourse에 번들링됨 :studio_microphone:","topic_html_title":"Voice: Discord 스타일 음성 및 비디오 방, 이제 Discourse에 번들링됨 :studio_microphone:","category_id":67,"display_username":"Jakke Flemming","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","reply_to_user":{"id":71041,"username":"satonotdead","name":"","avatar_template":"/user_avatar/meta.discourse.org/satonotdead/{size}/447830_2.png"},"bookmarked":false,"raw":"Thanks, it could done from rooms-tab of settings indeed. I was looking at forum GUI only 🤦‍♂️","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":83631,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"감사합니다. 설정의 방 탭에서 할 수 있네요. 포럼 GUI만 보고 있었어요 :man_facepalming:","truncated":true,"post_url":"/t/voice-discord-style-voice-and-video-rooms-now-bundled-with-discourse/411337/29","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"+1","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034436,"name":"","username":"satonotdead","avatar_template":"/user_avatar/meta.discourse.org/satonotdead/{size}/447830_2.png","created_at":"2026-09-05T14:01:56.113Z","cooked":"

사이드바를 사용하거나 활성화된 플러그인에서 ‘Resenha’ 탭을 찾아보시는 걸 추천해요. 아주 간단할 거예요.

","post_number":28,"post_type":1,"posts_count":25,"updated_at":"2026-09-05T14:02:19.554Z","reply_count":1,"reply_to_post_number":27,"quote_count":0,"incoming_link_count":1,"reads":24,"readers_count":23,"score":14.8,"yours":false,"topic_id":411337,"topic_slug":"voice-discord-style-voice-and-video-rooms-now-bundled-with-discourse","topic_title":"Voice: Discord 스타일 음성 및 비디오 방, 이제 Discourse에 번들링됨 :studio_microphone:","topic_html_title":"Voice: Discord 스타일 음성 및 비디오 방, 이제 Discourse에 번들링됨 :studio_microphone:","category_id":67,"display_username":"","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","reply_to_user":{"id":83631,"username":"Jagster","name":"Jakke Flemming","avatar_template":"/user_avatar/meta.discourse.org/jagster/{size}/192154_2.png"},"bookmarked":false,"raw":"I think you need to just use the sidebar or look for the Resenha tab in enabled plugins. It should be straightforward.","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":71041,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"사이드바를 사용하거나 활성화된 플러그인에서 ‘Resenha’ 탭을 찾아보시는 걸 추천해요. 아주 간단할 거예요.","truncated":true,"post_url":"/t/voice-discord-style-voice-and-video-rooms-now-bundled-with-discourse/411337/28","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034433,"name":"Ethan ","username":"Ethsim2","avatar_template":"/user_avatar/meta.discourse.org/ethsim2/{size}/522255_2.png","created_at":"2026-09-05T13:38:45.083Z","cooked":"

기존의 영구 삭제 코드를 파고든 후 빠른 진행 상황 업데이트를 드립니다.

\n

Discourse에는 이미 여기에 필요한 실제 일괄 삭제 동작이 존재한다는 것을 발견했습니다. 첫 번째 게시물이 영구적으로 삭제되면, PostDestroyer가 이미 해당 주제의 나머지 게시물들을 재귀적으로 영구 삭제할 수 있습니다. 제한 사항은 주로 권한/정책 검사에 있으며, 현재는 다른 게시물들이 먼저 영구 삭제되어야 하는 것을 요구합니다.

\n

따라서 위에서 제안했던 사이트 전체 범위의 enum 방식에서 벗어나, 더 보수적인 옵트인(opt-in) 모델을 사용한 작동 가능한 구현체를 만들었습니다.

\n\n

현재 해당 설정은 다음과 같이 표시되어 있습니다:

\n
\n

주제를 영구 삭제할 때 모든 게시물을 삭제하도록 허용

\n
\n

그리고 설명은 다음과 같습니다:

\n
\n

주제를 영구 삭제할 때, 개별적으로 영구 삭제하는 것을 요구하지 않고 나머지 모든 게시물을 함께 영구 삭제합니다.

\n
\n

백엔드 정책/보안 테스트, 주제와 모든 나머지 게시물이 실제로 영구적으로 제거되었음을 확인하는 컨트롤러 커버리지, 직렬화기/API 커버리지, 그리고 설정의 표시 및 저장을 위한 프론트엔드 인수 테스트를 추가했습니다. 현재 모두 통과하고 있습니다.

\n

또한, 더 파괴적인 삭제 모드를 활성화하는 것은 타임스탬프가 있는 감사 이벤트로 기록할 가치가 있다고 생각하여, 이 관리자별 옵트인에 대한 변경 사항을 스태프 액션 로그(Staff Action Logs)에 기록하는 방안도 검토하고 있습니다.

\n

해당 작업과 최종 검토를 마치는 대로 GitHub PR을 게시하겠습니다.

","post_number":3,"post_type":1,"posts_count":4,"updated_at":"2026-09-05T13:38:45.083Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":25,"readers_count":24,"score":10.0,"yours":false,"topic_id":411687,"topic_slug":"actually-delete-permanently-without-all-the-obstacles","topic_title":"다양한 장애물 없이 실제로 영구 삭제하기","topic_html_title":"다양한 장애물 없이 실제로 영구 삭제하기","category_id":2,"display_username":"Ethan ","primary_group_name":null,"flair_name":"theme_authors","flair_url":"paintbrush","flair_bg_color":"ddd","flair_color":"111","flair_group_id":73,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Tester","title_is_group":false,"bookmarked":false,"raw":"A quick progress update after digging into the existing permanent-deletion code:\n\nI found that Discourse already has the actual bulk deletion behaviour needed here. When the first post is permanently destroyed, `PostDestroyer` can already recursively permanently destroy the remaining posts in the topic. The restriction is mainly in the permission/policy checks which currently require the other posts to be permanently deleted first.\n\nI've therefore moved away from the site-wide enum I suggested above and have a working implementation using a more conservative opt-in model:\n\n- the existing `can_permanently_delete` setting remains the master switch\n- there is an additional hidden operator-level gate, disabled by default\n- when both are enabled, each admin can individually opt in under Preferences → Interface\n- one admin opting in does not change the behaviour for any other admin\n- disabling the hidden gate immediately restores the existing behaviour globally\n- the existing permanent-deletion confirmation and other safeguards remain in place\n\nThe preference is currently labelled:\n\n> Allow permanent topic deletion to delete all posts\n\nwith the explanation:\n\n> When permanently deleting a topic, also permanently delete all remaining posts instead of requiring them to be permanently deleted individually.\n\nI've added backend policy/security tests, controller coverage confirming that the topic and all remaining posts are actually permanently removed, serializer/API coverage, and frontend acceptance tests for the preference visibility and saving. Those are passing.\n\nI'm also looking at recording changes to this per-admin opt-in in the Staff Action Logs, since enabling a more destructive deletion mode seems worth having as a timestamped audit event.\n\nI'll post the GitHub PR once I've finished that and the final review.","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":160471,"hidden":false,"trust_level":1,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"기존의 영구 삭제 코드를 파고든 후 빠른 진행 상황 업데이트를 드립니다. \nDiscourse에는 이미 여기에 필요한 실제 일괄 삭제 동작이 존재한다는 것을 발견했습니다. 첫 번째 게시물이 영구적으로 삭제되면, PostDestroyer가 이미 해당 주제의 나머지 게시물들을 재귀적으로 영구 삭제할 수 있습니다. 제한 사항은 주로 권한/정책 검사에 있으며, 현재는 다른 게시물들이 먼저 영구 삭제되어야 하는 것을 요구합니다. \n따라서 위에서 제안했던 사이트 전체 범위의 enum 방식에서 벗어나, 더 보수적인 옵트인(opt-in) 모델을 사…","truncated":true,"post_url":"/t/actually-delete-permanently-without-all-the-obstacles/411687/3","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034429,"name":"Ed S","username":"Ed_S","avatar_template":"/user_avatar/meta.discourse.org/ed_s/{size}/134015_2.png","created_at":"2026-09-05T13:05:47.687Z","cooked":"\n

아, 그렇군요. 그래도 \"답글이 없는 주제\"를 삭제할 수 있게 해달라는 기능 요청으로 명확히 표현하는 것이 더 나을 수 있습니다.

\n

사용자의 기여물은 항상 해당 사용자의 통제 아래에 있어야 한다는 의견도 있지만, 저는 Discourse 팀의 관점이 더 중요하다고 생각합니다. 즉, 대화 기록이 개인의 기록을 수정할 자유보다 더 중요하다는 것이죠. 개인적으로도 이에 동의합니다. 하지만 다른 관점을 가진다면, 특정 기능이 도움이 될 수 있습니다.

","post_number":8,"post_type":1,"posts_count":12,"updated_at":"2026-09-05T13:05:47.687Z","reply_count":0,"reply_to_post_number":5,"quote_count":1,"incoming_link_count":1,"reads":25,"readers_count":24,"score":25.0,"yours":false,"topic_id":411689,"topic_slug":"allow-user-to-delete-their-own-topic-at-any-time","topic_title":"사용자가 언제든지 자신의 주제를 삭제할 수 있도록 허용","topic_html_title":"사용자가 언제든지 자신의 주제를 삭제할 수 있도록 허용","category_id":2,"display_username":"Ed S","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Bug Reporter","title_is_group":false,"bookmarked":false,"raw":"[quote=\"emilio, post:5, topic:411689\"]\nThey can’t delete at all if there are replies\n[/quote]\n\nAh. Still, it might be clearer as a feature request that it's unanswered topics which you'd like to make deletable.\n\nThere are schools of thought that say a person's contributions should always remain under their control, but I think the view in the Discourse team is that the conversational record is more important than the individual's freedom to change it. I personally agree. But if you take another view, it may be that a feature can help you.","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":63143,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"아, 그렇군요. 그래도 "답글이 없는 주제"를 삭제할 수 있게 해달라는 기능 요청으로 명확히 표현하는 것이 더 나을 수 있습니다. \n사용자의 기여물은 항상 해당 사용자의 통제 아래에 있어야 한다는 의견도 있지만, 저는 Discourse 팀의 관점이 더 중요하다고 생각합니다. 즉, 대화 기록이 개인의 기록을 수정할 자유보다 더 중요하다는 것이죠. 개인적으로도 이에 동의합니다. 하지만 다른 관점을 가진다면, 특정 기능이 도움이 될 수 있습니다.","truncated":true,"post_url":"/t/allow-user-to-delete-their-own-topic-at-any-time/411689/8","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034428,"name":"system","username":"system","avatar_template":"/user_avatar/meta.discourse.org/system/{size}/443519_2.png","created_at":"2026-09-05T13:00:58.443Z","cooked":"

Today on meta.discourse.org…

\n

Key Stats

\n

In the last 24 hours, 94 posts and 31 topics were active across Meta, with 71 likes recorded in the returned posts.

\n

Top users by likes and posts:

\n\n

Interesting Topics

\n

Support

\n\n

General

\n\n

#Community Building

\n\n

#Feature

\n\n

#Announcements

\n\n

#Self-hosting

\n\n

bug

\n\n

#Plugin

\n\n

Activity by the Team Group

\n\n
\n

From fighting spam bots and rate-limit gremlins to wrestling event calendars and voice rooms, it was another gloriously productive day in the life of Meta — see you all in the threads! \":tada:\"

","post_number":940,"post_type":1,"posts_count":714,"updated_at":"2026-09-05T13:00:58.443Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":3,"readers_count":2,"score":0.6,"yours":false,"topic_id":291852,"topic_slug":"daily-summary-1pm-utc","topic_title":"일일 요약 (UTC 오후 1시)","topic_html_title":"일일 요약 (UTC 오후 1시)","category_id":157,"display_username":"system","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"# Today on meta.discourse.org...\n\n## Key Stats\n\nIn the last 24 hours, **94 posts** and **31 topics** were active across Meta, with **71 likes** recorded in the returned posts.\n\nTop users by likes and posts:\n\n- Nicolsdennis — **8 likes**, **3 posts**\n- Per1234 — **7 likes**, **2 posts**\n- Ed_S — **6 likes**, **3 posts**\n- Lilly — **5 likes**, **9 posts**\n- Falco — **5 likes**, **1 post**\n- Nat — **4 likes**, **2 posts**\n- Jagster — **3 likes**, **5 posts**\n- Satonotdead — **3 likes**, **5 posts**\n- Emilio — **3 likes**, **4 posts**\n- HBP — **3 likes**, **1 post**\n\n## Interesting Topics\n\n### #Support\n\n- **Fresh Install (Hetzner VPS) Failing** — Apidevlab reported repeated bootstrap failures while installing Discourse on Hetzner, despite plenty of RAM and swap. Jagster and Ed_S both urged posting the *entire* log rather than just the tail error, and Lilly noted that Podman-based installs are unsupported, making debugging harder. [read more](https://meta.discourse.org/t/-/411664/1?silent=true)\n\n- **Odd spam user attack** — LordOfBikes shared details of a surge in spam registrations, including patterns in names and single-letter subdomain emails, and started blocking cloud provider networks. One1 said hCaptcha has eliminated the spam for them, while Ed_S added a mandatory user field to make fake applications easier to reject. Moin also asked about the `moderators_view_ips` and `moderators_view_emails` settings. [read more](https://meta.discourse.org/t/-/404427/16?silent=true)\n\n- **Exposing LiveKit status** — Nicolsdennis explained how they built a companion app and workaround to expose Discourse Voice/LiveKit status for their custom client, referencing an ongoing discussion about how the LiveKit integration should evolve. [read more](https://meta.discourse.org/t/-/411428/13?silent=true)\n\n### #General\n\n- **A Social Mobile & Desktop Client for Communities** — Nicolsdennis showcased new native Discourse Voice support in their Mesh client, with separate UX for web-only voice and LiveKit, plus a reworked companion app that allows live streaming while using Discourse Voice in a “watercooler” conversation. [read more](https://meta.discourse.org/t/-/408132/30?silent=true)\n\n### #Community Building\n\n- **Show us your Workflows** — Per1234 shared a **Discourse Update Notifier** workflow that automatically posts about new Discourse versions on a forum, helping technically minded communities stay informed about changes introduced by updates. [read more](https://meta.discourse.org/t/-/410589/13?silent=true)\n\n### #Feature\n\n- **Granular permissions for cameras and screen sharing** — Falco announced a ready-made PR for granular permissions in Discourse Voice, promising more control over camera and screen-sharing access. [read more](https://meta.discourse.org/t/-/411477/4?silent=true)\n\n- **Option to enable search for logged in users only** — Nat proposed a new `allow_anonymous_search` site setting and opened a PR, with Mcwumbly agreeing that the approach is a solid first step even if the UI could later show a login prompt instead of hiding search. [read more](https://meta.discourse.org/t/-/256772/12?silent=true)\n\n### #Announcements\n\n- **Voice: Discord-style voice and video rooms** — Community excitement continues about bundled Discourse Voice. Jagster asked whether admins can delete rooms, and Satonotdead confirmed admins can also rename rooms and limit them to specific groups. [read more](https://meta.discourse.org/t/-/411337/22?silent=true)\n\n- **New Calendar Feature: End Date for Recurring Events** — MiniForum couldn’t find the end-date option and Ethsim2 clarified the difference between `Insert date / time` and `Create event`, going on to suggest a Power Automate/API workaround for school calendars and linking an existing feature request for recurring date-range entries. [read more](https://meta.discourse.org/t/-/368527/6?silent=true)\n\n- **Introducing Upcoming Changes** — Ethsim2 asked whether opting out of the redesigned admin dashboard is the only way to keep the legacy dashboard, and Mcwumbly confirmed the old dashboard will go away entirely once the new one becomes permanent. [read more](https://meta.discourse.org/t/-/392894/50?silent=true)\n\n### #Self-hosting\n\n- **How to fix the blank Ask AI response** — Karthik_K1 reported Ask AI logs showing correct responses but nothing displayed, especially on desktop. Nat suggested the request was timing out due to a slow model response, since Ask AI has a 20-second deadline. [read more](https://meta.discourse.org/t/-/411572/3?silent=true)\n\n- **Solving Gemini API key errors** — Karthik_K1 worked through connecting Google Vertex AI to Discourse, with Lilly explaining her working Gemini API setup and Satonotdead recommending a LiteLLM proxy as a lower-latency workaround. [read more](https://meta.discourse.org/t/-/411545/2?silent=true)\n\n### #Bug\n\n- **Regression: check_username rate limit can block normal signup flow** — HBP wrote a detailed reproduction showing that the new 10-requests-per-minute rate limit on `/u/check_username.json` can block legitimate signups. Southpaw acknowledged the report and said a fix is in the works. [read more](https://meta.discourse.org/t/-/411646/1?silent=true)\n\n- **Editing event end date → post event date on topic title not updated** — Ethsim2 opened PR #43285 to fix the event title not updating after editing event start/end times, and shared a detailed screen recording of manual tests against the PR. [read more](https://meta.discourse.org/t/-/387466/4?silent=true)\n\n### #Plugin\n\n- **ProxyTracer: VPN & Proxy Blocker** — ProxyTracer released a new beta with optional blocking vs. CAPTCHA challenges for suspicious connections, support for Cloudflare Turnstile and hCaptcha, and 30-day visual analytics of detected proxy/VPN traffic. [read more](https://meta.discourse.org/t/-/399958/23?silent=true)\n\n## Activity by the Team Group\n\n- Southpaw responded to the **check_username signup regression**, thanking HBP for the detailed report and confirming a fix is in the works. [read more](https://meta.discourse.org/t/-/411646/4?silent=true)\n- Nat contributed to the **search permissions feature request** by proposing the `allow_anonymous_search` PR, and also helped diagnose a **blank Ask AI response** by pointing to timeout issues. [read more](https://meta.discourse.org/t/-/256772/12?silent=true) · [read more](https://meta.discourse.org/t/-/411572/3?silent=true)\n- Martin confirmed in **Discourse Events** that the recurring “fourth Thursday” issue should be fixed by PR #42852, and also noted that hashtag hover cards are working in the **subcategory links** discussion. [read more](https://meta.discourse.org/t/-/97376/629?silent=true) · [read more](https://meta.discourse.org/t/-/397217/20?silent=true)\n- Mcwumbly clarified in **Introducing Upcoming Changes** that the legacy admin dashboard will be removed completely once the new dashboard becomes permanent. [read more](https://meta.discourse.org/t/-/392894/52?silent=true)\n\n---\n\nFrom fighting spam bots and rate-limit gremlins to wrestling event calendars and voice rooms, it was another gloriously productive day in the life of Meta — see you all in the threads! 🎉","actions_summary":[],"moderator":true,"admin":true,"staff":true,"user_id":-1,"hidden":false,"trust_level":4,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Today on meta.discourse.org…\nKey Stats\nIn the last 24 hours, 94 posts and 31 topics were active across Meta, with 71 likes recorded in the returned posts. \nTop users by likes and posts: \n\nNicolsdennis — 8 likes, 3 posts\nPer1234 — 7 likes, 2 posts\nEd_S — 6 likes, 3 posts\nLilly — 5 likes, 9 posts\nFalc…","truncated":true,"post_url":"/t/daily-summary-1pm-utc/291852/940","locale":null,"is_localized":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null}]}