# Feature

**URL:** https://meta.discourse.org/c/contribute/feature/2.md?page=225&state=muted

[최신](https://meta.discourse.org/latest.md) · [카테고리](https://meta.discourse.org/categories.md) · [태그](https://meta.discourse.org/tags.md)

**Page:** 226

---

## [Expanded Digests on Google Inbox](https://meta.discourse.org/t/expanded-digests-on-google-inbox/45100)

<div class="topic-metadata">

**Author:** [@Falco](https://meta.discourse.org/u/Falco)\
**댓글:** 2\
**마지막 업데이트:** [6월 2, 2016, 5:24오전 UTC](https://meta.discourse.org/t/expanded-digests-on-google-inbox/45100 "2016-06-02T05:24:12Z")

</div>

When I get a Medium digest e-mail it looks like this: Before opening: After opening: Looks like Google is doing the hardwork for Medium, but I think implementing the Article metadata, without changing Digest loo…

---

## [Restrict tags to specific categories](https://meta.discourse.org/t/restrict-tags-to-specific-categories/44026)

<div class="topic-metadata">

**Author:** [@tomwrench](https://meta.discourse.org/u/tomwrench)\
**댓글:** 16\
**마지막 업데이트:** [6월 1, 2016, 10:24오후 UTC](https://meta.discourse.org/t/restrict-tags-to-specific-categories/44026 "2016-06-01T22:24:40Z")

</div>

Would it be possible to restrict tags to specific categories? This would be applicable where a tag list is only relevant in certain categories. For implementation I’m imagining an ‘allow tags in category’ flag in categ…

---

## [Add "select below" and "select above" admin post selection action](https://meta.discourse.org/t/add-select-below-and-select-above-admin-post-selection-action/14905)

<div class="topic-metadata">

**Author:** [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**댓글:** 3\
**마지막 업데이트:** [6월 1, 2016, 9:56오전 UTC](https://meta.discourse.org/t/add-select-below-and-select-above-admin-post-selection-action/14905 "2016-06-01T09:56:45Z")

</div>

It happens a lot that when splitting topics, you more-or-less need to select all posts downstream of a certain post to get a proper split. This is a pain in the ass in the current admin interface: you have to manually…

---

## [The "useless" feature, "Who's Online" simplified?](https://meta.discourse.org/t/the-useless-feature-whos-online-simplified/45074)

<div class="topic-metadata">

**Author:** [@Druid42](https://meta.discourse.org/u/Druid42)\
**댓글:** 2\
**마지막 업데이트:** [6월 1, 2016, 9:40오전 UTC](https://meta.discourse.org/t/the-useless-feature-whos-online-simplified/45074 "2016-06-01T09:40:07Z")

</div>

My members are talking, on a forum that’s been up and running for over a year, HERE, and they really want a green dot to show who is online. I’ve scoured the Meta, and yeah, I get it. It’s a plugin. But I say, no gree…

---

## [Migrate a topic to GitHub](https://meta.discourse.org/t/migrate-a-topic-to-github/45058)

<div class="topic-metadata">

**Author:** [@mholt](https://meta.discourse.org/u/mholt)\
**댓글:** 5\
**마지막 업데이트:** [5월 31, 2016, 11:23오후 UTC](https://meta.discourse.org/t/migrate-a-topic-to-github/45058 "2016-05-31T23:23:45Z")

</div>

Is there a plugin to migrate a topic to GitHub as an issue? That could be really useful for technical forums that want to move specific development-related topics to a GitHub issue. I’m not really sure how exactly it wo…

---

## [Need to see more user data on topic/post approvals](https://meta.discourse.org/t/need-to-see-more-user-data-on-topic-post-approvals/44961)

<div class="topic-metadata">

**Author:** [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)\
**댓글:** 1\
**마지막 업데이트:** [5월 31, 2016, 1:29오후 UTC](https://meta.discourse.org/t/need-to-see-more-user-data-on-topic-post-approvals/44961 "2016-05-31T13:29:14Z")

</div>

When I’m going to reject a pending post, I’m almost always going to redirect it to a support ticket. This is all I see: I need a better way to copy/edit the subject line I need a better way to see the email address,…

---

## [More granular mailing list mode](https://meta.discourse.org/t/more-granular-mailing-list-mode/38107)

<div class="topic-metadata">

**Author:** [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)\
**댓글:** 14\
**마지막 업데이트:** [5월 31, 2016, 11:15오전 UTC](https://meta.discourse.org/t/more-granular-mailing-list-mode/38107 "2016-05-31T11:15:28Z")

</div>

I’m making this proposal in response to the following topics: I think the vast majority of the problems & shortcomings discussed in the topics above would be solved by slightly more granular options for the “maili…

---

## [S3 uploads and Cache-Control](https://meta.discourse.org/t/s3-uploads-and-cache-control/25318)

<div class="topic-metadata">

**Author:** [@masda70](https://meta.discourse.org/u/masda70)\
**댓글:** 1\
**마지막 업데이트:** [5월 30, 2016, 8:49오전 UTC](https://meta.discourse.org/t/s3-uploads-and-cache-control/25318 "2016-05-30T08:49:08Z")

</div>

I’m aware that S3 setups for upload are not really recommended anymore vs origin pull CDNs, but I have a fairly old installation and I’ve been worried at how Discourse handles Cache control rules for S3 uploads. So far …

---

## [Display a link to an approved post or topic?](https://meta.discourse.org/t/display-a-link-to-an-approved-post-or-topic/44962)

<div class="topic-metadata">

**Author:** [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)\
**댓글:** 0\
**마지막 업데이트:** [5월 29, 2016, 12:24오전 UTC](https://meta.discourse.org/t/display-a-link-to-an-approved-post-or-topic/44962 "2016-05-29T00:24:41Z")

</div>

After approving a post and/or topic, if a ghost of the post would remain, so I can click on it to visit/follow up, that’d be wonderful. It’s also be a great place to allow for the Undo which was suggested:

---

## [Accidental double tap on post approval deleted the post](https://meta.discourse.org/t/accidental-double-tap-on-post-approval-deleted-the-post/28733)

<div class="topic-metadata">

**Author:** [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)\
**댓글:** 8\
**마지막 업데이트:** [5월 28, 2016, 11:59오후 UTC](https://meta.discourse.org/t/accidental-double-tap-on-post-approval-deleted-the-post/28733 "2016-05-28T23:59:24Z")

</div>

I have enabled post moderation in our forum, I think I like it a lot. However, I just went to edit a post’s topic, realized I couldn’t, and hit Cancel. I think I double tapped accidentally, and the Cancel button was ri…

---

## [Separate email prefs for "watched" vs "tracked"](https://meta.discourse.org/t/separate-email-prefs-for-watched-vs-tracked/44921)

<div class="topic-metadata">

**Author:** [@rhyolight](https://meta.discourse.org/u/rhyolight)\
**댓글:** 4\
**마지막 업데이트:** [5월 27, 2016, 10:05오후 UTC](https://meta.discourse.org/t/separate-email-prefs-for-watched-vs-tracked/44921 "2016-05-27T22:05:37Z")

</div>

Continued from Why am I getting emails on new replies to watched topics?… Ideally, my users would want different email preferences for Watched vs Tracked categories. For instance, some of us are using Discourse as a mai…

---

## [Why am I getting emails on new replies to watched topics?](https://meta.discourse.org/t/why-am-i-getting-emails-on-new-replies-to-watched-topics/44918)

<div class="topic-metadata">

**Author:** [@rhyolight](https://meta.discourse.org/u/rhyolight)\
**댓글:** 4\
**마지막 업데이트:** [5월 27, 2016, 9:18오후 UTC](https://meta.discourse.org/t/why-am-i-getting-emails-on-new-replies-to-watched-topics/44918 "2016-05-27T21:18:25Z")

</div>

My email settings look like this: I’d assume I would not get any emails unless someone PMed me, but I’m still getting emails for new topic creation and replies. Is it because I’m “watching” topics? I didn’t think wa…

---

## [Hide staff tags from non-staff users](https://meta.discourse.org/t/hide-staff-tags-from-non-staff-users/44025)

<div class="topic-metadata">

**Author:** [@tomwrench](https://meta.discourse.org/u/tomwrench)\
**댓글:** 3\
**마지막 업데이트:** [5월 27, 2016, 6:23오후 UTC](https://meta.discourse.org/t/hide-staff-tags-from-non-staff-users/44025 "2016-05-27T18:23:43Z")

</div>

When logged in as a non-staff user, I can still see a staff-only tag in the dropdown when creating a topic. Is this able to be hidden, so only staff members can see the staff tag in the dropdown? Thanks

---

## [Feature Request: Tall and Thin Image Handling](https://meta.discourse.org/t/feature-request-tall-and-thin-image-handling/43573)

<div class="topic-metadata">

**Author:** [@fearlessfrog](https://meta.discourse.org/u/fearlessfrog)\
**댓글:** 12\
**마지막 업데이트:** [5월 26, 2016, 10:43오전 UTC](https://meta.discourse.org/t/feature-request-tall-and-thin-image-handling/43573 "2016-05-26T10:43:55Z")

</div>

I think this is a feature request. We have users putting images in posts, and sometimes those images are quite tall, i.e. height much greater than the width. Discourse provides an image preview in the post, but uses the …

---

## [Custom settings for the "Staff Actions" logs](https://meta.discourse.org/t/custom-settings-for-the-staff-actions-logs/44790)

<div class="topic-metadata">

**Author:** [@FelixA](https://meta.discourse.org/u/FelixA)\
**댓글:** 1\
**마지막 업데이트:** [5월 25, 2016, 3:33오후 UTC](https://meta.discourse.org/t/custom-settings-for-the-staff-actions-logs/44790 "2016-05-25T15:33:14Z")

</div>

Hi there, am I right that there is no way to adapt the “staff actions” logs? If not, it would be great if this would be customizable. E.g. I would love to have the function that I can see who pushed topics to another …

---

## [Show navbar "unread, recent .." on a topic](https://meta.discourse.org/t/show-navbar-unread-recent-on-a-topic/44780)

<div class="topic-metadata">

**Author:** [@Chopper](https://meta.discourse.org/u/Chopper)\
**댓글:** 1\
**마지막 업데이트:** [5월 25, 2016, 12:22오후 UTC](https://meta.discourse.org/t/show-navbar-unread-recent-on-a-topic/44780 "2016-05-25T12:22:53Z")

</div>

Why the navbar “unread, recent” is not present on a topic post ? On a post this navabar does not exist, when want to see other unread posts or recent posts of a category we need to go back home by clicking on the logo…

---

## [Visualised traffic statistics](https://meta.discourse.org/t/visualised-traffic-statistics/44298)

<div class="topic-metadata">

**Author:** [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)\
**댓글:** 10\
**마지막 업데이트:** [5월 24, 2016, 11:53오전 UTC](https://meta.discourse.org/t/visualised-traffic-statistics/44298 "2016-05-24T11:53:37Z")

</div>

We now have fancy visual graphs to help community managers better track activity trends in their Discourse forum. This feature was quietly released by @sam some weeks ago; now we’d like some feedback. You can see the gr…

---

## [Arxiv onebox plugin](https://meta.discourse.org/t/arxiv-onebox-plugin/44312)

<div class="topic-metadata">

**Author:** [@rhyolight](https://meta.discourse.org/u/rhyolight)\
**댓글:** 14\
**마지막 업데이트:** [5월 23, 2016, 7:36오후 UTC](https://meta.discourse.org/t/arxiv-onebox-plugin/44312 "2016-05-23T19:36:39Z")

</div>

Anyone know if there is a plugin for Arxiv links? Our community references a lot of scientific papers from this website. Here’s an example link: The important data for the onebox would be the title, author, submission…

---

## [Ability to change tracking level from topic summary](https://meta.discourse.org/t/ability-to-change-tracking-level-from-topic-summary/28512)

<div class="topic-metadata">

**Author:** [@anon25879736](https://meta.discourse.org/u/anon25879736)\
**댓글:** 13\
**마지막 업데이트:** [5월 23, 2016, 10:43오전 UTC](https://meta.discourse.org/t/ability-to-change-tracking-level-from-topic-summary/28512 "2016-05-23T10:43:07Z")

</div>

As some of our users have pointed out, it is frustrating to only be able to change the topic tracking at the bottom of a topic. The problem scenario was outlined as follows: Set auto track rules to something like 4 min…

---

## [Link’s href is cut off after 500 characters](https://meta.discourse.org/t/link-s-href-is-cut-off-after-500-characters/44658)

<div class="topic-metadata">

**Author:** [@jesus2099](https://meta.discourse.org/u/jesus2099)\
**댓글:** 7\
**마지막 업데이트:** [5월 23, 2016, 8:06오전 UTC](https://meta.discourse.org/t/link-s-href-is-cut-off-after-500-characters/44658 "2016-05-23T08:06:48Z")

</div>

I have a big 1400 character long link here. If I inspect the document, it’s saved OK in Discourse. If I right click copy HREF then open new tab paste it and Enter it works OK too. But if I click it, the HREF URL will …

---

## [Allow Slack to unfurl/expand links to "login-required" Discourse instance](https://meta.discourse.org/t/allow-slack-to-unfurl-expand-links-to-login-required-discourse-instance/39547)

<div class="topic-metadata">

**Author:** [@mcwumbly](https://meta.discourse.org/u/mcwumbly)\
**댓글:** 5\
**마지막 업데이트:** [5월 22, 2016, 8:34오후 UTC](https://meta.discourse.org/t/allow-slack-to-unfurl-expand-links-to-login-required-discourse-instance/39547 "2016-05-22T20:34:10Z")

</div>

I reached out to the Slack folks with this request and got the following reply. My request: We have private Slack and Discourse instances and I’m looking for ways to better integrate the two. We also use Google Apps e…

---

## [Feature: Like via email](https://meta.discourse.org/t/feature-like-via-email/37052)

<div class="topic-metadata">

**Author:** [@gdpelican](https://meta.discourse.org/u/gdpelican)\
**댓글:** 27\
**마지막 업데이트:** [5월 22, 2016, 7:26오후 UTC](https://meta.discourse.org/t/feature-like-via-email/37052 "2016-05-22T19:26:58Z")

</div>

As part of the MOSS email features outlined here, a RFC for like via email. Current behaviour: No way to like a post via email Proposed behaviour: Clicking on a ‘:heart: this post via email’ link in the email will like…

---

## [No Highlighting of Group mentions in Markdown Preview](https://meta.discourse.org/t/no-highlighting-of-group-mentions-in-markdown-preview/41184)

<div class="topic-metadata">

**Author:** [@rriemann](https://meta.discourse.org/u/rriemann)\
**댓글:** 12\
**마지막 업데이트:** [5월 22, 2016, 1:16오후 UTC](https://meta.discourse.org/t/no-highlighting-of-group-mentions-in-markdown-preview/41184 "2016-05-22T13:16:43Z")

</div>

I just noticed that while usernames have a different style applied in the markdown preview (bold, gray), this is not the case for group mentions. Is this intentional? I consider this as incoherent and suggest to apply ei…

---

## [Tagging support is now part of Discourse](https://meta.discourse.org/t/tagging-support-is-now-part-of-discourse/43334)

<div class="topic-metadata">

**Author:** [@neil](https://meta.discourse.org/u/neil)\
**댓글:** 15\
**마지막 업데이트:** [5월 12, 2016, 2:10오전 UTC](https://meta.discourse.org/t/tagging-support-is-now-part-of-discourse/43334 "2016-05-12T02:10:08Z")

</div>

The discourse-tagging plugin had a good run, but the time has come to make it a core part of Discourse. @eviltrout and I spent the last few days pulling that plugin into core and merged it today. If you’re using the disc…

---

## [Experience from slow hotel connection](https://meta.discourse.org/t/experience-from-slow-hotel-connection/44421)

<div class="topic-metadata">

**Author:** [@charleswalter](https://meta.discourse.org/u/charleswalter)\
**댓글:** 6\
**마지막 업데이트:** [5월 20, 2016, 10:24오전 UTC](https://meta.discourse.org/t/experience-from-slow-hotel-connection/44421 "2016-05-20T10:24:50Z")

</div>

I’m at a hotel in Costa Rica and many other guests must be using the wifi right now, because the Internet is awfully slow. I thought it was interesting to see how Discourse behaved on a few instances. First, when tappin…

---

## [Uploading multiple files via drag and drop puts them all on one line](https://meta.discourse.org/t/uploading-multiple-files-via-drag-and-drop-puts-them-all-on-one-line/28099)

<div class="topic-metadata">

**Author:** [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)\
**댓글:** 2\
**마지막 업데이트:** [5월 20, 2016, 9:36오전 UTC](https://meta.discourse.org/t/uploading-multiple-files-via-drag-and-drop-puts-them-all-on-one-line/28099 "2016-05-20T09:36:27Z")

</div>

When I drag a bunch of files at once to upload them, I then have to go back and put in line breaks manually so they do not wrap. This is a bit tricky because it’s all HTML code. (aside: is there not a way to make these …

---

## [Reset all login tokens](https://meta.discourse.org/t/reset-all-login-tokens/14590)

<div class="topic-metadata">

**Author:** [@riking](https://meta.discourse.org/u/riking)\
**댓글:** 7\
**마지막 업데이트:** [5월 20, 2016, 4:59오전 UTC](https://meta.discourse.org/t/reset-all-login-tokens/14590 "2016-05-20T04:59:49Z")

</div>

With the recent Heartbleed vulnerability, I think it would be a good forward-looking feature to be able to reset/clear all user login tokens, and maybe some other breach recovery-oriented operations. There doesn’t need …

---

## [Add images to custom user fields?](https://meta.discourse.org/t/add-images-to-custom-user-fields/26942)

<div class="topic-metadata">

**Author:** [@Pirat](https://meta.discourse.org/u/Pirat)\
**댓글:** 2\
**마지막 업데이트:** [5월 18, 2016, 2:56오후 UTC](https://meta.discourse.org/t/add-images-to-custom-user-fields/26942 "2016-05-18T14:56:40Z")

</div>

I think it would be cool if it could be to add a picture instead of text /admin/customize/user\_fields how you like the idea?

---

## [Additional formatting options within posts](https://meta.discourse.org/t/additional-formatting-options-within-posts/44423)

<div class="topic-metadata">

**Author:** [@Karthik](https://meta.discourse.org/u/Karthik)\
**댓글:** 0\
**마지막 업데이트:** [5월 18, 2016, 5:03오전 UTC](https://meta.discourse.org/t/additional-formatting-options-within-posts/44423 "2016-05-18T05:03:44Z")

</div>

Hey Guys, Is there any plan to make available additional formatting options/visual editor in posts? Anything like WordPress/Medium will be awesome. For example, text alignment, quotes, H1, H2 tags etc. Use the Classic…

---

## [Multiple image upload on mobile](https://meta.discourse.org/t/multiple-image-upload-on-mobile/44070)

<div class="topic-metadata">

**Author:** [@DeanMarkTaylor](https://meta.discourse.org/u/DeanMarkTaylor)\
**댓글:** 4\
**마지막 업데이트:** [5월 17, 2016, 1:05오후 UTC](https://meta.discourse.org/t/multiple-image-upload-on-mobile/44070 "2016-05-17T13:05:02Z")

</div>

Continuing the discussion from Multiple Image Upload: Uploading images on mobile is far more annoying process compared to desktop… … allowing multiple image uploads on mobile helps with some of that pain. Pull request…

[이전 페이지](https://meta.discourse.org/c/contribute/feature/2.md?page=224&state=muted)

[다음 페이지](https://meta.discourse.org/c/contribute/feature/2.md?page=226&state=muted)
