• Activity
  • Votes
  • Comments
  • New
  • All activity
  • Showing only topics with the tag "ui". Back to normal view
    1. [SOLVED] "User menu" can you implement a differentiation between "Your posts" and "Your submissions"

      Right now when I click user menu I see this: User menu Profile Your posts Your bookmarks Your votes Your ignored topics I think it would easier to if we could differentiate between posts we made...

      Right now when I click user menu I see this:

      User menu
      Profile
      Your posts
      Your bookmarks
      Your votes
      Your ignored topics

      I think it would easier to if we could differentiate between posts we made on other's submissions and our own submissions. Don't know if this is easy to implement, but for me at least, it would make searching through my stuff here way easier.

      4 votes
    2. Groups don't show unsubscribed topics

      On https://tildes.net/groups it looks like at least on Firefox 88 the normal link color: a.link-user:visited, a.link-group:visited is overriding the unsubscribed color:...

      On https://tildes.net/groups it looks like at least on Firefox 88 the normal link color:

      a.link-user:visited, a.link-group:visited
      

      is overriding the unsubscribed color:

      .group-list-item-not-subscribed a.link-group
      
      4 votes
    3. No feedback when saving filters

      If I add, remove, or change a topic filter, and then press the "Save" button, I get no indication that anything happened. It does work, but it's odd that it doesn't tell you it tried. What if...

      If I add, remove, or change a topic filter, and then press the "Save" button, I get no indication that anything happened. It does work, but it's odd that it doesn't tell you it tried. What if something caused it to fail? (Maybe that case is handled?) I think it should say something like "Changes saved at 3:11:42PM", or something along those lines so you know it actually updated.

      5 votes
    4. Feature request: "confirm comment submission" option

      I constantly hit the "Enter" key in the middle of writing a comment, usually when moving my hand over to my mouse. To avoid this, I'd love it if there were an option in settings to require a...

      I constantly hit the "Enter" key in the middle of writing a comment, usually when moving my hand over to my mouse. To avoid this, I'd love it if there were an option in settings to require a confirmation before any comments are actually submitted. It shouldn't be required, but it would be helpful for me personally.

      5 votes
    5. Blocking or ignoring users

      I've used a myriad of online forums for decades and most, if not all, of them supported blocking or ignoring users. I don't believe that Tildes has this functionality since I can't seem to locate...

      I've used a myriad of online forums for decades and most, if not all, of them supported blocking or ignoring users.

      I don't believe that Tildes has this functionality since I can't seem to locate it.

      If that's the case, then why doesn't Tildes have this feature?

      7 votes
    6. Is there an easy way to make ctrl/cmd-enter work everywhere?

      I don't want to ask this question in "default" groups as peeps that monitor this group will likely know the answer, and I support not making "Tildes a site about discussing Tildes" :) inline-edit:...

      I don't want to ask this question in "default" groups as peeps that monitor this group will likely know the answer, and I support not making "Tildes a site about discussing Tildes" :)
      inline-edit: for context this was originally posted in ~test.

      I am probably one of the most heavily mobile-first users here, but when on desktop, I really want ctrl-enter to work everywhere. Is there some way to make sure all "save" buttons use ctrl/cmd-enter across the entire site? Can this be done via a class or something?

      If not, I can go through the whole site and find places where it does not work.. first example is in the new awesome edit tags ui.

      4 votes
    7. Differentiating between comments collapsed via noise versus user-actioned & old collapses

      Quick thought. Is there currently a purely visual way of distinguishing the rationale for why a comment is collapsed? It seems to me at the moment there's three distinct ways a comment can take on...

      Quick thought. Is there currently a purely visual way of distinguishing the rationale for why a comment is collapsed? It seems to me at the moment there's three distinct ways a comment can take on a collapsed property:

      • The user actively collapsed the comment while scrolling through the topic. This type of collapse is transient, and is neither persisted on the Tildes server, or in the browser, after the users leaves the page.

      • The comment was collapsed via the "negative weighting" heuristic as the community applied noise/joke tags to the comment. This is permanent, until presumably the comment gains enough votes to exceed any negative weighting causing its collapse.

      • Thirdly, the comment can be collapsed because the user has enabled "collapse old comments" in https://tildes.net/settings/comment_visits. Once a user visits a thread, any comments that existed at the last visit to the thread will be collapsed on any subsequent visits to the thread.

      Is there any visual way of distinguishing a user-collapsed comment from a community-collapsed comment currently? And if not, should there be one? Perhaps by making the collapsed text slightly more translucent? I'm actually looking to contribute to the Tildes source code in some small way, so this would potentially be an interesting shoehorn for that.

      26 votes
    8. Content control features (and is there a feature roadmap?)

      I am wondering if it is planned to provide the user with methods to control the content they see, ie; filtering the topics in a group or comments in a topic based on various criteria including...

      I am wondering if it is planned to provide the user with methods to control the content they see, ie; filtering the topics in a group or comments in a topic based on various criteria including keywords.
      I looked around to see if this has been asked, or if there was a roadmap document, but did not find anything. (this is no criticism, I do realize we are early in the dev cycle and I cannot image just one person being able to do all this!)

      I do hope so. No matter how high the quality of the topics/comments there will always be things a user may not want to see.

      5 votes
    9. Make clicking on the indent line collapse comments to that level

      Whilst I am no fan of reddit's redesign, one of the features I liked about it was the way you could click on a indent line to collapse the child comments at that level. Whilst tildes displays...

      Whilst I am no fan of reddit's redesign, one of the features I liked about it was the way you could click on a indent line to collapse the child comments at that level. Whilst tildes displays these indent lines, clicking on them does nothing, and you have to scroll up to get to the collapse button. Another possible solution would be to collapse comments under the cursor when a hotkey is pressed, although this could be awkward due to both mouse and keyboard being used.

      15 votes
    10. Suggestion: Add a show all posts by x button

      As a lurker on the somethingawful forums one of my favorite features is a button which will show all the posts a single person has made in a thread. It'd be really handy if someone (like the OP)...

      As a lurker on the somethingawful forums one of my favorite features is a button which will show all the posts a single person has made in a thread. It'd be really handy if someone (like the OP) is answering questions about a topic. It's really nice to have on a more traditional forum website, but I'm not sure how useful it'd be here. Regardless, I thought I would suggest it.

      Here is an example: Before and After

      9 votes
    11. Usability Suggestion: Mobile sidebar closing.

      Edit: As @Bauke pointed out, apparently this feature already exists via tapping outside of the sidebar. I never even thought to try that. I'm not sure if this is in the gitlab issues or not, but a...

      Edit: As @Bauke pointed out, apparently this feature already exists via tapping outside of the sidebar. I never even thought to try that.


      I'm not sure if this is in the gitlab issues or not, but a cursory search suggested it's not. On mobile, if you tap the link to the most recent comment from the sidebar, you navigate directly to that comment just as on the desktop site, but the sidebar remains open and can't be closed without scrolling all the way back up to the top of the page. This is incredibly cumbersome and inconvenient.

      Ideally there would either be a method of closing the sidebar from anywhere, or for the sidebar to close on clicking the link. I would imagine that the latter would be simplest.

      8 votes
    12. Feature request: A better way to navigate unread comments in a thread

      I've found that the red (X new) indicator next to a thread's comment count on the main page keeps me coming back to the discussion to see the latest messages. This is a good thing, but the UX for...

      I've found that the red (X new) indicator next to a thread's comment count on the main page keeps me coming back to the discussion to see the latest messages. This is a good thing, but the UX for actually navigating through those messages leaves something to be desired.

      There are two relevant existing features I'd like to discuss:

      • All new comments since I last viewed the thread are highlighted with a conspicuous red stripe.
      • The sidebar on any given discussion page has a link to jump to the most recent comment.

      I use the most recent comment link in threads that I know only have one new comment. The link takes me right to it. But in threads with more than one new comment, it's a lot less foolproof. My only method for seeing them all is to scroll down the page and stop when I see a flash of that red stripe. This is tedious in busy discussions which both update frequently with new comments to read, and take a long time to scroll through every time I check them. It's also easy to miss something this way, and since comments are considered "read" after you load the page, there's no second chance to see whatever I missed.

      I'd like to propose a method for iterating through all unread comments on a page, either in chronological order (oldest first) or in order of appearance on the page. Or if @Deimos wants to get really fancy, some kind of hybrid sort that keeps nested comment chains grouped together for contextual continuity when navigating.

      This would require two controls: "Jump to next unread comment" and "Jump to previous unread comment." These could be "sticky" clickable icons on the page, or just some sort of keystroke (like , and . for previous and next, respectively) without a UI at all.

      An important secondary feature of this would be a count indicating both how many unread comments are on the page and how many within that set you have jumped to with this mechanism so far:

      Viewing 2 of 7 unread comments

      This could remain visible or only appear briefly when jumping to the next/previous unread, then fade away. It could also be shortened to something more minimal:

      2/7

      That on-screen feedback would help prevent getting lost in busy threads with high unread counts, particular if the sequence is not determined by order of comment appearance on the page.

      Edit: Whoops, fixed my formatting error I didn't notice after posting.

      12 votes
    13. Sidebars for FAQs, subtopic rules, or Wiki-esque reference links?

      I'm probably about to be guilty of causing the problem I'd like to solve, namely the endless iterations of questions asked and previously answered, or seemingly innocent questions that are...

      I'm probably about to be guilty of causing the problem I'd like to solve, namely the endless iterations of questions asked and previously answered, or seemingly innocent questions that are tantamount to trolling.

      I'm sure there have been prior discussions about pinning items, and I've seen prior commentary about further refining the ground rules for some sub-group areas.

      For the sake of efficiency and comity, there are communities where it would be helpful to create a common body of rules, reference material or other semi-permanent posts which should be regarded as the minimum governance/factual/technical basis for having a productive discussion.

      From a UI design perspective, Reddit, xda-developers, and some other forums have created visually confusing, dis-unified means of handling this - there are multipage FAQ/Wiki top links plus sidebars plus top pins. There's considerable independence among Reddit forums as to which model is chosen, furthering the confusion. I'd like to see Tildes "keep it simple", so pinned topics may be the way to maintain consistency and uniformity.

      Seeking thoughts and discussion about whether this is needed, feasible, desirable, etc.

      [What prompted this query was a a random response on this topic which posited a strawman argument so disingenuous that I wanted to run off and pull a Wiki together just so I could say, "do this minimal amount of homework and come back later, or get reported for being an obvious troll".]

      Note: edited to remove confusion of groups, sub-groups and topics, since I hadn't had enough coffee yet. Sadly I can't do this for the topic title...

      11 votes
    14. Using icons vs using words

      I noticed that Tildes docs make a point out of using words instead of labels. The stated reason is that icons may be difficult to understand, and I honestly don't get how is this the case. Icons,...

      I noticed that Tildes docs make a point out of using words instead of labels. The stated reason is that icons may be difficult to understand, and I honestly don't get how is this the case.

      Icons, when used right, are much more usable and intuitive than any text labels. They are small, distinct, they draw attention and you can tell what they do just by looking at them instead of reading them.

      Take the classic upvote/downvote scrollers used on Reddit, Imgur, etc. It uses icons for upvotes and downvotes, but there isn't a single person I know who doesn't know what those mean. It's intuitive and usable. It doesn't require localization. It just works.

      In contrast, the "Vote (10)" button on Tildes. It uses text, on a page full of text. It's an important UI element, one of the most used UI elements really, but it's not visually highlighted in any way. The amount of votes, which is an important metric, isn't distinct, making it hard to read. The "text button" style it uses is usually reserved for buttons that are used rarely, such as "Edit" or "Delete", or buttons that open more menus, such as "Edit" or "Reply". It's not intuitive.

      Yes, this is a minor thing, but it's minor things that make the overall experience pleasant or unpleasant. And it shows how icons (and highlights), when used right, make user experience better.

      13 votes
    15. Discussion: The merits of removing the ability to vote from the "main" page

      So I was thinking the other day -- is there any good reason to allow voting from the main ~'s page? For clarity in this discussion, I'm talking about this view. Some pro's and con's for removing...

      So I was thinking the other day -- is there any good reason to allow voting from the main ~'s page? For clarity in this discussion, I'm talking about this view.

      Some pro's and con's for removing the vote button from the main page:

      Pro:

      • Discourages "drive-by" voting. We all (mostly?) know that reddit in particular is notorious for having highly up-voted posts that most users read the headline / top-comment and not the article itself. This is particularly noxious for political posts, as often times a vote on a post is an extension of one's own biases / beliefs, rather than an engagement on the topic at hand. This hasn't reared it's head to the same extent on ~'s yet (this post with 15 votes / and only 1 comment would seem to be the closest I can find), but I think it would be a mistake to think that this sort of behavior wouldn't migrate over from reddit. Other reasons for voting on a post without at least getting into the comments are equally bad e.g.: "Oh, I like that band / song / movie / whatever" -- this is a key driver of recycled content on /r/music or movies or tv etc. This reason alone is enough for me to consider removing front-page voting a net-positive

      • The user is forced to enter the comments to vote, wherein they may actually read something that sparks their desire to read the thing / interact with the post. The goal on ~'s is to promote substantive discussion, and I think this would be an interesting tool to try to direct users to said discussion.

      Cons

      • It's more inconvenient, but hey -- so is putting the comment box at the bottom of the page (and I think that's a good idea on net as well)

      • UI inconsistency -- this is a bad thing, but we've got a lot of smart computer people on here. We can probably figure out some way to make this work.

      • It doesn't actually force the user to read / listen / interact with the submission, just suggests that they do. But hey, let's not let the perfect be the enemy of the good, eh?

      Hanging Questions

      • What about voting on ~group pages? My off-the-cuff idea would be that voting on ~music.world.calypso would be a good thing (to promote organic growth of quality posts from small ~groups), but not voting on overarching groups (~music) -- but then the UI issue rears' it's ugly head

      • What about comment / submission voting from other places e.g.: user-pages, notifications, inbox replies, etc.

      19 votes
    16. Thoughts on collapsible code snippets?

      One thing I ended up realizing is that for e.g. code challenges in ~comp, there could be threads with a lot of code blocks that could easily take up a ton of screen real-estate. Something like the...

      One thing I ended up realizing is that for e.g. code challenges in ~comp, there could be threads with a lot of code blocks that could easily take up a ton of screen real-estate. Something like the following isn't so bad:

      /*
          This is a short multi-line example that doesn't
          take up much screen real-estate at all.
      */
      

      But, what if the average comment for a particular topic has several of these with 100 lines or more? This could make navigating the comments really cumbersome as the number of comments grows. In the case of code challenges, lengthy code snippets could be very common, and collapsing the comment threads may not be the desirable course of action--in collapsing the thread for navigational convenience, you lose the ability to view and contribute to discussions. Hosting the code elsewhere risks links expiring or becoming lost or broken, and it feels like a clunky workaround to try to avoid inconveniencing other users.

      With that in mind, what are your thoughts on having these code blocks display in a collapsed state by default with only a preview of the code block showing? Is there any support for this idea? If so, should this be implemented as part of Tildes itself or as a client-side extension of some sort? Are there any concerns about this?

      (If there's general support for the idea, but opposition toward adding it to the Tildes code base, I may get off my lazy ass and try to hack something together.)

      13 votes
    17. Click a message to mark it read?

      While I also appreciate the ability to read things without marking them as read, it took me a minute to figure out how to mark things as read and now I find it more of a burden than anything....

      While I also appreciate the ability to read things without marking them as read, it took me a minute to figure out how to mark things as read and now I find it more of a burden than anything. Would it be possible to implement functionality to mark things as read if you click on the message in your inbox?

      Sometimes I even reply out of my inbox and it keeps it unread. While I sometimes keep emails I've replied to as unread at work, I can't see any reason I'd want to do that on a social media website. Maybe that's another functionality that could be implemented?

      7 votes
    18. Anyone else confusing quotes and OP comments when scrolling through a thread

      I'm glad we got that extra highlight for OP comments on a post. However, sometimes when scrolling down a post, and looking for OP's comments, I will stop thinking I've found one when actually it's...

      I'm glad we got that extra highlight for OP comments on a post. However, sometimes when scrolling down a post, and looking for OP's comments, I will stop thinking I've found one when actually it's just a quote inside someone else's comment, which is highlighted with the same color.

      Maybe we could get rid of the quote highlight and just use the indentation and lighter background? Or use another color for either of the two? Or do you think it's fine like it is now?

      NOTE: I always browse of mobile and use the solarized dark theme, not sure if this is the same with other settings.

      10 votes
    19. Move the "votes" string on your own posts?

      Just a minor UI thing - other people's vote count/vote button is on the bottom of their posts, while yours is on top. Just a bit jarring going from one to the other, is there any reason your...

      Just a minor UI thing - other people's vote count/vote button is on the bottom of their posts, while yours is on top. Just a bit jarring going from one to the other, is there any reason your post's vote count can't be in the same place?

      3 votes
    20. Small UI Improvement: Increase Gap Between Collapse Comment & Username

      I'm really enjoying the mobile interface, if there is one improvement I would like to see be made is the ability to quickly swipe through on a touch interface and collapse comment threads that I...

      I'm really enjoying the mobile interface, if there is one improvement I would like to see be made is the ability to quickly swipe through on a touch interface and collapse comment threads that I want to skip. I'm using a larger phone, and have pretty big fingers, so I'm constantly hitting the username and accidentally begin reading their post history. Maybe I just have poor hand eye coordination, but the collapse button is small and really close to the edge of the screen.

      This could easily be remedied in a couple ways, by either adding a couple more spaces between the button and username, or by making the button rectangular instead of square.

      9 votes
    21. Universal Settings

      I think having the theme settings be universal as long as you are logged into your account would be nice. For example, if I log in on my browser I have Dark Theme set. However, if I log in on my...

      I think having the theme settings be universal as long as you are logged into your account would be nice. For example, if I log in on my browser I have Dark Theme set. However, if I log in on my phone it defaults to light theme.

      I assume as more settings are added (e.g - turn off custom group stylesheets if those are added) it woud be nice to not have to go reconfigure settings on various devices.

      6 votes
    22. Adding a collapse button at the bottom

      I've been using ~ on mobile to try it out, and although it's great, there's one major inconvenience. If I'm reading through a long comment, I want to instintively collapse it so it won't distract...

      I've been using ~ on mobile to try it out, and although it's great, there's one major inconvenience.

      If I'm reading through a long comment, I want to instintively collapse it so it won't distract me. But on mobile, I have to scroll a long way up to do that. It's even worse with comment chains.

      Can we have a collapse button at the bottom as well? Or a swipe, like on the Reddit app? Or do we have to wait for the development of the app before mobile users get good UI?

      11 votes
    23. Put a small vote button on the left

      This one is super first world, but it would make the transition from Reddit much easier. The vote button is on the far right of the screen even though the rest of the UI and most people naturally...

      This one is super first world, but it would make the transition from Reddit much easier. The vote button is on the far right of the screen even though the rest of the UI and most people naturally gravitate to the left. I am fine with them keeping the old vote button, but they should put a small one on the left side also.

      8 votes
    24. Tildes UI design

      Hey everyone, I've seen a bunch of posts discussing the design of the site, and I was wondering if there are any other designers on here that would be interested in discussing the interface more...

      Hey everyone,
      I've seen a bunch of posts discussing the design of the site, and I was wondering if there are any other designers on here that would be interested in discussing the interface more precisely, and coming up with potential improvements. I wrote up a design audit and gave it to @Deimos last week, and I wanted to share it with everyone and generate some discussion about minutiae such as colors, placement and styles of buttons and links, etc. I feel like these are just as important as larger features that people are asking for (such as a markdown preview), and have the added benefit of being very fast to iterate on.

      16 votes
    25. UI suggestions

      Some suggestions I think would improve navigation a bit: 1.Comment votes. I think comment votes should appear at the bottom of the comment. The reason for that is is to avoid "copycat voting" (I'm...

      Some suggestions I think would improve navigation a bit:

      1.Comment votes. I think comment votes should appear at the bottom of the comment. The reason for that is is to avoid "copycat voting" (I'm sure there must be another term). I think it's a common effect: you see a comment, you see it has 5 votes while the rest you've been reading have 1 or 2, you start being predisposed to see it as a valuable comment even before reading it, you end up voting it too, etc. Similarly to why the top level reply box is at the end of the thread, I think having comment votes at the end of the comment (or even hidden under an expandable menu, but maybe that's too much) would help users reading comments more open-mindedly. I would even argue that putting the user name at the bottom would be a good idea as well, especially since the user base now is small is easy to adscribe more credibility to some user names than others, which is not bad by itself, but might push a type of "authoritative bias".

      2.Top level comments count. If we understand top level comments as the main ideas discussed in a thread, maybe it would make sense to show that in the post. Right now, what we get in the submission listing is the title, username, the ~, the tags and the comment number. I wonder how important is having the total comment number shown here. I guess it's an indicator of activity, but maybe it'd be more interesting having the top level comment number, indicating the ramifications of the topic. Total comment count could be maintained as well, or not, or just when entering the submission, etc. New comments could still be shown in the listing. After all, if we are ordering by activity, we care that there is some activity, and total number of comments is not that relevant.

      3.Cascading tags. Not so sure about this one, but I though I'd mention it. When marking a comment Off-topic... I think most usually all comments under that one will also be Off-topic. Maybe it'd make sense that from that point on all comments would be marked as off topic automatically, and possibly collapsed. Right now it seems when there is an off topic comment thread, you just keep seeing off topic tags down the line, which is a bit distracting and probably unnecessary since they are almost surely going to be off topic, so it's probably not necessary for user to try and judge that. Maybe, if it makes sense, this would better be done when the tags are more developed.

      4.Parent link for context. Thank you for adding the parent link! Much needed. However, wouldnt it be better if when tapping a parent link, the end page would be the parent comment (obviously) plus the comment where you tapped the link? What I mean is, to provide better context, I think it'd be better to show the parent and the comment I was reading, with all other comments under the parent AND above the origin comment collapsed. I don't know if that's clear...

      1. Reply - Tag - Vote. Probably a bit nitpicking here, but I think inverting the current order of the Reply and Vote buttons would be a better fit. Since most people are right handed, and the action of voting is (probably?) more common than replying, having the vote button on the right side might be a minor enhancement in usability.

      6.Highlighting OP's comments. Right now, OP's comments are marked by "(OP)" next to the username. I think it'd be better to make the indication more evident. For example, displaying OP's username in a different color or marking the comment with a different color (as with new comments in orange or own comments in purple). I would prefer the username color since it's less invasive while still being easy to spot.

      Anyway, just some ideas I've had in the last few days, hopefully not too ridiculous or confusingly worded.

      EDIT: Sorry for the generic title, I forgot to edit it before sending...

      18 votes
    26. Possible bug: using the ~ character preceding a word within inline preformatted text.

      In preformatted text blocks (three back ticks), group syntax with ~ doesn't get rendered as a hyperlink, but it does with inline preformatted text e.g. ~group. This seems like it would be...

      In preformatted text blocks (three back ticks), group syntax with ~ doesn't get rendered as a hyperlink, but it does with inline preformatted text e.g. ~group.

      This seems like it would be undesirable and unintended behavior. That being said, I'd rather have this verified before opening an issue on gitlab.

      Is this a bug or a feature?

      7 votes