# Forum Operations Feedback Thread **URL:** \ **Category:** Wyze News\ **Tags:** important\ **Created:** [November 6, 2018, 9:29pm UTC](https://forums.wyze.com/t/forum-operations-feedback-thread/6789 "2018-11-06T21:29:24Z")\ **Posts on this page:** 20\ **Page:** 73
**Author:** ![Crease](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/crease/32/123254_2.png) [@Crease](https://forums.wyze.com/u/Crease)\ **Post date:** [August 24, 2025, 6:25pm UTC](https://forums.wyze.com/t/forum-operations-feedback-thread/6789/1545 "2025-08-24T18:25:49Z")
> [@carverofchoice](#): > > That’s useful. 👍 That was another reason I posed the question, kind of as a #Tips & Tricks thing. > [@carverofchoice](#): > > For @me I usually just type my own username to search through. That’s what I used to do, too, but `@me` is way easier, I think, and I don’t have to wait for the search entry field to autocomplete my username. ---
**Author:** ![peepeep](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/peepeep/32/107148_2.png) [@peepeep](https://forums.wyze.com/u/peepeep)\ **Post date:** [August 27, 2025, 5:05pm UTC](https://forums.wyze.com/t/forum-operations-feedback-thread/6789/1546 "2025-08-27T17:05:11Z")
Are you aware of a way to _exclude_ a member from a search? Like NOT @peepeep ? I did look for it, but not exhaustively. 🙂 ---
**Author:** ![Crease](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/crease/32/123254_2.png) [@Crease](https://forums.wyze.com/u/Crease)\ **Post date:** [August 27, 2025, 5:27pm UTC](https://forums.wyze.com/t/forum-operations-feedback-thread/6789/1547 "2025-08-27T17:27:03Z")
I’m not, though I see that it’s been discussed quite a bit in Discourse Meta when I do [a query for `search exclude`](https://meta.discourse.org/search?q=search+exclude). I know that it’s possible to exclude _some_ types of terms, and I see that if I add something like `-user:peepeep`\[1\] to a query here in the Forum it eliminates _some_ results from the search, but I don’t know if that answers your question or provides whatever you’re trying to accomplish. Knowing more about the goal would be helpful. * * * 1. The minus sign (-) provides the “NOT”. ---
**Author:** ![peepeep](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/peepeep/32/107148_2.png) [@peepeep](https://forums.wyze.com/u/peepeep)\ **Post date:** [August 27, 2025, 5:56pm UTC](https://forums.wyze.com/t/forum-operations-feedback-thread/6789/1548 "2025-08-27T17:56:27Z")
Thanks! Let’s say a member said “Reolink” a lot and you wanted to determine how many times they had said it when compared to the total times it had been said. So you’d run an unqualified search for “Reolink”, and then a qualifed one excluding the user:squeezecam, then divide the results of the latter by the results of the former to get the %. 😉 Seriously, that describes what I’m trying to do (but not with @squeezecam and Reolink.) It looks like it’s not supported. ---
**Author:** ![Crease](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/crease/32/123254_2.png) [@Crease](https://forums.wyze.com/u/Crease)\ **Post date:** [August 27, 2025, 6:48pm UTC](https://forums.wyze.com/t/forum-operations-feedback-thread/6789/1549 "2025-08-27T18:48:18Z")
For something like that, I think your best bet would be to directly query the database if you had access to that. Maybe you should be gunning for co-Admin. 😉 Also, I think in your math you’d subtract the results of the latter from the results of the former and then divide _that_ by the results of the former. 🤓 I get what you mean, though, and I appreciate the example choices you selected for the query term and username. 😁 ---
**Author:** ![peepeep](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/peepeep/32/107148_2.png) [@peepeep](https://forums.wyze.com/u/peepeep)\ **Post date:** [August 27, 2025, 8:18pm UTC](https://forums.wyze.com/t/forum-operations-feedback-thread/6789/1550 "2025-08-27T20:18:09Z")
![image](https://us1.discourse-cdn.com/wyze/original/3X/3/b/3b09974524b2227e8edbf1596d7917365468111e.png) Yeah, great co-Admin material. 😆 If I’m gonna kid somebody I should get the process right. ---
**Author:** ![carverofchoice](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/carverofchoice/32/107068_2.png) [@carverofchoice](https://forums.wyze.com/u/carverofchoice)\ **Post date:** [September 20, 2025, 9:20pm UTC](https://forums.wyze.com/t/forum-operations-feedback-thread/6789/1551 "2025-09-20T21:20:49Z")
@Loki do you have any objections to enabling the following badges: > [@On another topic](https://forums.wyze.com/t/30155/1): > > ### Solved Badges > > | Name | Description | Long Description | Type | Grouping | > | --- | --- | --- | --- | --- | > | Solved! | Have a reply marked as a Solution | This badge is granted for having a reply marked as a Solution to a topic. ✅ Nice job. 👍 | 🥉 | Community | > | Guidance Counsellor | Have 10 replies marked as Solutions | This badge is granted for having 10 of your replies marked as Solutions to topics. ✅ You are a true asset to your fellow community members. | 🥈 | Community | > | Know-it-All | Have 50 replies marked as Solutions | This badge is granted for having 50 of your replies marked as Solutions to topics. ✅ You really know your stuff. 👏 | 🥇 | Community | > | Solution Institution | Have 150 replies marked as Solutions | This badge is granted for having 150 of your replies marked as Solutions to topics. ✅ Excellent work. 🙂 You are officially a Solution Institution. 🧠 | 🥇 | Community | > > > ℹ These badges will be disabled by default. You can enable them from your `admin/badges` page I just learned that they exist. I kind of enjoy the gamification aspect in general. Interestingly nobody yet qualifies for the top solutions badge, though @Omgitstony is REALLY close. ![image](https://us1.discourse-cdn.com/wyze/original/3X/8/2/8241456d0e82953633a1df078f247149dca11bb5.png) I don’t know what other badge options there are to enable, but I learned about these ones today and think they would be pretty cool if you don’t have any objections to it. 🙂 ---
**Author:** ![Crease](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/crease/32/123254_2.png) [@Crease](https://forums.wyze.com/u/Crease)\ **Post date:** [September 20, 2025, 9:23pm UTC](https://forums.wyze.com/t/forum-operations-feedback-thread/6789/1552 "2025-09-20T21:23:18Z")
> [@carverofchoice](#): > > I just learned that they exist. ☝ This is my fault. @Loki, I’m so sorry. I’m not trying to add to your to-do list. 🫣 2025-09-20T21:27:45Z Edit: Now I’m 😆 at how quickly this happened: ![@carverofchoice liked this](https://us1.discourse-cdn.com/wyze/original/3X/6/a/6adc23ccd376b9779b37caaceb3a0a34b04c710b.png "@carverofchoice liked this") ---
**Author:** ![carverofchoice](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/carverofchoice/32/107068_2.png) [@carverofchoice](https://forums.wyze.com/u/carverofchoice)\ **Post date:** [September 20, 2025, 9:40pm UTC](https://forums.wyze.com/t/forum-operations-feedback-thread/6789/1553 "2025-09-20T21:40:53Z")
> [@Crease](#): > > Now I’m 😆 at how quickly this happened: > > ![@carverofchoice liked this](https://us1.discourse-cdn.com/wyze/original/3X/6/a/6adc23ccd376b9779b37caaceb3a0a34b04c710b.png "@carverofchoice liked this") I mean…I still get to ask for what I want AND if it goes badly, you already accepted responsibility. Win-Win. 😆 ---
**Author:** ![Crease](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/crease/32/123254_2.png) [@Crease](https://forums.wyze.com/u/Crease)\ **Post date:** [September 25, 2025, 3:00am UTC](https://forums.wyze.com/t/forum-operations-feedback-thread/6789/1554 "2025-09-25T03:00:30Z")
> [@Firmware Update - Released 9/24/2025](https://forums.wyze.com/t/firmware-update-released-9-24-2025/337573/5): > > I will look into doing that, I get into the habit of just putting Firmware Updates because there are many times it is more than one. If you’re considering a habit/process change for topic titles, then I’m going to put in a plug for this again: > [@Forum Operations Feedback Thread](https://forums.wyze.com/t/forum-operations-feedback-thread/6789/1332): > > I haven’t seen an answer to this question in this topic, so I’ll ask it: What could be done to have posts in the #Beta category be tagged better for easier search? @peepeep’s [earlier post might be related](https://forums.wyze.com/t/forum-operations-feedback-thread/6789/1193), but [a discussion in another topic](https://forums.wyze.com/t/way-point-drift-issue-with-a-different-pan-cam-in-same-place/299460) is what prompted this question. When looked at [the list of topics in the Beta category](https://forums.wyze.com/c/beta), one of the things I noticed is that few of the topics seem to be tagged for product. I don’t know if that’s just the practice for people like @WyzeAndy or @WyzeJasonJ wh… Although I mentioned #Beta in that one, I think it could be especially helpful for finding relevant topics in #Wyze News, too. Those are categories I tend to search a lot when trying to help other users and point to resources. ---
**Author:** ![Loki](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/loki/32/1595_2.png) [@Loki](https://forums.wyze.com/u/Loki)\ **Post date:** [October 16, 2025, 4:27pm UTC](https://forums.wyze.com/t/forum-operations-feedback-thread/6789/1555 "2025-10-16T16:27:10Z")
I’m finally catching up on some long awaited backlog. I’ve enabled these four badges. ---
**Author:** ![Loki](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/loki/32/1595_2.png) [@Loki](https://forums.wyze.com/u/Loki)\ **Post date:** [October 16, 2025, 4:34pm UTC](https://forums.wyze.com/t/forum-operations-feedback-thread/6789/1556 "2025-10-16T16:34:08Z")
Again, finally catching up on some stuff. Topic creation in the #Beta category is now restricted to Wyze employees. ---
**Author:** ![Crease](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/crease/32/123254_2.png) [@Crease](https://forums.wyze.com/u/Crease)\ **Post date:** [October 16, 2025, 6:17pm UTC](https://forums.wyze.com/t/forum-operations-feedback-thread/6789/1557 "2025-10-16T18:17:08Z")
![“And there was much rejoicing!” (Monty Python and the Holy Grail (1975))](https://us1.discourse-cdn.com/wyze/original/3X/1/c/1c239f28d037404ec01ee11fa6747bc6d42e68ef.gif "“And there was much rejoicing!” (Monty Python and the Holy Grail (1975))") Thank you! I hope it helps with the organizational clutter and improves users’ issues visibility. 👍 ---
**Author:** ![peepeep](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/peepeep/32/107148_2.png) [@peepeep](https://forums.wyze.com/u/peepeep)\ **Post date:** [October 23, 2025, 11:53pm UTC](https://forums.wyze.com/t/forum-operations-feedback-thread/6789/1558 "2025-10-23T23:53:55Z")
Why did they reduce the size of the standard emoji face (assuming they did and it’s not just me on my desktop browser) ? Standard emoji face: 🤣 Iso emoji face: 🤣 I feel only one emotion reading them now: 😖 ---
**Author:** ![Seapup](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/seapup/32/118966_2.png) [@Seapup](https://forums.wyze.com/u/Seapup)\ **Post date:** [October 24, 2025, 12:09am UTC](https://forums.wyze.com/t/forum-operations-feedback-thread/6789/1559 "2025-10-24T00:09:04Z")
Ask Loki if he wants to play… User in this context is site admin: > Discourse recently changed the size of emojis, moving from a fixed 20px to being relative to the base font-size (1em), which often results in them appearing smaller. This change was implemented to align with other theme defaults, but has since prompted some users to seek ways to restore the original sizing. > > - **The change:** Before the update, emojis were hardcoded to be 20 pixels in size. After the update, their size is now relative to the site’s base font-size, which is 16px in the default theme. > > - **The effect:** Because 16px is smaller than 20px, emojis now appear smaller for many users. > > - **Customization:** Users who want to adjust the size can do so through custom CSS, with specific rules for different areas of the site. For example, you can add a custom CSS rule to set the height of all emoji images to a specific pixel value. ---
**Author:** ![peepeep](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/peepeep/32/107148_2.png) [@peepeep](https://forums.wyze.com/u/peepeep)\ **Post date:** [October 24, 2025, 12:20am UTC](https://forums.wyze.com/t/forum-operations-feedback-thread/6789/1560 "2025-10-24T00:20:03Z")
Ah. That’s ok. Just remembered I can ctrl/+ a few times and return with ctrl/zero. No hardship. 🙂 ---
**Author:** ![Seapup](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/seapup/32/118966_2.png) [@Seapup](https://forums.wyze.com/u/Seapup)\ **Post date:** [October 24, 2025, 12:21am UTC](https://forums.wyze.com/t/forum-operations-feedback-thread/6789/1561 "2025-10-24T00:21:32Z")
I’d like to see emojis return back to 20px. 👍 ---
**Author:** ![Crease](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/crease/32/123254_2.png) [@Crease](https://forums.wyze.com/u/Crease)\ **Post date:** [October 24, 2025, 12:29am UTC](https://forums.wyze.com/t/forum-operations-feedback-thread/6789/1562 "2025-10-24T00:29:06Z")
Then you have this guy who makes it more complicated by snatching the URL and letting the Markdown (`![{image_name}]({image_URL})`) or HTML (`` tag) render at its default size: ![:zany_face:](https://emoji.discourse-cdn.com/facebook_messenger/zany_face.png ":zany\_face:") ---
**Author:** ![Loki](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/loki/32/1595_2.png) [@Loki](https://forums.wyze.com/u/Loki)\ **Post date:** [November 11, 2025, 3:17pm UTC](https://forums.wyze.com/t/forum-operations-feedback-thread/6789/1563 "2025-11-11T15:17:40Z")
> [@Seapup](#): > > Ask Loki if he wants to play… User in this context is site admin: Sorry, I’m not going to mess with it. ---
**Author:** ![Crease](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/crease/32/123254_2.png) [@Crease](https://forums.wyze.com/u/Crease)\ **Post date:** [November 12, 2025, 6:53pm UTC](https://forums.wyze.com/t/forum-operations-feedback-thread/6789/1564 "2025-11-12T18:53:32Z")
I dig some of these incremental changes, like how checking s now shows _above_ the element: ![checking ♥️s above](https://us1.discourse-cdn.com/wyze/original/3X/f/d/fd53e9b09d2d932315ae2de8199fa8d61d582016.png "checking ♥️s above") [Previous page](https://forums.wyze.com/t/forum-operations-feedback-thread/6789.md?page=72) [Next page](https://forums.wyze.com/t/forum-operations-feedback-thread/6789.md?page=74)