Just noticed that @ mentions don't parse names when they are a different case from their canonical name, e.g.:
@MindWolf@ is not parsed but Mindwolf is (sorry, Mindwolf but yours was the name that prompted this).
Since I assume usernames are unique despite case, the parsing of the mentions should disregard case, no?
Not sure what @MK@ mk and @Mk@ will do but let's see...
Actually, so do I, so insomniasexx's solution could work out well. However, to throw in a vote for the other side, since I'm writing the message I want as much control over the form as I can have. If I were being hilariously ironic in all caps and demanding you LISTEN TO ME GODDAMIT @CASHEWGUY@, I'M BUYING THE DRINKS!!! I wouldn't want that formatting interrupted by an automatically replaced @ mention.
So, I may regret this, but whatever. The best solution for this is to autocorrect any usernames on submit. So, if I type UsEr_NaMe it 1. finds user in db regardless of case sensitivity. 2. turns UsEr_NaMe into <a href="https://hubski.com/user?id=USER_NAME_FROM_URL">USER_NAME_FROM_URL</a> I know the current process checks if it's a user and if it is, makes it a link to that profile. Because it's making the link, the replacement of the username AND link shouldn't be that bad. But it may be a more intensive db call to search for case-insensative. mk?
Here's another bug: https://hubski.com/ptags?id=history&activity User follow colors don't reflect on personal tag activity pages
Agree. mk, can I suggest a ... monthly (?) thread to air little complaints about obvious stuff like this? I think about them all the time but rarely feel like going to the trouble of taking screenshots or messaging you, also don't want to be a pain. I have a feeling you're going to say: after the back end gets rewritten everything will be very different and it won't matter anyway so let's wait until then. If so, preemptively, I say "sure."
You (or anyone) can also randomly mail / email me stuff if you don't feel like making a post about it. I have a list and we review every week on the calls. insomniasexx at icanhazchat dot com (I should really get a Hubski email. IThat's been on the list for ages now.) Also, anything design wise that you would like redone. I'm literally redoing the entire front end from scratch.
I would really love an easy clean way to paste poetry or song lyrics and preserve the whitespacing.
We will be implementing true, classic markdown with live preview abilities. I will look into a way to provide support for this because I do this it's worthwhile having.
To what extent can you make the step by step of this a community process? I would love to see in-progress on whatever you come up with to give suggestions etc and I bet everyone else would too. There's some really solid design on the site right now, not all of which is scalable probably, and then there are some things that are inconsistent or could be neater. Thanks for being amazing, both of you.Also, anything design wise that you would like redone. I'm literally redoing the entire front end from scratch.
I may make a post sometime this week going over some of the specifics. When I say I'm redoing it, the code is getting redone. The design, for the most part, is remaining intact. For now, there are no plans to change the overall layout / look & feel to be massively different. It's just going to be more consistent, cleaner code, and generally updated.
Lately the one I've been thinking about is the badge menus. If you see a badge symbol on your feed (indicating a badged comment within the thread), the menu you get when you click on it to see the comment, who badged it, etc is kinda clunky. Takes a lot of scrolling to find out who badged the comment, but tells you twice, redundantly, whose comment it was.
Duly noted. I am sure that insomniasexx will rework that. She is leading the design.