• Activity
  • Votes
  • Comments
  • New
  • All activity
  • Showing only topics in ~tildes with the tag "extensions". Back to normal view / Search all groups
    1. Stylus userstyle that hides comment vote counts

      This simple stylus userstyle hides vote counts on both voted and unvoted comments and your own comments. I really like what Deimos did, it significantly improved my time here on Tildes. If you...

      This simple stylus userstyle hides vote counts on both voted and unvoted comments and your own comments. I really like what Deimos did, it significantly improved my time here on Tildes. If you want the feature back, install Stylus extension, click the Stylus icon > write style for tildes.net and paste this:

      /* Hide vote count for unvoted comments */
      .btn-post-action[name="vote"] {
          visibility: hidden;
          position: relative;
      }
      .btn-post-action[name="vote"]:after {
          visibility: visible;
      	content: "Vote";
          position: absolute;
      }
      
      /* Hide vote count for voted comments */
      .btn-post-action[name="unvote"] {
          visibility: hidden;
          position: relative;
      }
      .btn-post-action[name="unvote"]:after {
          visibility: visible;
      	content: "Voted";
          position: absolute;
      }
      
      /* Hide vote count for your own comments */
      .comment-votes {
          display: none;
      }
      

      Known issues

      • There is extra padding around Vote button
      • Extensions such as Vim Vixen cannot interact with Vote button
      10 votes
    2. We're starting to have more contributions for custom themes and extensions. I think it's about time we start to catalog these nicely.

      One of the unfortunate realities of open source efforts is that these efforts are often fragmented and scattered all over the place, making things difficult to find. With that in mind, I've...

      One of the unfortunate realities of open source efforts is that these efforts are often fragmented and scattered all over the place, making things difficult to find. With that in mind, I've started a new GitLab project here consisting of a simple README file that we can use to start tracking the client-side themes and extensions that the community here has been hard at work developing.

      The list, at the time of posting this, is empty. The README is sparse and the entire thing is subject to change by the community itself. I will only be reviewing changes to ensure that changes are acceptable before a merge is allowed through (we don't want e.g. malicious links thrown in or perfectly good projects removed by someone acting in bad faith). You can change contribution notes/guidelines, existing language, layout, categories, and whatever else you can think of. If there's something else that you think the repository could use aside from the README, then you're free to issue a merge request to have it reviewed as well.

      I'm hoping that this will help us keep track of everything and aid future users in discovering the various tools and themes provided by the community.

      Please feel free to discuss guidelines here. Is there anything that shouldn't be allowed on the list? Is there anything that should be taken care of immediately? Are there any immediate concerns? Is there anything else on your mind?

      19 votes