Thanks for the reply @Loki .
It’s not a big concern. I must have been hangry at the time.
Same here.
I’m not suggesting that you do this (nor suggesting that you don’t do this). I’m just curious about how it would work. What I imagine is that a user interested in seeing the Beta category would navigate to the Groups page and Join the Beta members group, then that category would become visible to the user here in the Forum. If the user decided to Leave the group, then the Beta category would be hidden for that user. Is that correct?
Again, I’m not suggesting either way. I’m just trying to understand how it would work and thinking that if such a change was implemented then the main Web site would probably need a note about this on the Become a Beta Tester page, and the How To Become A Beta Tester topic would also need an update and a category change, because the latter is already in the Beta category and would then have its visibility restricted only to people who are already in the Beta group (if I understand how this would work).
I’ll just point back to my original suggestion, because my goal with that was to reduce some organizational clutter and hopefully cause beta testing users to post actual beta bugs to topics created (and hopefully tracked) by Wyze Team members, so just restricting topic creation in Beta (like with Wyze News) is what makes sense to me, and I imagine that would be an easier change to implement.
yes
I’m still okay with your original suggestion and yes it would be more effective. I can implement that if we decide to go that way. Still waiting to hear from @WyzeJasonJ about it.
I’m in no rush on this and don’t have a strong opinion either way. I just occasionally have questions or thoughts about possible improvements and then decide to spew them out of my brain. Thanks for taking the time to read and respond!
I would not have an issue with that suggestion. I think it would make things easier for some of the engineers that do try to watch for beta bugs since they are more likely to look in the threads that were created for a release than those just randomly created.
Does a new account default to a private profile now? There seem to be a rash of new users with private profiles lately.
Or they could be rational, constructive (and friendly!) Discourse user-bots, I guess.
Can’t rule out anything these days. 
Sorry, I don’t know the answer to that, but I don’t think so. There haven’t been any changes to the site settings in that regard.
I think that’s a change to the platform as a whole, and I first noticed it yesterday or the day before, but I’d read about it previously in Discourse Meta. They have an announcement topic over there, and IIRC what I was reading before were other topics when they made it available for testing. I think it automatically selects the new “rich text editor” (that was my experience using Google Chrome on a PC running Windows 11), and I’ve tried it a little, but mostly I’ve switched back to the Markdown editor because I like the controls and previews. It’s cool that it’s easy to toggle between them with a shortcut key, though. I like that they apparently put a lot of thought into usability.
I think it saves the user’s preference across platforms, too. Opening new replies on both Google Chrome and Mozilla Firefox on a Linux installation just now, it’s beginning with the Markdown editor mode that I’ve selected. Nice. 
I’ve also noticed that notifications appear different now. (I use https://forums.wyze.com/u/Crease/notifications?filter=unread as my effective “home” by creating a custom section in the sidebar, but it’s also present on the regular Notifications page.) The list doesn’t seem to be as compact as it was before (this is viewing with both Dark and Wyze Theme), which means I now have to scroll more (not a big deal, but not what I’d prefer). The way the notification count displays over my profile picture in the upper-right corner, I’m not quite sure where that number is coming from now, because it doesn’t seem accurate. It’s undercounting “new” notifications, but I haven’t yet cleared the new stuff today, so maybe the change was made sometime overnight (for me) and that caused the count to reset, so stuff that was “new” before then was cleared and isn’t actually “new” after this reset?
I also noticed in my notifications that I had a personal message. In the past, those seemed to take priority in the profile picture overlay: There would be an envelope icon in place of a numerical count of new notifications, presumably to let the user know that a personal message was waiting, because that might be more important than other notification types. With this most recent personal message, though, there was no such envelope icon on the profile picture, so I’m thinking that might also be part of the “new” reset (which I’m just guessing about). Hopefully that’s not a permanent change in message prioritization, but I imagine I’ll have an opportunity to figure that out within a few days or so.
Agree. It’s a lot of fun to use. 
If you search with a quoted phrase:
@dave27 “too much wifi”
…and then try to make a link of the search results page by copying from the URL field:
you can’t. The search fails when you click the created link.
You have to paste it directly to a post in full and get:
https://forums.wyze.com/search?q=%40dave27%20%22too%20much%20wifi%22%20order%3Alatest
…instead of a compact link, though then if you quote 
to another post you get:
For the second part, are you trying to shorten the link text that’s presented to the user or achieve something else? I wonder if this is a consequence of Discourse’s Onebox feature because the pasted URL is on a line by itself, though I don’t know exactly why this is happening within a quote but not when pasted by itself in original (non-quote) content. I see that it happens even if you’re not doing a Discourse [quote] but instead using a > blockquote. You can always use Markdown or HTML to edit the quote so that it shows the URL string itself and not the Onebox expansion:
Markdown:
[https://forums.wyze.com/search?q=%40dave27%20%22too%20much%20wifi%22%20order%3Alatest](https://forums.wyze.com/search?q=%40dave27%20%22too%20much%20wifi%22%20order%3Alatest)Result:
https://forums.wyze.com/search?q=%40dave27%20%22too%20much%20wifi%22%20order%3Alatest
HTML:<a href="https://forums.wyze.com/search?q=%40dave27%20%22too%20much%20wifi%22%20order%3Alatest">https://forums.wyze.com/search?q=%40dave27%20%22too%20much%20wifi%22%20order%3Alatest</a>Result:
Search results for '@dave27 "too much wifi" order:latest' - Wyze Forum
You could also just edit the quote and surround the URL with angle brackets (<>), which would be much easier:
<https://forums.wyze.com/search?q=%40dave27%20%22too%20much%20wifi%22%20order%3Alatest>…yields…
https://forums.wyze.com/search?q=%40dave27%20"too%20much%20wifi"%20order%3Alatest
…which unadorned with angle brackets is like you noted:
Search results for '@dave27 "too much wifi" order:latest' - Wyze Forum
See Creating rich link previews with Onebox - Using Discourse - Discourse Meta for that last one.
I suspect that this (the coversion of URLs to linked titles) is happening within quotes because when quoted those URLs (as a consequence of being within quotes) are no longer single-line URLs actually starting at the beginning of the line itself, so then they become “inline Oneboxes” and are subject to the default enable inline onebox on all domains setting[1][2], thus Discourse’s Onebox feature converts them within the post’s quote. I think that’s what’s happening, anyway. If you want the full URL (instead of the linked page’s title) to display, then it’s probably best/easiest to just use the angle bracket override and also use the standard composer’s (Markdown editor’s) preview to make sure that line is going to render the way you want before submitting the post. That’s probably what I’d do.
With regard to what you’re seeing in the first part of your post, I believe that’s a browser-dependent display. For instance, Firefox’s address bar shows the spaces as spaces and makes the URL more human-readable:
Chrome’s address bar percent-encodes each space to %20:
I don’t know if that helps or if you were trying to express a question or just making an observation, but hopefully that sheds a little light on what you’re seeing.
2025-08-13T06:34:28Z Edit: I just noticed after submitting another edit to this reply that Discourse is now showing footnotes in a more compact way rather than the big ol’ boxed “⋯” that it used to[3]:
Nice!
Like what’s demonstrated in the image on the Footnotes plugin page. ↩︎
peep one
[peep one](https://forums.wyze.com/search?q=%40peepeep%20good%20order%3Alatest)
peep two
[peep two](https://forums.wyze.com/search?q=%40peepeep%20good%20will%20order%3Alatest)
peep three
[peep three](https://forums.wyze.com/search?q=%40peepeep%20%22good%20will%22%20order%3Alatest)
“peep three” is what I was after
Manually percent-encoding the spaces and quotation marks so it conforms with the sample above will work for me.
Dude. Thanks so much for laying your crazy brain all over this. 
My crazy brain becomes kinked trying to keep it all straight so I look for a frog-simple solution.
And the footnotes, yeah, that’s cool…
Oof. Now I’m seeing my HTML sample above rendering the page title instead of the URL (I thought it was showing the URL before), so I don’t know what’s up with that.
You’re welcome. I think “crazy brain” might be the operative phrase here. 
Who else here searches @me when trying to find specific Forum content to link or quote? Since reading about that a while back in Discourse Meta, I’ve started to use that and other aliases, like t, to make my searches more efficient, and adding @me to a search query helps me to find something I’ve already written so that I don’t have to type the whole thing again.
. Often.
Thanks for that other aliases link.
I wondered if you were aware of that one, especially since you link to your own posts so often. I think it’s helpful for connecting thoughts.
I wasn’t aware of all the alias and order options. That’s useful.
For @me I usually just type my own username to search through. I like the option to only search the first post. I didn’t know admit that filter option 