![\":man_facepalming:\"](\"https://emoji.discourse-cdn.com/twitter/man_facepalming.png?v=15\" "\\":man_facepalming:\\"")
감사합니다. 설정의 방 탭에서 할 수 있네요. 포럼 GUI만 보고 있었어요
사이드바를 사용하거나 활성화된 플러그인에서 ‘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":8,"readers_count":7,"score":11.6,"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":"기존의 영구 삭제 코드를 파고든 후 빠른 진행 상황 업데이트를 드립니다.
\nDiscourse에는 이미 여기에 필요한 실제 일괄 삭제 동작이 존재한다는 것을 발견했습니다. 첫 번째 게시물이 영구적으로 삭제되면, PostDestroyer가 이미 해당 주제의 나머지 게시물들을 재귀적으로 영구 삭제할 수 있습니다. 제한 사항은 주로 권한/정책 검사에 있으며, 현재는 다른 게시물들이 먼저 영구 삭제되어야 하는 것을 요구합니다.
따라서 위에서 제안했던 사이트 전체 범위의 enum 방식에서 벗어나, 더 보수적인 옵트인(opt-in) 모델을 사용한 작동 가능한 구현체를 만들었습니다.
\ncan_permanently_delete 설정은 여전히 마스터 스위치 역할을 합니다.현재 해당 설정은 다음과 같이 표시되어 있습니다:
\n\n\n주제를 영구 삭제할 때 모든 게시물을 삭제하도록 허용
\n
그리고 설명은 다음과 같습니다:
\n\n\n주제를 영구 삭제할 때, 개별적으로 영구 삭제하는 것을 요구하지 않고 나머지 모든 게시물을 함께 영구 삭제합니다.
\n
백엔드 정책/보안 테스트, 주제와 모든 나머지 게시물이 실제로 영구적으로 제거되었음을 확인하는 컨트롤러 커버리지, 직렬화기/API 커버리지, 그리고 설정의 표시 및 저장을 위한 프론트엔드 인수 테스트를 추가했습니다. 현재 모두 통과하고 있습니다.
\n또한, 더 파괴적인 삭제 모드를 활성화하는 것은 타임스탬프가 있는 감사 이벤트로 기록할 가치가 있다고 생각하여, 이 관리자별 옵트인에 대한 변경 사항을 스태프 액션 로그(Staff Action Logs)에 기록하는 방안도 검토하고 있습니다.
\n해당 작업과 최종 검토를 마치는 대로 GitHub PR을 게시하겠습니다.
","post_number":3,"post_type":1,"posts_count":3,"updated_at":"2026-09-05T13:38:45.083Z","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":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":8,"updated_at":"2026-09-05T13:05:47.687Z","reply_count":0,"reply_to_post_number":5,"quote_count":1,"incoming_link_count":1,"reads":6,"readers_count":5,"score":6.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":"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":[],"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":[],"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":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":"In 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:
\nFresh 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
\nOdd 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
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
\nGranular 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
\nOption 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
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
\nNew 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
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
\nHow 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
\nSolving 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
\nRegression: 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
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
\nallow_anonymous_search PR, and also helped diagnose a blank Ask AI response by pointing to timeout issues. read more · read moreFrom 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:\"](\"https://emoji.discourse-cdn.com/twitter/tada.png?v=15\" "\\":tada:\\"")
아마도 저는 절반만 설정한 것 같네요. 그 점에 대해 알려주셔서 감사합니다! 운영진에게 그들이 어떤 내용을 보고 있는지 다시 확인해 봐야 할 것 같습니다.
","post_number":22,"post_type":1,"posts_count":22,"updated_at":"2026-09-05T13:00:32.984Z","reply_count":0,"reply_to_post_number":21,"quote_count":1,"incoming_link_count":1,"reads":7,"readers_count":6,"score":21.4,"yours":false,"topic_id":404427,"topic_slug":"is-anyone-experiencing-an-odd-spam-user-attack-any-way-to-block","topic_title":"이상한 스팸 유저 공격을 경험하고 계신 분 계신가요? 차단 방법이 있을까요?","topic_html_title":"이상한 스팸 유저 공격을 경험하고 계신 분 계신가요? 차단 방법이 있을까요?","category_id":6,"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=\"Moin, post:21, topic:404427\"]\nHow did you configure\n[/quote]\n\nI think the answer is that I half-configured them, so thanks for the heads-up on that! I'll have to check (again) with the mods as to what they see.","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":"아마도 저는 절반만 설정한 것 같네요. 그 점에 대해 알려주셔서 감사합니다! 운영진에게 그들이 어떤 내용을 보고 있는지 다시 확인해 봐야 할 것 같습니다.","truncated":true,"post_url":"/t/is-anyone-experiencing-an-odd-spam-user-attack-any-way-to-block/404427/22","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":2034426,"name":"","username":"Moin","avatar_template":"/user_avatar/meta.discourse.org/moin/{size}/554653_2.png","created_at":"2026-09-05T12:58:56.643Z","cooked":"\nmoderators_view_ips와 moderators_view_emails 사이트 설정을 어떻게 구성하셨나요?
결함 조사에 도움이 될 수 있는 세부 사항: 예상치 못한 버튼은 검토 대상 전용 페이지(예: /review/45721)에만 존재합니다. 일반 검토 대상 목록 페이지(예: /review?&status=all&type=ReviewableUser)의 항목에는 존재하지 않습니다.
(게시글이 작성자에 의해 삭제되었습니다)
","post_number":20,"post_type":1,"posts_count":22,"updated_at":"2026-09-05T10:19:26.849Z","reply_count":0,"reply_to_post_number":19,"quote_count":0,"incoming_link_count":0,"reads":11,"readers_count":10,"score":2.2,"yours":false,"topic_id":404427,"topic_slug":"is-anyone-experiencing-an-odd-spam-user-attack-any-way-to-block","topic_title":"이상한 스팸 유저 공격을 경험하고 계신 분 계신가요? 차단 방법이 있을까요?","topic_html_title":"이상한 스팸 유저 공격을 경험하고 계신 분 계신가요? 차단 방법이 있을까요?","category_id":6,"display_username":"Robert","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":2,"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,"reply_to_user":{"id":63143,"username":"Ed_S","name":"Ed S","avatar_template":"/user_avatar/meta.discourse.org/ed_s/{size}/134015_2.png"},"bookmarked":false,"raw":"(post deleted by author)","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":27384,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":true,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"(게시글이 작성자에 의해 삭제되었습니다)","truncated":true,"post_url":"/t/is-anyone-experiencing-an-odd-spam-user-attack-any-way-to-block/404427/20","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":2034411,"name":"Ed S","username":"Ed_S","avatar_template":"/user_avatar/meta.discourse.org/ed_s/{size}/134015_2.png","created_at":"2026-09-05T09:41:48.224Z","cooked":"며칠 전, 인간 모더레이터가 지원서를 승인하는 데 도움이 되도록 지원자에게 필수 텍스트 필드(이름이 \"관심사\"인 사용자 필드)를 추가했습니다. (“계정 승인을 결정하는 데 도움이 되도록 몇 마디만 적어 주세요.”)
\n\n아직 이르지만, 의심스러운 계정 두 개가 무작위 비밀번호 같은 텍스트를 입력하여 쉽게 거부할 수 있었습니다.
\n모더레이터들이 계정 검토 처리를 도와주길 원하며 실제로도 도와주고 있지만, 이메일 주소나 IP 주소를 볼 수 없어 다소 제한적입니다. Stopforumspam은 꽤 유용한 자원이었습니다.
","post_number":19,"post_type":1,"posts_count":22,"updated_at":"2026-09-05T11:47:58.778Z","reply_count":2,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":12,"readers_count":11,"score":27.4,"yours":false,"topic_id":404427,"topic_slug":"is-anyone-experiencing-an-odd-spam-user-attack-any-way-to-block","topic_title":"이상한 스팸 유저 공격을 경험하고 계신 분 계신가요? 차단 방법이 있을까요?","topic_html_title":"이상한 스팸 유저 공격을 경험하고 계신 분 계신가요? 차단 방법이 있을까요?","category_id":6,"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":2,"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":"A few days ago I added a mandatory text (a User Field called \"Interests\") for applicants to help the human moderators approve their application (\"a few words please to help the human reviewers in deciding to approve your account.\" \n\n\n\n\nIt’s early to say but two suspicious accounts put random password like text in there which makes for easy rejection. \n\nI’d like my mods to help with processing account reviews, and they do, but they can’t see emails or IP addresses which is a bit limiting. Stopforumspam has been quite a useful resource.","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 [image] \n아직 이르지만, 의심스러운 계정 두 개가 무작위 비밀번호 같은 텍스트를 입력하여 쉽게 거부할 수 있었습니다. \n모더레이터들이 계정 검토 처리를 도와주길 원하며 실제로도 도와주고 있지만, 이메일 주소나 IP 주소를 볼 수 없어 다소 제한적입니다. Stopforumspam은 꽤 유용한 자원이었습니다.","truncated":true,"post_url":"/t/is-anyone-experiencing-an-odd-spam-user-attack-any-way-to-block/404427/19","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":2034410,"name":"Josue Navarro","username":"josuens14","avatar_template":"/user_avatar/meta.discourse.org/josuens14/{size}/249690_2.png","created_at":"2026-09-05T09:15:31.926Z","cooked":"(게시글이 작성자에 의해 삭제되었습니다)
","post_number":1,"post_type":1,"posts_count":1,"updated_at":"2026-09-05T09:46:14.829Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":15,"reads":19,"readers_count":18,"score":78.8,"yours":false,"topic_id":411702,"topic_slug":"delete","topic_title":"삭제","topic_html_title":"삭제","category_id":1,"display_username":"Josue Navarro","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":3,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"(topic deleted by author)","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":111444,"hidden":false,"trust_level":1,"deleted_at":null,"user_deleted":true,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"(게시글이 작성자에 의해 삭제되었습니다)","truncated":true,"post_url":"/t/delete/411702/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":2034409,"name":"","username":"one1","avatar_template":"/user_avatar/meta.discourse.org/one1/{size}/493591_2.png","created_at":"2026-09-05T09:15:12.186Z","cooked":"이어서 말씀드리자면… 몇 주 전에 hCaptcha를 도입하기 시작했는데, 처음 게시글에서 언급했던 특정 유형의 스팸 사용자는 완전히 사라졌습니다. 전반적인 스팸 양도 줄어들었을 가능성이 있으며, 가입자 수가 눈에 띄게 감소하지는 않았습니다.
\n그래서 hCaptcha를 한번 사용해 보시길 권합니다.
","post_number":18,"post_type":1,"posts_count":22,"updated_at":"2026-09-05T09:15:12.186Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":14,"readers_count":13,"score":22.8,"yours":false,"topic_id":404427,"topic_slug":"is-anyone-experiencing-an-odd-spam-user-attack-any-way-to-block","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":null,"bookmarked":false,"raw":"To follow up… A few weeks ago we started using the hCaptcha and that has completely eliminated the specific type of spam users I mentioned in the OP. Perhaps even spam in general is down, without any noticeable decrease in over all signups.\n\nSo, give the hCaptcha a try.","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":80288,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"이어서 말씀드리자면… 몇 주 전에 hCaptcha를 도입하기 시작했는데, 처음 게시글에서 언급했던 특정 유형의 스팸 사용자는 완전히 사라졌습니다. 전반적인 스팸 양도 줄어들었을 가능성이 있으며, 가입자 수가 눈에 띄게 감소하지는 않았습니다. \n그래서 hCaptcha를 한번 사용해 보시길 권합니다.","truncated":true,"post_url":"/t/is-anyone-experiencing-an-odd-spam-user-attack-any-way-to-block/404427/18","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":2034408,"name":"Robert","username":"merefield","avatar_template":"/user_avatar/meta.discourse.org/merefield/{size}/176214_2.png","created_at":"2026-09-05T08:59:31.860Z","cooked":"최근에 이런 것들을 한꺼번에 많이 봤어요. 처음에는 드디어 SEO를 깨뜨린 줄 알았죠 ![\":sweat_smile:\"](\"https://emoji.discourse-cdn.com/twitter/sweat_smile.png?v=15\" "\\":sweat_smile:\\"")
근데 OpenClaw를 떠올렸어요
다행히 새로운 대량 사용자 관리 기능이 있네요! ![\":folded_hands:\"](\"https://emoji.discourse-cdn.com/twitter/folded_hands.png?v=15\" "\\":folded_hands:\\"")
저도 동일한 문제를 겪고 있습니다. 자체 호스팅 인스턴스에서 발생하며, 숫자가 증가하고 있습니다. 처음에는 주당 1~2건의 Sporadic(불규칙한) 가입이 시작되었습니다. 이번 주에는 10건의 가입이 발생했고, 그중 5건은 어제였습니다.
\n패턴은 성별(Pronoun) 설정에 랜덤 문자열이 사용되고, 이전에 언급된 이름과 성의 패턴이 나타나는 것입니다.
\n저는 whois IP 쿼리를 수행했는데, 90% 이상이 미국의 2개 클라우드 제공업체에서 온 것이었습니다. 그래서 IP 대신 네트워크를 차단하기 시작했습니다. 클라우드 제공업체 네트워크를 차단할 때 일반 사용자를 차단할 위험은 매우 낮습니다. 대부분은 /24이며, 일부는 /23 또는 /22 네트워크였습니다.
종종 가입 이메일에 대해 반송(bounce) 메시지를 받는데, 이는 이메일 주소를 사용할 수 없기 때문입니다. 이 주소들에도 패턴이 있습니다. 공통 부분은 서브도메인으로, 도메인 부분이 a, b, c, e와 같은 단일 문자 서브도메인으로 시작되는 형태입니다(예: ...@a.example.com).
이것이 정규식 패턴만 허용하는 경우 차단된 이메일 도메인 설정으로 차단할 수 있는 좋은 속성이 될 수 있습니다. 간단한 @[a-z]\\.* 패턴으로 이러한 시도를 막을 수 있습니다.
새 대시보드가 정식 버전으로 전환되면 기존 대시보드는 완전히 제거됩니다.
\n\n이제 새 대시보드에 새로운 섹션으로 추가되었습니다:
\n","post_number":52,"post_type":1,"posts_count":47,"updated_at":"2026-09-05T08:48:35.253Z","reply_count":0,"reply_to_post_number":51,"quote_count":1,"incoming_link_count":1,"reads":7,"readers_count":6,"score":36.4,"yours":false,"topic_id":392894,"topic_slug":"introducing-upcoming-changes-a-system-to-manage-new-features-and-changes-to-existing-functionality-in-your-community","topic_title":"새로운 기능과 기존 기능 변경 사항을 관리하는 시스템 'Upcoming Changes' 소개","topic_html_title":"새로운 기능과 기존 기능 변경 사항을 관리하는 시스템 ‘Upcoming Changes’ 소개","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,"bookmarked":false,"raw":"The old dashboard will be going away completely when the new one becomes permanent.\n\n[quote=\"Ethsim2, post:51, topic:392894\"]\nwill there be another supported way to view that information?\n[/quote]\n\nIt's a new section in the new dashboard now:\n\n[quote=\"chapoi, post:56, topic:404528\"]\nWe have added a redesigned system section. By default it can be found at the bottom of the dashboard (you can move this up in the configure menu).\n\n\n\nThis is visible for *self-hosters only.*\n[/quote]","actions_summary":[{"id":2,"count":2}],"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":"새 대시보드가 정식 버전으로 전환되면 기존 대시보드는 완전히 제거됩니다. \n\n이제 새 대시보드에 새로운 섹션으로 추가되었습니다:","truncated":true,"post_url":"/t/introducing-upcoming-changes-a-system-to-manage-new-features-and-changes-to-existing-functionality-in-your-community/392894/52","locale":"en","is_localized":true,"language":"en","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":2034399,"name":"Ethan ","username":"Ethsim2","avatar_template":"/user_avatar/meta.discourse.org/ethsim2/{size}/522255_2.png","created_at":"2026-09-05T08:13:24.969Z","cooked":"감사합니다. 구현 방식을 다시 한번 확인해 보았습니다.
\n?version=alt가 이전에 대체 관리자 대시보드를 미리 보기 위한 방법으로 제공되었으나, 여기에서 제거되었음을 확인했습니다:
Dashboard improvements가 Permanent이 아닌 Stable 상태임에도 불구하고, 이제 Enabled for → No one을 설정하는 것이 레거시 관리자 대시보드를 얻는 유일한 지원되는 방법이라는 제 추측이 맞습니까?
특히 저는 이전의 행복한/중립적인/슬픈 업데이트 상태 표시기를 매우 좋아합니다.
\ndashboard_improvements가 Permanent이 되면, 해당 업데이트 상태 표시를 포함한 레거시 대시보드를 완전히 제거할 의도인지, 아니면 해당 정보를 볼 수 있는 다른 지원되는 방법이 있는지 궁금합니다.
![\"image\"](\"https://global.discourse-cdn.com/meta/original/4X/d/d/1/dd13b6d05ef02a54c75dcdbf50333e4811f33f11.png\")
![\"IMG_4319\"](\"https://global.discourse-cdn.com/meta/original/4X/4/6/f/46f4ca728d37e5c2524e779752403642f1d9678c.jpeg\")
\n대시보드 개선\n\n커뮤니티의 성공과 가치를 기반으로 한 사이트 트래픽, 참여도 및 기타 분석 기능을 개선하고 사용자 정의 보고서를 고정할 수 있도록 재설계된 관리자 대시보드를 활성화합니다.\n\n피드백…\n\n⚠️ 이 변경 사항은 곧 영구적으로 적용됩니다. 더 이상 옵트아웃이 불가능합니다.\n\n안정적\n관리자\n기능\n\n활성화 대상…\n\n모두\n지금 Everyone(모두)을 No one(아무도)으로 변경하면 업데이트에 대한 슬픈/중립적인/행복한 얼굴 아이콘을 다시 볼 수 있을까요?
기존 동작을 기본값으로 유지하면서, 이를 열거형(enum) 사이트 설정으로 구현하는 것이 잘 작동할 수 있다고 생각합니다. 예를 들어, permanent_topic_deletion_mode 설정에서 현재와 같은 “각 게시물을 먼저 영구 삭제해야 함” 동작과, 선택적으로 “토픽과 모든 게시물을 영구 삭제” 동작을 제공할 수 있으며, 기존과 동일한 유형화된 확인 단계를 거치도록 할 수 있습니다. 이를 통해 기존 사이트의 현재 안전 정책을 유지하면서, 일괄 삭제를 명시적으로 원하는 관리자가 해당 기능을 선택적으로 사용할 수 있게 됩니다.
아마 그래서 기능 요청 사항인 것일까요 ![\":wink:\"](\"https://emoji.discourse-cdn.com/twitter/wink.png?v=15\" "\\":wink:\\"")
제가 이해하기로는, 이 요청은 Facebook 그룹에서 이미 사용하고 있는 기능과 완전히 동일합니다. 사용자는 원할 때 언제든지 자신의 게시물을 삭제할 수 있습니다. 게시물을 삭제한 사용자가 토픽/스레드를 시작한 경우, 해당 스레드의 모든 게시물도 함께 삭제됩니다. 삭제된 게시물에 답글이 있는 경우, 해당 답글들도 함께 삭제됩니다.
\n이러한 기능이 허용될지는 관리자의 선택 사항입니다. 요청은 없었지만, Facebook에서는 한 사람이 다른 사람의 작업을 동시에 삭제할 수 있기 때문에 이러한 기능이 매우 비호감으로 여겨집니다. 제 Facebook 그룹에서는 이러한 행위를 하는 경우 즉시 그룹에서 추방됩니다.
","post_number":6,"post_type":1,"posts_count":8,"updated_at":"2026-09-05T07:05:18.229Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":16,"readers_count":15,"score":8.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":"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":"","bookmarked":false,"raw":"As I understand this request is totally same functionality what Facebook groups are using. An user can delete own post when ever wanted so. If deleted one started a topic/thread then every posts will be deleted too. If deleted one is a post that has replies, those replies will be deleted too.\n\nWell, admin’s choise if such move will be allowed. Not asked, but in Facebook that is heavily hated becuse then one person can delete anothers work at same. In my FB-groups such action will lead immident kick out of that group.","actions_summary":[],"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":"제가 이해하기로는, 이 요청은 Facebook 그룹에서 이미 사용하고 있는 기능과 완전히 동일합니다. 사용자는 원할 때 언제든지 자신의 게시물을 삭제할 수 있습니다. 게시물을 삭제한 사용자가 토픽/스레드를 시작한 경우, 해당 스레드의 모든 게시물도 함께 삭제됩니다. 삭제된 게시물에 답글이 있는 경우, 해당 답글들도 함께 삭제됩니다. \n이러한 기능이 허용될지는 관리자의 선택 사항입니다. 요청은 없었지만, Facebook에서는 한 사람이 다른 사람의 작업을 동시에 삭제할 수 있기 때문에 이러한 기능이 매우 비호감으로 여겨집니다. 제 F…","truncated":true,"post_url":"/t/allow-user-to-delete-their-own-topic-at-any-time/411689/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":2034387,"name":"Ethan ","username":"Ethsim2","avatar_template":"/user_avatar/meta.discourse.org/ethsim2/{size}/522255_2.png","created_at":"2026-09-05T06:39:24.505Z","cooked":"정리가 안 될까 걱정된다면, 주제별 캘린더 대신 Events_calendar_categories 설정을 사용하길 권장합니다. 그리고 부모들은 아래 자동화를 통해 Discourse에 접근할 수 있습니다:
제 기억에 따르면, 답글이 있으면 아예 삭제할 수 없으니, 질문하신 내용이 뭔지 이해가 잘 안 됩니다.
","post_number":5,"post_type":1,"posts_count":8,"updated_at":"2026-09-05T06:24:03.272Z","reply_count":2,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":17,"readers_count":16,"score":18.4,"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":"emilio","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":"Afaik They can't delete at all if there are replies, so i don't understand your question.","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":41152,"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/allow-user-to-delete-their-own-topic-at-any-time/411689/5","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":2034384,"name":"Karthik K","username":"Karthik_K1","avatar_template":"/user_avatar/meta.discourse.org/karthik_k1/{size}/489159_2.png","created_at":"2026-09-05T05:53:46.109Z","cooked":"LiteLLM 워크어라운드가 잘 작동하므로, Vertex 방식은 작동하지 않는다는 점을 인지하고 이 주제를 닫겠습니다.
","post_number":17,"post_type":1,"posts_count":16,"updated_at":"2026-09-05T05:53:46.109Z","reply_count":0,"reply_to_post_number":16,"quote_count":0,"incoming_link_count":1,"reads":6,"readers_count":5,"score":21.2,"yours":false,"topic_id":411545,"topic_slug":"solving-gemini-api-key-errors-in-discourse","topic_title":"Discourse에서 Gemini API 키 오류 해결하기","topic_html_title":"Discourse에서 Gemini API 키 오류 해결하기","category_id":31,"display_username":"Karthik K","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":198618,"username":"Karthik_K1","name":"Karthik K","avatar_template":"/user_avatar/meta.discourse.org/karthik_k1/{size}/489159_2.png"},"bookmarked":false,"raw":"Closing this topic, though the Vertex method is not working, as the LiteLLM workaround is fine.","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":198618,"hidden":false,"trust_level":1,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"LiteLLM 워크어라운드가 잘 작동하므로, Vertex 방식은 작동하지 않는다는 점을 인지하고 이 주제를 닫겠습니다.","truncated":true,"post_url":"/t/solving-gemini-api-key-errors-in-discourse/411545/17","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":true},{"id":2034383,"name":"Karthik K","username":"Karthik_K1","avatar_template":"/user_avatar/meta.discourse.org/karthik_k1/{size}/489159_2.png","created_at":"2026-09-05T05:51:04.967Z","cooked":"가벼운 모델로 전환했는데, 이제 지연이 없어요. 감사합니다.
","post_number":16,"post_type":1,"posts_count":16,"updated_at":"2026-09-05T05:51:04.967Z","reply_count":1,"reply_to_post_number":15,"quote_count":0,"incoming_link_count":1,"reads":6,"readers_count":5,"score":11.2,"yours":false,"topic_id":411545,"topic_slug":"solving-gemini-api-key-errors-in-discourse","topic_title":"Discourse에서 Gemini API 키 오류 해결하기","topic_html_title":"Discourse에서 Gemini API 키 오류 해결하기","category_id":31,"display_username":"Karthik K","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":71041,"username":"satonotdead","name":"","avatar_template":"/user_avatar/meta.discourse.org/satonotdead/{size}/447830_2.png"},"bookmarked":false,"raw":"I switched to a lighter model, and there's no latency now. Thanks.","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":198618,"hidden":false,"trust_level":1,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"가벼운 모델로 전환했는데, 이제 지연이 없어요. 감사합니다.","truncated":true,"post_url":"/t/solving-gemini-api-key-errors-in-discourse/411545/16","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":true},{"id":2034381,"name":"Nate Dhaliwal","username":"NateDhaliwal","avatar_template":"/user_avatar/meta.discourse.org/natedhaliwal/{size}/313494_2.png","created_at":"2026-09-05T05:33:36.756Z","cooked":"Ask의 도움 덕분에 이렇게 하면 되는 것 같았습니다:
\n<Form\n+ @data={{hash content=this.rawPost}}\n @onSubmit={{this.handleSubmit}}\n as |form|\n>\nFormKit에서 composer 필드에 값을 미리 설정하는 방법은 무엇인가요? 아래 코드는 작동하지 않습니다:
<form.Field\n @name=\"content\"\n @validation=\"required\"\n @title=\" \"\n @type=\"composer\"\n @value={{this.rawPost}}\n as |field|\n>\n <field.Control @preview={{true}} />\n</form.Field>\nOver the last 24 hours, 74 new posts were published across 27 new topics, with 62 likes given.
\nTop users by likes received:
\n| User | \nPosts | \nLikes | \n
|---|---|---|
| Nicolsdennis | \n3 | \n8 | \n
| Per1234 | \n1 | \n7 | \n
| Lilly | \n9 | \n5 | \n
| Ed_S | \n2 | \n5 | \n
| Falco | \n1 | \n5 | \n
| Nat | \n2 | \n4 | \n
| Satonotdead | \n5 | \n3 | \n
| Jagster | \n3 | \n3 | \n
| HBP | \n1 | \n3 | \n
| Ethsim2 | \n5 | \n2 | \n
Also worth a glance: a comparison of Discourse MiniMod with category moderators, a broken-link report in the Transformers guide, an interaction bug with expanded markdown tables, ongoing review queue layout discussion, an Exposing LiveKit status request, a Git hang fix confirmation, a moderation “Yes” button question, and fresh feature requests on permanent deletion and self-deletion of topics.
\nVoice: Discord-style voice and video rooms, now bundled with Discourse — The Voice buzz continues! Newkid shared excitement about Voice for their real-estate community, and Jagster asked whether admins can delete rooms. Satonotdead confirmed admins can delete, rename, and gate rooms to specific groups.
\n![\":date:\"](\"https://emoji.discourse-cdn.com/twitter/date.png?v=15\" "\\":date:\\"")
New Calendar Feature: End Date for Recurring Events — MiniForum couldn’t find the new end-date option at first; Ethsim2 helpfully clarified the difference between Insert date/time and Create event, and pointed to an existing feature request that matches the school-calendar use case of recurring weekly appointments read more.
Granular permissions for cameras and screen sharing — Falco has a PR ready for this Voice feature request, bringing fine-grained camera and screen-sharing permissions closer to reality read more.
\nOption to enable search for logged in users only? — Nat submitted PR #43281, adding an allow_anonymous_search site setting that sends anons from /search to the login page. Mcwumbly agreed it’s “sufficient to address this request as a first step” read more.
Allow Category Moderator to add or remove Users from that Category — Heliosurge pointed to the Category Restrictor plugin as a workaround, and Happyhappy noted that limiting group membership may be enough without adding moderation powers read more.
\nRegression: new check_username rate limit can block normal signup flow — HBP's detailed report showed the new rate limit from PR #43042 can block legitimate signups after roughly 10 automatic username checks in a minute. Southpaw reassured: “We have a fix in the works”.
\nEditing event end date → post event date on topic title not updated — Ethsim2 opened PR #43285 with a thorough screen recording covering multiple start/end edit scenarios for event BBCode read more.
\nHow to fix the blank Ask AI response — Karthik_K1 logged Ask AI returning correct responses that never reach the UI; Nat diagnosed a likely request timeout caused by a 15.5-second response time. The issue reproduces only on desktop browsers so far read more.
\nSolving Gemini API key errors in Discourse — Karthik_K1 is wrestling with GCP credits via Vertex AI; Lilly demonstrated that a straightforward Gemini API config works fine, and Satonotdead vouched for LiteLLM proxy with zero latency.
\nProxyTracer: VPN & Proxy Blocker — A new beta adds CAPTCHA challenges (Cloudflare Turnstile + hCaptcha), independent clearance tokens, and Chart.js analytics. Eisammy offered to contribute VPN network intel while navigating LGPD compliance read more.
\nDiscourse Events — Jenmck flagged a regression where recurring events on the fourth Thursday can no longer be configured. Martin pointed to PR #42852 as the likely fix, with Davidb to investigate next week read more.
\nallow_anonymous_search site setting, and diagnosed a blank Ask AI response as a likely request timeout.From Voice rooms to calendar wrangling and VPN-blocking CAPTCHAs, it was a day of building, debugging, and birthday-wish launches — see you in the next 24 hours!
더 엄격해야 하는데 ![\":laughing:\"](\"https://emoji.discourse-cdn.com/twitter/laughing.png?v=15\" "\\":laughing:\\"")
그 모든 세부사항을 어디서 어떻게 수정해야 하는지는 알지만, 방을 삭제하는 방법은 모르겠어. 아니면 아직 초기 단계의 resenha(리뷰/평가) 단계에 머물러 있는 건가…
최근 UI 변경으로 보입니다. “예” 버튼은 중단 후 확인 작업을 위한 단순한 확인 동작일 수 있지만, 의도된 것인지 버그인지 확인하려면 스태프의 확인이 필요합니다.
","post_number":2,"post_type":1,"posts_count":3,"updated_at":"2026-09-05T04:56:11.982Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":13,"readers_count":12,"score":7.6,"yours":false,"topic_id":411693,"topic_slug":"moderation-yes-button-after-suspending-user","topic_title":"사용자 정지 후 '예' 버튼이 활성화되지 않음","topic_html_title":"사용자 정지 후 ‘예’ 버튼이 활성화되지 않음","category_id":9,"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":"Looks like a recent UI change. The “Yes” button may simply be a confirmation action after suspension, but staff would need to confirm whether it’s intentional or a bug.","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":202093,"hidden":false,"trust_level":0,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"최근 UI 변경으로 보입니다. “예” 버튼은 중단 후 확인 작업을 위한 단순한 확인 동작일 수 있지만, 의도된 것인지 버그인지 확인하려면 스태프의 확인이 필요합니다.","truncated":true,"post_url":"/t/moderation-yes-button-after-suspending-user/411693/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":2034376,"name":"Ed S","username":"Ed_S","avatar_template":"/user_avatar/meta.discourse.org/ed_s/{size}/134015_2.png","created_at":"2026-09-05T04:51:56.364Z","cooked":"다른 사람의 답장이 없는 경우에만 걱정하나요?
\n(대화가 언제든 삭제될 수 있으면 문제가 있습니다.)
","post_number":4,"post_type":1,"posts_count":8,"updated_at":"2026-09-05T04:51:56.364Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":18,"readers_count":17,"score":8.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":"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":"Are you only concerned about the case where there no replies from other people?\n\n(There's a problem if conversations can be deleted at any time.)","actions_summary":[],"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(대화가 언제든 삭제될 수 있으면 문제가 있습니다.)","truncated":true,"post_url":"/t/allow-user-to-delete-their-own-topic-at-any-time/411689/4","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":2034373,"name":"","username":"sterretje","avatar_template":"https://avatars.discourse-cdn.com/v4/letter/s/cdc98d/{size}.png","created_at":"2026-09-05T04:23:46.045Z","cooked":"안녕하세요
\n플래그: 사용자 승인 필요.
\n스팸으로 인해 사용자를 정지시킨 후, 현재 “예” 버튼이 남아 있습니다.
\n\n이 변경 사항은 GitHub - discourse/discourse at 5b61a1d4496d9ea51fcd6fd79f736dff530781ab · GitHub (또는 그 이전 버전)에서 발생한 것 같습니다.
\n참고:
\n문제를 이렇게 자세하고 명확하게 보고해 주셔서 감사합니다, @HBP! 현재 수정 작업을 진행 중입니다.
","post_number":4,"post_type":1,"posts_count":2,"updated_at":"2026-09-05T04:05:48.935Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":11,"readers_count":10,"score":22.2,"yours":false,"topic_id":411646,"topic_slug":"regression-new-check-username-rate-limit-can-block-normal-signup-flow","topic_title":"회귀 문제: 새로운 check_username 속도 제한이 정상적인 가입 흐름을 차단할 수 있음","topic_html_title":"회귀 문제: 새로운 check_username 속도 제한이 정상적인 가입 흐름을 차단할 수 있음","category_id":1,"display_username":"Southpaw","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":"Support Manager - Americas East & Oceania","title_is_group":false,"bookmarked":false,"raw":"Thank you for your very thorough and clear report of the issue, @HBP! We have a fix in the works.","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":true,"staff":true,"user_id":29739,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"문제를 이렇게 자세하고 명확하게 보고해 주셔서 감사합니다, @HBP! 현재 수정 작업을 진행 중입니다.","truncated":true,"post_url":"/t/regression-new-check-username-rate-limit-can-block-normal-signup-flow/411646/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":2034362,"name":"emilio","username":"emilio","avatar_template":"/user_avatar/meta.discourse.org/emilio/{size}/132550_2.png","created_at":"2026-09-05T03:41:41.970Z","cooked":"그래서 24시간 후에 삭제할 수 있도록 하는 것입니다. 더 명확하게 표현하는 방법을 모르겠습니다. 몇 주 동안 아무도 답글을 남기지 않는 경우도 있거든요. 24시간이라는 수치는 임의적으로 정한 것입니다. 그리고 매니저에게 요청하기 위해 플래깅을 해야 한다는 생각에는 동의하지 않습니다.
","post_number":3,"post_type":1,"posts_count":8,"updated_at":"2026-09-05T03:44:35.107Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":21,"readers_count":20,"score":9.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":"emilio","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":"So they can delete after 24 hours. I don'tknow how to make it more clear. Sometimes no one answers a post for weeks. 24 hrs is arbitrary. And I don't think flagging to beg a mod to do it should be needed.","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":41152,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"그래서 24시간 후에 삭제할 수 있도록 하는 것입니다. 더 명확하게 표현하는 방법을 모르겠습니다. 몇 주 동안 아무도 답글을 남기지 않는 경우도 있거든요. 24시간이라는 수치는 임의적으로 정한 것입니다. 그리고 매니저에게 요청하기 위해 플래깅을 해야 한다는 생각에는 동의하지 않습니다.","truncated":true,"post_url":"/t/allow-user-to-delete-their-own-topic-at-any-time/411689/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":2034357,"name":"Nate Dhaliwal","username":"NateDhaliwal","avatar_template":"/user_avatar/meta.discourse.org/natedhaliwal/{size}/313494_2.png","created_at":"2026-09-05T02:53:05.790Z","cooked":"\n\n이 링크들은 작동하지 않습니다. lib/transformers라는 경로는 존재하지 않습니다. lib/registry/transformers.js여야 합니다.
왜인가요? 이 결정의 근거는 무엇인가요?
\n그로 인해 어떤 이점이 얻어지나요?
","post_number":2,"post_type":1,"posts_count":8,"updated_at":"2026-09-05T02:41:26.721Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":22,"readers_count":21,"score":24.4,"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":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":"Why? What is the reasoning behind this?\n\nWhat advantage is gained from it?","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":176316,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"왜인가요? 이 결정의 근거는 무엇인가요? \n그로 인해 어떤 이점이 얻어지나요?","truncated":true,"post_url":"/t/allow-user-to-delete-their-own-topic-at-any-time/411689/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":2034335,"name":"emilio","username":"emilio","avatar_template":"/user_avatar/meta.discourse.org/emilio/{size}/132550_2.png","created_at":"2026-09-05T00:14:54.923Z","cooked":"사용자가 24시간 이내라는 임의의 시간 제한 없이 자신의 주제를 언제든 삭제할 수 있도록 허용하고 싶습니다.
","post_number":1,"post_type":1,"posts_count":8,"updated_at":"2026-09-05T00:14:54.923Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":5,"reads":29,"readers_count":28,"score":30.8,"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":"emilio","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":"Would like to allow user to delete their own topic indefinitely. Not the arbitrary within 24hrs timeframe.","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":41152,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"사용자가 24시간 이내라는 임의의 시간 제한 없이 자신의 주제를 언제든 삭제할 수 있도록 허용하고 싶습니다.","truncated":true,"post_url":"/t/allow-user-to-delete-their-own-topic-at-any-time/411689/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":2034326,"name":"emilio","username":"emilio","avatar_template":"/user_avatar/meta.discourse.org/emilio/{size}/132550_2.png","created_at":"2026-09-04T23:44:30.778Z","cooked":"게시물/토픽을 실제로 삭제할 수 있는 옵션이 있으면 좋겠습니다. 매번 삭제할 때마다 이런 식으로 막히니까 오히려 더 불편하거든요.
\n이 부분은 그냥 \"이런 결과가 생길 수 있다는 걸 알고도 삭제하고 싶다\"는 확인 체크박스 하나만 있으면 됩니다. 초장문 토픽에서 모든 게시물을 하나하나 수동으로 삭제해야 하는 상황을 강요하지 말아 주세요.
\n아니면 Reddit처럼 첫 번째 게시물만 실제로 삭제해서 비워둘 수 있으면 좋겠습니다.
\n\n\"하지만 다른 사용자나 후세를 위해 답변이 중요할 수 있다\"고 말하는 사람들이 많을 거라는 건 알겠어요. 하지만 그게 얼마나 중요하지 않은지 강조하고 싶고, 모든 답변이 삭제되는 건 전혀 신경 쓰지 않습니다.
\n그리고 이걸 모든 게시물에 대해 반복해서 해야 하는 것도 안 됩니다.
\n","post_number":1,"post_type":1,"posts_count":3,"updated_at":"2026-09-04T23:46:24.274Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":2,"reads":32,"readers_count":31,"score":91.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":"emilio","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":"Would love an option to actually delete post/topic, without being stuck at every turn to do so its making it harder.\n\nThis should just have a checkbox to say I am aware that will happen and want to anyway. Not force me to potentially have to manually delete every post in super long topics\n\n\nor like Reddit I should be able to really delete just the first post make it empty.\n\n\n\nI understand there will be many that say something like \"but the replies may be important for others/posterity\". I cannot stress how little that matters and we just don't care if all the replies are deleted.\n\nand should not have to do this for every single post\n\n","actions_summary":[{"id":2,"count":3}],"moderator":false,"admin":false,"staff":false,"user_id":41152,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"게시물/토픽을 실제로 삭제할 수 있는 옵션이 있으면 좋겠습니다. 매번 삭제할 때마다 이런 식으로 막히니까 오히려 더 불편하거든요. \n이 부분은 그냥 "이런 결과가 생길 수 있다는 걸 알고도 삭제하고 싶다"는 확인 체크박스 하나만 있으면 됩니다. 초장문 토픽에서 모든 게시물을 하나하나 수동으로 삭제해야 하는 상황을 강요하지 말아 주세요. \n아니면 Reddit처럼 첫 번째 게시물만 실제로 삭제해서 비워둘 수 있으면 좋겠습니다. \n [Why_is_a_4k_movie_called_as_HD_…ow__-_Plex_Players_-_Plex_…","truncated":true,"post_url":"/t/actually-delete-permanently-without-all-the-obstacles/411687/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":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,"can_vote":true},{"id":2034299,"name":null,"username":"MiniForum","avatar_template":"https://avatars.discourse-cdn.com/v4/letter/m/0ea827/{size}.png","created_at":"2026-09-04T21:54:36.384Z","cooked":"고마워요, 그렇게 할게요!
","post_number":14,"post_type":1,"posts_count":15,"updated_at":"2026-09-04T21:54:36.384Z","reply_count":1,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":12,"readers_count":11,"score":12.4,"yours":false,"topic_id":368527,"topic_slug":"new-calendar-feature-end-date-for-recurring-events","topic_title":"📅 새 캘린더 기능: 반복 이벤트 종료 날짜","topic_html_title":":date: 새 캘린더 기능: 반복 이벤트 종료 날짜","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":"Thanks, I'll do that !","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":202262,"hidden":false,"trust_level":1,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"고마워요, 그렇게 할게요!","truncated":true,"post_url":"/t/new-calendar-feature-end-date-for-recurring-events/368527/14","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":2034293,"name":"Ethan ","username":"Ethsim2","avatar_template":"/user_avatar/meta.discourse.org/ethsim2/{size}/522255_2.png","created_at":"2026-09-04T21:40:18.101Z","cooked":"네 — 불행히도 API를 사용하면 답글 생성은 자동화되지만, 혼란 문제는 실제로 해결되지 않습니다. 토픽 캘린더의 경우 개별 캘린더 항목이 여전히 개별 답글로 표시되므로요.
\n다행히도 거의 동일한 사용 사례를 다루는 기존 기능 요청을 찾았습니다:
\n\n\n이 예시에서는 12주 연속 수요일에 진행되는 과정을 다루고 있으며, 동일한 점을 지적하고 있습니다. 즉, 모든 발생 건을 개별적으로 생성하는 것은 번거롭고 토픽을 혼란스럽게 만듭니다.
\n그들은 날짜/시간 삽입에서 반복 설정을 허용하고, 마지막 발생 건을 위한 종료 날짜를 함께 지정할 수 있도록 제안하고 있는데, 이는 귀하가 필요로 하는 것과 매우 유사해 보입니다.
\n따라서 52개의 게시물을 생성하는 API/Power Automate 우회 솔루션을 구축하는 것보다는, 해당 기능 요청에 학교 캘린더 사용 사례를 추가하는 것이 더 나은 선택일 것입니다.
","post_number":13,"post_type":1,"posts_count":15,"updated_at":"2026-09-04T21:40:18.101Z","reply_count":0,"reply_to_post_number":12,"quote_count":0,"incoming_link_count":1,"reads":12,"readers_count":11,"score":22.4,"yours":false,"topic_id":368527,"topic_slug":"new-calendar-feature-end-date-for-recurring-events","topic_title":"📅 새 캘린더 기능: 반복 이벤트 종료 날짜","topic_html_title":":date: 새 캘린더 기능: 반복 이벤트 종료 날짜","category_id":67,"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,"reply_to_user":{"id":202262,"username":"MiniForum","name":null,"avatar_template":"https://avatars.discourse-cdn.com/v4/letter/m/0ea827/{size}.png"},"bookmarked":false,"raw":"Yes - unfortunately the API would automate creating the replies, but it wouldn't really solve the clutter problem: for a topic calendar the individual calendar entries are still represented by individual replies.\n\nI've just found an existing feature request which is almost exactly your use case:\n\nhttps://meta.discourse.org/t/add-recurrent-items-within-a-date-range/286514\n\nTheir example is a course occurring on twelve consecutive Wednesdays, and they make the same point: creating every occurrence individually is tedious and clutters the topic.\n\nThey suggest allowing recurrence in **Insert date / time** together with an end date for the final occurrence, which sounds very close to what you need.\n\nSo rather than building an API/Power Automate workaround that generates 52 posts, that feature request is probably the better place to add your school-calendar use case.","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":"네 — 불행히도 API를 사용하면 답글 생성은 자동화되지만, 혼란 문제는 실제로 해결되지 않습니다. 토픽 캘린더의 경우 개별 캘린더 항목이 여전히 개별 답글로 표시되므로요. \n다행히도 거의 동일한 사용 사례를 다루는 기존 기능 요청을 찾았습니다: \n\n\n이 예시에서는 12주 연속 수요일에 진행되는 과정을 다루고 있으며, 동일한 점을 지적하고 있습니다. 즉, 모든 발생 건을 개별적으로 생성하는 것은 번거롭고 토픽을 혼란스럽게 만듭니다. \n그들은 날짜/시간 삽입에서 반복 설정을 허용하고, 마지막 발생 건을 위한 종료 날짜를 함께 지정할 …","truncated":true,"post_url":"/t/new-calendar-feature-end-date-for-recurring-events/368527/13","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":2034291,"name":null,"username":"MiniForum","avatar_template":"https://avatars.discourse-cdn.com/v4/letter/m/0ea827/{size}.png","created_at":"2026-09-04T21:35:50.082Z","cooked":"아직 한 번만 그런 일이 있었으니, 다음에 다시 발생하면 그때까지 기다리겠습니다(다시 일어나지 않기를 바라며).
\n이메일로 답장하는 방법은 유지하겠습니다. 감사합니다. 그런데 일 년 내내 매주 열리는 이벤트의 경우, 52개의 답장을 모두 생성해야 한다는 뜻인가요? 그러면 주제가 읽기 힘들어질 것 같은데…
\n그 외에는 관리자 권한이 있으므로 API를 통해 예약을 수동으로 추가하는 방법도 사용할 수 있을 것 같습니다.
\n알려주셔서 감사합니다!
","post_number":12,"post_type":1,"posts_count":15,"updated_at":"2026-09-04T21:35:50.082Z","reply_count":1,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":11,"readers_count":10,"score":7.2,"yours":false,"topic_id":368527,"topic_slug":"new-calendar-feature-end-date-for-recurring-events","topic_title":"📅 새 캘린더 기능: 반복 이벤트 종료 날짜","topic_html_title":":date: 새 캘린더 기능: 반복 이벤트 종료 날짜","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":"It only happened once at the moment, so I'll wait until next time (and hope that it won't happen again).\n\nI'll keep the reply-by-email trick, thanks. But does that mean that for an event every week for a whole year, we'll have to generate 52 replies ? It will make the topic difficult to read...\n\nOtherwise I suppose, as I have admin rights, that I can also use the API to add manually the appointments.\n\nThanks for the insights !","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":202262,"hidden":false,"trust_level":1,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"아직 한 번만 그런 일이 있었으니, 다음에 다시 발생하면 그때까지 기다리겠습니다(다시 일어나지 않기를 바라며). \n이메일로 답장하는 방법은 유지하겠습니다. 감사합니다. 그런데 일 년 내내 매주 열리는 이벤트의 경우, 52개의 답장을 모두 생성해야 한다는 뜻인가요? 그러면 주제가 읽기 힘들어질 것 같은데… \n그 외에는 관리자 권한이 있으므로 API를 통해 예약을 수동으로 추가하는 방법도 사용할 수 있을 것 같습니다. \n알려주셔서 감사합니다!","truncated":true,"post_url":"/t/new-calendar-feature-end-date-for-recurring-events/368527/12","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":2034287,"name":"Ed Kelly","username":"apidevlab","avatar_template":"/user_avatar/meta.discourse.org/apidevlab/{size}/423316_2.png","created_at":"2026-09-04T21:24:31.532Z","cooked":"@Lilly 감사합니다. 그런 건 어느 정도 예상하고 있었어요. 오늘은 좀 지쳤으니 내일 전체 로그를 올리겠습니다. 정보 주셔서 감사합니다.
","post_number":8,"post_type":1,"posts_count":8,"updated_at":"2026-09-04T21:24:31.532Z","reply_count":0,"reply_to_post_number":7,"quote_count":0,"incoming_link_count":1,"reads":14,"readers_count":13,"score":22.8,"yours":false,"topic_id":411664,"topic_slug":"fresh-install-hetzner-vps-failing","topic_title":"신규 설치 (Hetzner VPS) 실패","topic_html_title":"신규 설치 (Hetzner VPS) 실패","category_id":6,"display_username":"Ed Kelly","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":127856,"username":"Lilly","name":"Lillian ","avatar_template":"/user_avatar/meta.discourse.org/lilly/{size}/575047_2.png"},"bookmarked":false,"raw":"@Lilly Thanks, I sort of expected that. I have had enough today, so I will post full logs tomorrow, but thankyou for the info.","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":150614,"hidden":false,"trust_level":1,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"@Lilly 감사합니다. 그런 건 어느 정도 예상하고 있었어요. 오늘은 좀 지쳤으니 내일 전체 로그를 올리겠습니다. 정보 주셔서 감사합니다.","truncated":true,"post_url":"/t/fresh-install-hetzner-vps-failing/411664/8","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"hugs","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":2034284,"name":"Lillian ","username":"Lilly","avatar_template":"/user_avatar/meta.discourse.org/lilly/{size}/575047_2.png","created_at":"2026-09-04T21:21:01.604Z","cooked":"\n마지막 에러 메시지만 있는 것이 아니라, 부트스트랩 실패에 대한 전체 출력 코드가 필요합니다. 빌드를 시도할 때 시스템이 출력하는 모든 내용을 그대로 올려주세요.
","post_number":7,"post_type":1,"posts_count":8,"updated_at":"2026-09-04T21:21:01.604Z","reply_count":1,"reply_to_post_number":6,"quote_count":1,"incoming_link_count":1,"reads":14,"readers_count":13,"score":42.8,"yours":false,"topic_id":411664,"topic_slug":"fresh-install-hetzner-vps-failing","topic_title":"신규 설치 (Hetzner VPS) 실패","topic_html_title":"신규 설치 (Hetzner VPS) 실패","category_id":6,"display_username":"Lillian ","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":150614,"username":"apidevlab","name":"Ed Kelly","avatar_template":"/user_avatar/meta.discourse.org/apidevlab/{size}/423316_2.png"},"bookmarked":false,"raw":"[quote=\"apidevlab, post:1, topic:411664\"]\n```\n** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one.\n\n```\n[/quote]\n\nwe need the whole failed bootstrap output code, not just that last error message. just post everything that the system spits out when you attempt to build.","actions_summary":[{"id":2,"count":2}],"moderator":false,"admin":false,"staff":false,"user_id":127856,"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/fresh-install-hetzner-vps-failing/411664/7","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"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":2034282,"name":"Ethan ","username":"Ethsim2","avatar_template":"/user_avatar/meta.discourse.org/ethsim2/{size}/522255_2.png","created_at":"2026-09-04T21:19:28.603Z","cooked":"기존의 토픽 단위 [calendar] 워크플로를 유지하면서 수동 답변을 자동화하는 방법이 있을 수 있습니다.
한 가지 가능성은 이메일로 답변할 수 있는 기능이 활성화된 전용 Discourse 사용자를 만들고, Power Automate나 Azure Logic App과 같은 도구를 사용하여 날짜가 포함된 개별 답변을 생성한 뒤 이메일을 통해 캘린더 토픽으로 전송하는 것입니다.
\n예를 들어, 종료일이 있는 주간 예약은 자동화 도구를 통해 필요한 개별 답변으로 확장될 수 있습니다. 이렇게 하면 학부모들은 분리된 이벤트 토픽이 아닌, 평소와 같은 단일 토픽 캘린더를 볼 수 있습니다.
\nDiscourse의 사용자별 이메일 답변 키 설정과 관련하여 주의 깊게 구성해야 할 세부 사항이 몇 가지 있으므로, 이 토픽에서 구성 과정을 자세히 다루기는 적절하지 않을 수 있습니다.
\n이 방식이 유용할 것 같다면, 별도의 메타 토픽에서 함께 해결하는 것을 기꺼이 도와드리겠습니다.
","post_number":11,"post_type":1,"posts_count":15,"updated_at":"2026-09-04T21:19:28.603Z","reply_count":0,"reply_to_post_number":10,"quote_count":0,"incoming_link_count":0,"reads":11,"readers_count":10,"score":2.2,"yours":false,"topic_id":368527,"topic_slug":"new-calendar-feature-end-date-for-recurring-events","topic_title":"📅 새 캘린더 기능: 반복 이벤트 종료 날짜","topic_html_title":":date: 새 캘린더 기능: 반복 이벤트 종료 날짜","category_id":67,"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,"reply_to_user":{"id":202262,"username":"MiniForum","name":null,"avatar_template":"https://avatars.discourse-cdn.com/v4/letter/m/0ea827/{size}.png"},"bookmarked":false,"raw":"There may be a way to automate the manual replies while keeping your existing topic-local `[calendar]` workflow.\n\nOne possibility would be to use a dedicated Discourse user with reply-by-email enabled, then have something such as **Power Automate** or an **Azure Logic App** generate the individual dated replies and send them into the calendar topic by email.\n\nFor example, a weekly appointment with an end date could be expanded by the automation into the required individual replies, so parents would still see one normal topic calendar rather than separate Event topics.\n\nThere are a few details around Discourse's per-user reply-by-email keys that would need to be set up carefully, so this topic probably isn't the best place to go through the configuration.\n\nIf that approach would be useful to you, I'm happy to help work through it in a separate Meta topic.","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":"기존의 토픽 단위 [calendar] 워크플로를 유지하면서 수동 답변을 자동화하는 방법이 있을 수 있습니다. \n한 가지 가능성은 이메일로 답변할 수 있는 기능이 활성화된 전용 Discourse 사용자를 만들고, Power Automate나 Azure Logic App과 같은 도구를 사용하여 날짜가 포함된 개별 답변을 생성한 뒤 이메일을 통해 캘린더 토픽으로 전송하는 것입니다. \n예를 들어, 종료일이 있는 주간 예약은 자동화 도구를 통해 필요한 개별 답변으로 확장될 수 있습니다. 이렇게 하면 학부모들은 분리된 이벤트 토픽이 아닌, 평…","truncated":true,"post_url":"/t/new-calendar-feature-end-date-for-recurring-events/368527/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":2034280,"name":"Ed Kelly","username":"apidevlab","avatar_template":"/user_avatar/meta.discourse.org/apidevlab/{size}/423316_2.png","created_at":"2026-09-04T21:18:55.121Z","cooked":"거의 포기한 상태입니다. 어떤 정보가 필요한 건가요? 말씀드린 대로 로그와 커맨드라인 입력/출력 제공에는 문제없습니다. 새 설치조차 실패해서 저도 당황하고 있습니다.
\n이전에는 이런 문제가 없었습니다. 이건 Podman 설치가 아니라 1줄 설치기를 사용한 ‘공식’ 버전입니다.
","post_number":6,"post_type":1,"posts_count":8,"updated_at":"2026-09-04T21:20:09.474Z","reply_count":1,"reply_to_post_number":4,"quote_count":0,"incoming_link_count":1,"reads":14,"readers_count":13,"score":12.8,"yours":false,"topic_id":411664,"topic_slug":"fresh-install-hetzner-vps-failing","topic_title":"신규 설치 (Hetzner VPS) 실패","topic_html_title":"신규 설치 (Hetzner VPS) 실패","category_id":6,"display_username":"Ed Kelly","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":127856,"username":"Lilly","name":"Lillian ","avatar_template":"/user_avatar/meta.discourse.org/lilly/{size}/575047_2.png"},"bookmarked":false,"raw":"I have pretty much given up on it. What sort of info is needed? Like I said happy to provide logs and command-line inputs/outputs; it has me stumped even a clean install is failing.\n\nNever had it before. This NOT a Podman install it's an 'official' version using the 1 line installer","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":150614,"hidden":false,"trust_level":1,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"거의 포기한 상태입니다. 어떤 정보가 필요한 건가요? 말씀드린 대로 로그와 커맨드라인 입력/출력 제공에는 문제없습니다. 새 설치조차 실패해서 저도 당황하고 있습니다. \n이전에는 이런 문제가 없었습니다. 이건 Podman 설치가 아니라 1줄 설치기를 사용한 ‘공식’ 버전입니다.","truncated":true,"post_url":"/t/fresh-install-hetzner-vps-failing/411664/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":2034279,"name":"Lillian ","username":"Lilly","avatar_template":"/user_avatar/meta.discourse.org/lilly/{size}/575047_2.png","created_at":"2026-09-04T21:18:06.087Z","cooked":"\nPodman 설치도 지원되지 않으므로 버그가 있는 것은 놀라운 일이 아닙니다. 이 설치 구성에 대한 지원을 받는 것은 어려울 것입니다.
","post_number":5,"post_type":1,"posts_count":8,"updated_at":"2026-09-04T21:18:06.087Z","reply_count":0,"reply_to_post_number":null,"quote_count":1,"incoming_link_count":1,"reads":13,"readers_count":12,"score":22.6,"yours":false,"topic_id":411664,"topic_slug":"fresh-install-hetzner-vps-failing","topic_title":"신규 설치 (Hetzner VPS) 실패","topic_html_title":"신규 설치 (Hetzner VPS) 실패","category_id":6,"display_username":"Lillian ","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=\"apidevlab, post:1, topic:411664\"]\nVirtualmin has also launched a new Podman module with a Discourse recipe that works but is a little bit buggy.\n[/quote]\n\nalso podman installs are unsupported so it's not surprising that it's buggy. you will have a difficult time getting support for this install configuration.","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":127856,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Podman 설치도 지원되지 않으므로 버그가 있는 것은 놀라운 일이 아닙니다. 이 설치 구성에 대한 지원을 받는 것은 어려울 것입니다.","truncated":true,"post_url":"/t/fresh-install-hetzner-vps-failing/411664/5","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":2034276,"name":"Lillian ","username":"Lilly","avatar_template":"/user_avatar/meta.discourse.org/lilly/{size}/575047_2.png","created_at":"2026-09-04T21:15:18.851Z","cooked":"더 많은 정보가 필요합니다. 실패한 부트스트랩 코드를 전체적으로 올려 주세요.
\nHetzner에 설치하는 것은 매우 쉽습니다. 저는 Hetzner만 사용하고 있습니다.
","post_number":4,"post_type":1,"posts_count":8,"updated_at":"2026-09-04T21:16:54.702Z","reply_count":1,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":14,"readers_count":13,"score":22.8,"yours":false,"topic_id":411664,"topic_slug":"fresh-install-hetzner-vps-failing","topic_title":"신규 설치 (Hetzner VPS) 실패","topic_html_title":"신규 설치 (Hetzner VPS) 실패","category_id":6,"display_username":"Lillian ","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":"we need more info. post the entire failed bootstrap code. \n\ninstalling on Hetzner is super easy. i use it exclusively.","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":127856,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"더 많은 정보가 필요합니다. 실패한 부트스트랩 코드를 전체적으로 올려 주세요. \nHetzner에 설치하는 것은 매우 쉽습니다. 저는 Hetzner만 사용하고 있습니다.","truncated":true,"post_url":"/t/fresh-install-hetzner-vps-failing/411664/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":2034266,"name":null,"username":"MiniForum","avatar_template":"https://avatars.discourse-cdn.com/v4/letter/m/0ea827/{size}.png","created_at":"2026-09-04T21:06:29.059Z","cooked":"네, 이해했습니다.
\n사용 사례는 제 학교의 달력을 관리하는 것입니다. 항상 입력해야 할 일정이 있으므로, 학부모 누구나 주제에 답글을 달아 새로운 일정을 추가할 수 있습니다.
\n하지만 어제 반복되는 일정을 입력해야 했는데, 불행히도 이 워크플로우에는 그런 옵션이 없습니다. 그래서 새 날짜로 주제를 여러 번 답글을 달아 수동으로 처리해야 합니다(더 현명한 방법이 있는지 모르겠네요…).
","post_number":10,"post_type":1,"posts_count":15,"updated_at":"2026-09-04T21:06:29.059Z","reply_count":1,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":11,"readers_count":10,"score":12.2,"yours":false,"topic_id":368527,"topic_slug":"new-calendar-feature-end-date-for-recurring-events","topic_title":"📅 새 캘린더 기능: 반복 이벤트 종료 날짜","topic_html_title":":date: 새 캘린더 기능: 반복 이벤트 종료 날짜","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":"Yes I understand.\n\nThe use case is to maintain a calendar for my school. There are always appointments to be entered and so any parent can reply to the topic to add a new appointment.\n\nBut just yesterday, I needed to enter a recurring appointment and unfortunately we don't have this option in this workflow. So I have to do it manually by replying many times to the topic with a new date (don't know if there is a clever way...).","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":202262,"hidden":false,"trust_level":1,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"네, 이해했습니다. \n사용 사례는 제 학교의 달력을 관리하는 것입니다. 항상 입력해야 할 일정이 있으므로, 학부모 누구나 주제에 답글을 달아 새로운 일정을 추가할 수 있습니다. \n하지만 어제 반복되는 일정을 입력해야 했는데, 불행히도 이 워크플로우에는 그런 옵션이 없습니다. 그래서 새 날짜로 주제를 여러 번 답글을 달아 수동으로 처리해야 합니다(더 현명한 방법이 있는지 모르겠네요…).","truncated":true,"post_url":"/t/new-calendar-feature-end-date-for-recurring-events/368527/10","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":2034248,"name":"system","username":"system","avatar_template":"/user_avatar/meta.discourse.org/system/{size}/443519_2.png","created_at":"2026-09-04T21:01:06.288Z","cooked":"Over the past 24 hours, the community produced 155 posts across 51 new topics, with 136 likes given on returned posts.
\nTop users by posts and likes:
\nSatonotdead walked users through enabling and finding the new bundled Voice rooms, with Newkid praising the feature for their real estate community and Jagster asking whether admins can delete rooms — which Satonotdead confirmed, adding that room titles, slugs, and group limits can also be managed in the Voice announcement topic.
\nRishabh unveiled the Discourse Admin Assistant, an LLM-powered chat helper for hosted sites that can answer documentation questions, change settings with an approve/cancel prompt, assist with moderation, and explain hosting plan details to admins.
\nGilles praised the new Workflows feature preview as powerful and intuitive, and suggested creating a dedicated space for workflow sharing; Eviepayne pointed to an open request for such a category.
\nEd_S reported growing numbers of pitchfork worker timeouts linked to the GitHub outage, while Satonotdead confirmed Git authentication failures; Falco traced it to an over-eager feature check and merged a fix, after Jeanas noted that a GitHub outage should never take down a Discourse forum in the first place.
\nApidevlab asked for help with a fresh Hetzner VPS install failing during bootstrap, posting memory and disk diagnostics but no full log; Jagster and Ed_S advised scrolling up for the real error before anyone could diagnose the failure.
\nBOUCUR shared a community report about post and topic links no longer appearing under Badges, such as “Nice Reply” and “Nice Topic,” and confirmed the same issue exists here on Meta.
\nJagster hit PG::UndefinedTable errors for 0 after upgrading a two-container install; Nat identified leftover Resenha plugin migration conflicts and supplied a SQL script to rename the old tables, which resolved the issue.
\nPeter_Backgren and Lunikon described GitHub-caused 1 hangs and locked-out admins on self-hosted forums; Taste-OF-IT confirmed a retry eventually rebuilt and brought the site back online.
\nFabien_1015 reported persistent Error 500s after upgrading to v2026.9.0 on users.scala-lang.org, with the problem temporarily solved by deleting the _t cookie; Merefield asked for the actual backtrace from /logs before offering a fix.
Opcourdis pushed for archiving completed recurring event topics and creating successor topics, and Ethsim2 responded with an opt-in 4 PR that preserves the completed occurrence while advancing the series.
\nMcwumbly revived the request for logged-in-only search after noting the pain anonymous search abuse causes; Nat agreed and opened a PR adding allow_anonymous_search while keeping group-based internal search logic manageable.
HBP reported a regression in the signup flow caused by a new 10-per-minute IP rate limit on /u/check_username.json, which can block legitimate users who edit or correct their username while creating an account.
Ethsim2 investigated the wrong +1h Outlook ICS export with TZID=Europe/Berlin and opened a PR adding VTIMEZONE definitions so Outlook can interpret daylight-saving rules correctly.
\nThe Team group had a full day of fixes, guidance, and shipping.
\nFalco merged a fix for the GitHub-caused pitchfork and login hang, explaining that the issue was triggered by an over-eager feature check while GitHub was down.
\nFalco closed out several older requests by pointing to the new bundled Voice plugin, including HIRING: Voice Chat/Call Feature, Discourse Group Voice Chat, and Video Conference Call.
\nFalco helped a developer use rooms.json to check LiveKit transport status and confirmed expected_transport is the intended field for distinguishing LiveKit from mesh rooms, then shared a PR for granular camera and screen permissions.
Nat diagnosed the upgrade dead-end caused by Voice plugin migrations conflicting with leftover Resenha plugin versions, and provided a SQL rename script for affected self-hosters.
\nNat proposed 9 to let sites disable anonymous search while preserving search for logged-in users, after Mcwumbly raised the anonymous-search griefing problem.
\nNat traced blank Ask AI responses to a 20-second request deadline being exceeded by a slow LLM response, advising Karthik_K1 to test with a faster provider.
\nMartin opened a draft PR for more concise inline subcategory links with hover cards, then updated the thread after Mcwumbly suggested showing the full parent path only in the card.
\nMartin fixed an issue in the unified New view topic list after it was announced.
\nMartin confirmed a fix for recurring event weekday selection issues, with follow-up investigation planned by Davidb next week.
\nPmusaraj published the LiveKit integration guide, explaining how to configure voice_livekit_room_policy, webhooks, and recording settings step by step.
Rishabh announced the Discourse Admin Assistant, describing its moderation actions, site setting changes, and hosting plan awareness for hosted admins.
\nYesterday the forum learned that even GitHub can stumble, but with a little pitchfork wrangling and a fresh set of voice rooms, Discourse is still standing — and now it can talk about it too!
","post_number":974,"post_type":1,"posts_count":716,"updated_at":"2026-09-04T21:01:06.288Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":3,"readers_count":2,"score":0.4,"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\nOver the past 24 hours, the community produced **155 posts** across **51 new topics**, with **136 likes** given on returned posts.\n\nTop users by posts and likes:\n\n- Falco — **16 posts**, **23 likes**\n- Nicolsdennis — **6 posts**, **9 likes**\n- Ed_S — **6 posts**, **8 likes**\n- Rishabh — **1 post**, **8 likes**\n- Satonotdead — **11 posts**, **7 likes**\n- Per1234 — **1 post**, **7 likes**\n- Mcwumbly — **5 posts**, **6 likes**\n- Nat — **5 posts**, **6 likes**\n- Jagster — **9 posts**, **5 likes**\n- Ethsim2 — **8 posts**, **5 likes**\n\n## Interesting Topics\n\n### #Announcements\n\n- Satonotdead walked users through [enabling and finding the new bundled Voice rooms](https://meta.discourse.org/t/-/411337/18?silent=true), with Newkid praising the feature for their real estate community and Jagster asking whether admins can delete rooms — which Satonotdead confirmed, adding that room titles, slugs, and group limits can also be managed in the [Voice announcement topic](https://meta.discourse.org/t/-/411337/1?silent=true).\n\n- Rishabh unveiled the [Discourse Admin Assistant](https://meta.discourse.org/t/-/410439/1?silent=true), an LLM-powered chat helper for hosted sites that can answer documentation questions, change settings with an approve/cancel prompt, assist with moderation, and explain hosting plan details to admins.\n\n- Gilles praised the [new Workflows feature preview](https://meta.discourse.org/t/-/406990/26?silent=true) as powerful and intuitive, and suggested creating a dedicated space for workflow sharing; Eviepayne pointed to an [open request for such a category](https://meta.discourse.org/t/-/408415?silent=true).\n\n### #Support\n\n- Ed_S reported growing numbers of pitchfork worker timeouts linked to the GitHub outage, while Satonotdead confirmed Git authentication failures; Falco traced it to an over-eager feature check and [merged a fix](https://meta.discourse.org/t/-/411513/20?silent=true), after Jeanas noted that a GitHub outage should never take down a Discourse forum in the first place.\n\n- Apidevlab asked for help with [a fresh Hetzner VPS install failing during bootstrap](https://meta.discourse.org/t/-/411664/1?silent=true), posting memory and disk diagnostics but no full log; Jagster and Ed_S advised scrolling up for the real error before anyone could diagnose the failure.\n\n- BOUCUR shared a community report about [post and topic links no longer appearing under Badges](https://meta.discourse.org/t/-/411593/1?silent=true), such as “Nice Reply” and “Nice Topic,” and confirmed the same issue exists here on Meta.\n\n### #Self-hosting\n\n- Jagster hit [PG::UndefinedTable errors for 0](https://meta.discourse.org/t/-/411555/1?silent=true) after upgrading a two-container install; Nat identified leftover Resenha plugin migration conflicts and supplied a [SQL script to rename the old tables](https://meta.discourse.org/t/-/411555/8?silent=true), which resolved the issue.\n\n- Peter_Backgren and Lunikon described [GitHub-caused 1 hangs and locked-out admins](https://meta.discourse.org/t/-/411498/8?silent=true) on self-hosted forums; Taste-OF-IT confirmed a retry eventually rebuilt and brought the site back online.\n\n- Fabien_1015 reported persistent [Error 500s after upgrading to v2026.9.0](https://meta.discourse.org/t/-/411566/1?silent=true) on users.scala-lang.org, with the problem temporarily solved by deleting the `_t` cookie; Merefield asked for the actual backtrace from `/logs` before offering a fix.\n\n### #Feature\n\n- Opcourdis pushed for [archiving completed recurring event topics and creating successor topics](https://meta.discourse.org/t/-/370600/10?silent=true), and Ethsim2 responded with an [opt-in 4 PR](https://github.com/discourse/discourse/pull/43187) that preserves the completed occurrence while advancing the series.\n\n- Mcwumbly revived the [request for logged-in-only search](https://meta.discourse.org/t/-/256772/9?silent=true) after noting the pain anonymous search abuse causes; Nat agreed and opened a PR adding `allow_anonymous_search` while keeping group-based internal search logic manageable.\n\n### #Bug\n\n- HBP reported a [regression in the signup flow](https://meta.discourse.org/t/-/411646/1?silent=true) caused by a new 10-per-minute IP rate limit on `/u/check_username.json`, which can block legitimate users who edit or correct their username while creating an account.\n\n- Ethsim2 investigated the [wrong +1h Outlook ICS export with TZID=Europe/Berlin](https://meta.discourse.org/t/-/409797/5?silent=true) and opened a [PR adding VTIMEZONE definitions](https://github.com/discourse/discourse/pull/43168) so Outlook can interpret daylight-saving rules correctly.\n\n### #Integrations\n\n- Pmusaraj published a detailed guide to [integrating Discourse Voice with LiveKit](https://meta.discourse.org/t/-/411585/1?silent=true), covering room policies, mesh fallback, webhooks, and LiveKit Egress recording settings.\n\n### #Community Building\n\n- Per1234 shared an importable [Discourse Update Notifier workflow](https://meta.discourse.org/t/-/410589/13?silent=true) in the “Show us your Workflows” topic, complete with a JSON download and a live demonstration on Arduino’s forum.\n\n## Activity by the Team Group\n\nThe Team group had a full day of fixes, guidance, and shipping.\n\n- Falco [merged a fix](https://meta.discourse.org/t/-/411513/20?silent=true) for the GitHub-caused pitchfork and login hang, explaining that the issue was triggered by an over-eager feature check while GitHub was down.\n\n- Falco closed out several older requests by pointing to the [new bundled Voice plugin](https://meta.discourse.org/t/-/411337/1?silent=true), including [HIRING: Voice Chat/Call Feature](https://meta.discourse.org/t/-/91252/6?silent=true), [Discourse Group Voice Chat](https://meta.discourse.org/t/-/279027/4?silent=true), and [Video Conference Call](https://meta.discourse.org/t/-/291600/4?silent=true).\n\n- Falco [helped a developer](https://meta.discourse.org/t/-/411428/8?silent=true) use `rooms.json` to check LiveKit transport status and confirmed `expected_transport` is the intended field for distinguishing LiveKit from mesh rooms, then shared a [PR for granular camera and screen permissions](https://meta.discourse.org/t/-/411477/4?silent=true).\n\n- Nat [diagnosed the upgrade dead-end](https://meta.discourse.org/t/-/411555/2?silent=true) caused by Voice plugin migrations conflicting with leftover Resenha plugin versions, and provided a [SQL rename script](https://meta.discourse.org/t/-/411555/8?silent=true) for affected self-hosters.\n\n- Nat [proposed 9](https://meta.discourse.org/t/-/256772/12?silent=true) to let sites disable anonymous search while preserving search for logged-in users, after Mcwumbly raised the anonymous-search griefing problem.\n\n- Nat [traced blank Ask AI responses](https://meta.discourse.org/t/-/411572/3?silent=true) to a 20-second request deadline being exceeded by a slow LLM response, advising Karthik_K1 to test with a faster provider.\n\n- Martin [opened a draft PR](https://meta.discourse.org/t/-/397217/18?silent=true) for more concise inline subcategory links with hover cards, then [updated the thread](https://meta.discourse.org/t/-/397217/20?silent=true) after Mcwumbly suggested showing the full parent path only in the card.\n\n- Martin [fixed an issue](https://meta.discourse.org/t/-/404728/71?silent=true) in the unified New view topic list after it was announced.\n\n- Martin [confirmed a fix](https://meta.discourse.org/t/-/97376/629?silent=true) for recurring event weekday selection issues, with follow-up investigation planned by Davidb next week.\n\n- Pmusaraj [published the LiveKit integration guide](https://meta.discourse.org/t/-/411585/1?silent=true), explaining how to configure `voice_livekit_room_policy`, webhooks, and recording settings step by step.\n\n- Rishabh [announced the Discourse Admin Assistant](https://meta.discourse.org/t/-/410439/1?silent=true), describing its moderation actions, site setting changes, and hosting plan awareness for hosted admins.\n\nYesterday the forum learned that even GitHub can stumble, but with a little pitchfork wrangling and a fresh set of voice rooms, Discourse is still standing — and now it can talk about it too!","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\nOver the past 24 hours, the community produced 155 posts across 51 new topics, with 136 likes given on returned posts. \nTop users by posts and likes: \n\nFalco — 16 posts, 23 likes\nNicolsdennis — 6 posts, 9 likes\nEd_S — 6 posts, 8 likes\nRishabh — 1 post, 8 likes\nS…","truncated":true,"post_url":"/t/daily-summary-9pm-utc/291850/974","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":2034245,"name":"Ethan ","username":"Ethsim2","avatar_template":"/user_avatar/meta.discourse.org/ethsim2/{size}/522255_2.png","created_at":"2026-09-04T20:48:15.183Z","cooked":"문제없어요 ![\":slightly_smiling_face:\"](\"https://emoji.discourse-cdn.com/twitter/slightly_smiling_face.png?v=15\" "\\":slightly_smiling_face:\\"")
정리하자면, 날짜/시간 삽입 기능이 실제로 작동하지 않는 경우는 아니라고 생각해요. 워크플로가 다른 것이에요.
\n날짜/시간 삽입은 토픽의 첫 번째 게시글에 [calendar] 블록이 있을 때, 날짜가 있는 답변이 해당 토픽의 캘린더에 표시되도록 할 때 사용해요.
반면 이벤트 생성은 실제 Discourse 이벤트([event ...][/event])를 생성해요. 이 토픽에서 논의된 반복 이벤트 종료 날짜는 그 이벤트 반복 시스템에 적용돼요.
따라서 특정 토픽에 국한된 캘린더를 유지하려는 것이 목표라면, 원래 스크린샷에 표시된 워크플로가 적절해요. 다만 이벤트와 동일한 제한적 반복 기능을 사용하지는 않아요.
","post_number":9,"post_type":1,"posts_count":15,"updated_at":"2026-09-04T20:48:15.183Z","reply_count":0,"reply_to_post_number":8,"quote_count":0,"incoming_link_count":0,"reads":12,"readers_count":11,"score":2.4,"yours":false,"topic_id":368527,"topic_slug":"new-calendar-feature-end-date-for-recurring-events","topic_title":"📅 새 캘린더 기능: 반복 이벤트 종료 날짜","topic_html_title":":date: 새 캘린더 기능: 반복 이벤트 종료 날짜","category_id":67,"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,"reply_to_user":{"id":202262,"username":"MiniForum","name":null,"avatar_template":"https://avatars.discourse-cdn.com/v4/letter/m/0ea827/{size}.png"},"bookmarked":false,"raw":"No problem 🙂\n\nJust to clarify, I don't think this is really a case of the feature not working for **Insert date / time** - it is a different workflow.\n\n`Insert date / time` is used when you have a `[calendar]` block in the opening post of a topic and want dated replies to appear on that particular topic's calendar.\n\n**Create event**, on the other hand, creates an actual Discourse Event (`[event ...][/event]`). The recurring-event end date discussed in this topic applies to that Event recurrence system.\n\nSo if your aim is to maintain a calendar local to one topic, the workflow shown in your original screenshot is the appropriate one; it just doesn't use the same bounded-recurrence feature as Events.","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":"문제없어요 :slightly_smiling_face: \n정리하자면, 날짜/시간 삽입 기능이 실제로 작동하지 않는 경우는 아니라고 생각해요. 워크플로가 다른 것이에요. \n날짜/시간 삽입은 토픽의 첫 번째 게시글에 [calendar] 블록이 있을 때, 날짜가 있는 답변이 해당 토픽의 캘린더에 표시되도록 할 때 사용해요. \n반면 이벤트 생성은 실제 Discourse 이벤트([event ...][/event])를 생성해요. 이 토픽에서 논의된 반복 이벤트 종료 날짜는 그 이벤트 반복 시스템에 적용돼요. \n따라서 특정 토픽에 국한된 캘린더를…","truncated":true,"post_url":"/t/new-calendar-feature-end-date-for-recurring-events/368527/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":2034237,"name":null,"username":"MiniForum","avatar_template":"https://avatars.discourse-cdn.com/v4/letter/m/0ea827/{size}.png","created_at":"2026-09-04T20:41:37.426Z","cooked":"실제로는 특정 주제 안에서 캘린더(이벤트 수집)를 유지하는 것이었습니다.
\n오해가 있었던 점 죄송합니다. 이곳에 처음 온 사람이라서요.
\n사실 이벤트를 생성할 때는 잘 작동하는 것 같습니다.
\n날짜/시간 삽입 기능에서는 작동하지 않는 것이 아쉬울 뿐입니다.
도와주셔서 감사합니다!
","post_number":8,"post_type":1,"posts_count":15,"updated_at":"2026-09-04T20:41:37.426Z","reply_count":1,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":15,"readers_count":14,"score":28.0,"yours":false,"topic_id":368527,"topic_slug":"new-calendar-feature-end-date-for-recurring-events","topic_title":"📅 새 캘린더 기능: 반복 이벤트 종료 날짜","topic_html_title":":date: 새 캘린더 기능: 반복 이벤트 종료 날짜","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":"Indeed it was to maintain a calendar (collecting events) in a topic.\n\nSorry for the misunderstanding, I'm new to this.\n\nIndeed when creating an event, it seems to work.\n\nA pity that it does not work for `Insert date / time`.\n\nThanks for your help !","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":202262,"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날짜/시간 삽입 기능에서는 작동하지 않는 것이 아쉬울 뿐입니다. \n도와주셔서 감사합니다!","truncated":true,"post_url":"/t/new-calendar-feature-end-date-for-recurring-events/368527/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}]}![\"image\"](\"https://global.discourse-cdn.com/meta/original/4X/b/4/c/b4ca8a1648a2d08ee935aa6b1b216bcfc7286f32.png\")
![\"Why_is_a_4k_movie_called_as_HD_…ow__-_Plex_Players_-_Plex_Forum\"](\"https://global.discourse-cdn.com/meta/original/4X/9/0/1/901df2c233717ea9983a6b0eb94c44a56c229279.jpeg\")
![\"Why_is_a_4k_movie_called_as_HD_…ow__-_Plex_Players_-_Plex_Forum\"](\"https://global.discourse-cdn.com/meta/original/4X/e/5/c/e5c57ee88035b69e63b4762c7e165a115ae63703.jpeg\")