Hide individual posts without blocking blog.

Comments

5 comments

  • Jennie

    I would like a close variant of this: a mute button for a blog. Consider the following scenarios:
    - Generally you like a blog's content, but occasionally your current mood and their current mood don't match. Just make them disappear from your dash for a while.
    - A blog starts "rapid fire" reblogging, where you only see pages and pages of their posts on your dash, and this batch tends to be off lower quality.
    In both cases, you want their posts to disappear, but not necessarily unfollow. A "mute" button, to shut then off for an hour (or some other time window), would be nice.

    6
    Comment actions Permalink
  • FckMe2Dad

    I know just what you mean. I end up UN-following when a blog starts a deluge of re-posts, especially when they are re-posts of posts just posted by another blog you may follow! Your idea sounds good, however what happens when you later UN-mute? If you like or want to browse back into your dash feed, you're going to see those million re-posts, or off topic posts after UN-muting? Hiding individual posts would/should "hold" forever, unless you actually went to the blog in question's archive and intentionally UN-hid that particular post.

    0
    Comment actions Permalink
  • Jennie

    A lot of it depends on how they implement it. Currently, if you follow a blog mid-dash, and don't refresh the dash, you still don't see that blog's content until the page makes the next fetch scrolling down, and you'll see nothing from the recently-followed blog if you scroll back up. After the mute expires, I would expect to see all their posts again. (This is could actually be implemented entirely client side, with an x-kit style extension - just don't show the post/fetch the rest of the post if the poster is the muted user. I'm assuming the backend here is similar to Tumblr's "/posts" REST endpoint.)

    I agree that "hide" should be persistent. Both are related to hiding content, but different enough that maybe I should open a different request. I'll do that, but let this sit for a day or so first in case anyone else wants to chime in.

    0
    Comment actions Permalink
  • JoshSlater

    I think this is a problem that is shared with many platforms. In practice there are multiple issues that needs to be untangled. Some accounts are "source accounts" posting original or at least unique content. They vary between high quality and must see content. You want these posts in your feed. Some of them you even want to make sure you never miss a post from. Then there are accounts that just heaps out volumes of reblogs. These are typically people with whom you share taste and interest. You want some of their content, because it points you in new directions, but you don't really care if you miss anything.

    1. There is a difference between bookmarking an account and wanting to see all of their content. Perhaps the easy way right now is to just have a Mute button on the subscription. You can still click it to see their blog. You absolutely want to track this information though, to create better feeds and recommendations in the future.

    2. There is a difference between accessing all content chronologically as it happens, accessing it in a deduplicated and possible with watch markers to avoid seeing things more than once, and accessing it in a smart curation. The "smart" curation could be to interleave the top X posts from each blog into a stream that is more resilient against the burst nature and difference in volume between blogs.

    3. There should be a difference between like and save for a post. This would allow for better generation of feeds, and also to pair users with eachother to create automatic recommendation.

    0
    Comment actions Permalink
  • Jennie

    @staff This thread had moved beyond the original feature request (and I'm probably to blame), which is a reasonable and valuable feature that should be implemented regardless of this conversation. Would it be possible to move this discussion to the general forum, while keeping the feature request in place?
    Regarding point 1, there is an open feature request for blog grouping. That would solve that problem - I could have the main dash, with all followed blog's, and switch to a grouped view to only see a subset of those ("suspension bondage" or "people I chat with" or whatever groups I create.)

    For point 2, if staff even considers non chronological posts, I will personally be the domme to engage in lengthy and painful CBT sessions with the staff until they change it back. That is the most hated feature of FB and Twitter, and tumblr got massive push back even though they let you disable it.
    3. Like is pretty meaningless here; i just use it to track what I've reblogged. But there's not a lot of analytics that can go into it, since most posts are poorly tagged and severely lacking in content metadata. A meta-tagging system would be useful here, but that's probably 3-4000 hours of development time the staff didn't have.

    Hopefully everything I said makes sense, the mobile interface only shows 2 lines, so it's hard to go back and proofread.

    1
    Comment actions Permalink

Please sign in to leave a comment.