Citiverse
  • hwll@sunny.gardenH
    1
    0

    @JessTheUnstill I don't necessarily even blame the folks doing it, because so many are hurting... It's hard to exercise meaningful empathy when you're scared just for yourself.

    But yeah, we'll never prefigure a real mutual aid economy if all it means is "I need help from you."

    Good point.

  • jesstheunstill@infosec.exchangeJ
    13
    0
    1. There's no mute conversation button on someone else's post

    2. Hit reply on the post - note by default it says public and includes the person's username

    3. Change the post visibility to private

    4. Make a junk post

    (Continued)

    Link Preview ImageLink Preview ImageLink Preview ImageLink Preview Image
  • jesstheunstill@infosec.exchangeJ
    13
    0

    Now it allows you to mute conversation

    Link Preview Image
  • jesstheunstill@infosec.exchangeJ
    13
    0

    @hwll This isn't even specifically about mutual aid folks. It can be anyone for any reason. People shitposting about something you don't care about. People with a really popular political post that keeps getting boosted into your timeline but you don't want to see it. A meme you just hate for whatever reason. It doesn't matter. Your timeline is your own.

  • jesstheunstill@infosec.exchangeJ
    13
    0

    @CarbonCarrot It's more likely a Mastodon limitation. My HYPOTHESIS is that each conversation has a ID on it, which is how it decides on conversation threading and such. Your instance won't allow you to make any changes on other people's posts - for obvious reasons. The mute conversation feature may be working by setting a metadata tag on one of your posts where it suppresses anything with that particular conversation ID on it from appearing on your timeline. But it's still a crappy UI/UX for what should be basic functionality.

  • anctreat5358@mindly.socialA
    1
    0

    @JessTheUnstill *Thank you*! I've wanted this capability for a long time.

  • xanna@mastodon.ieX
    1
    0

    @JessTheUnstill I thought if you take out all the usernames it stops being part of that conversation? Good to know

  • julian@activitypub.spaceJ
    192
    0

    jesstheunstill@infosec.exchange the inability to mute someone else's conversation seems to arbitrary. Maybe there's a technical reason behind it but there needn't be...

  • webhat@infosec.exchangeW
    4
    0

    @JessTheUnstill I do something similar to this, instead I add a poll to remind me of the post in X days. I wonder if it work with a mute? 🤔

  • 8r3n7@mstdn.ca8
    1
    0

    @JessTheUnstill

    Is there some reason these steps cannot be automated, and exposed as a single control in the UI?

  • julian@activitypub.spaceJ
    192
    0

    webhat@infosec.exchange oh my god, using a poll as a hack for snoozing is genius

  • webhat@infosec.exchangeW
    4
    0

    @julian thank you, I don't think I came up with it originally

  • aslakr@mastodon.socialA
    8
    0

    RE: https://mastodon.social/@aslakr/109789888503839904

    @julian @JessTheUnstill Muting/following conversation and sub-conversation (threads) is one of the things I miss from usenet.

  • jesstheunstill@infosec.exchangeJ
    13
    0

    @8r3n7 a 3rd party client could probably automate some sort of hidden meta-post, but no idea how fragile that might end up being. And yeah, Mastodon devs could build something to fix it, but I don't think it's on their roadmap anytime soon.

  • ticho@mas.toT
    5
    0

    @julian @JessTheUnstill After a brief dive into the mastodon API documentation, it seems to be a protocol limitation indeed. You (or rather your client program) do not get to see the conversation ID until you join that conversation, so until then, you do not have the correct piece of information to request muting of that conversation.

    Some references:
    https://docs.joinmastodon.org/methods/timelines/#home
    https://docs.joinmastodon.org/methods/conversations/#get

  • xinit@mastodon.coffeeX
    1
    0

    @JessTheUnstill
    I know you're talking about the default web client, but for what it's worth, some clients do include this mute option.

    Link Preview Image
  • julian@activitypub.spaceJ
    192
    0

    ticho@mas.to hey, I sort of disagree. While the protocol itself doesn't contain topic level information, it can be inferred from context.

    This is how NodeBB achieves it. It also sends contextual information so it's explicitly available as well.

  • oblomov@sociale.networkO
    34
    0

    @JessTheUnstill this is an exceptionally useful tip. It's also grotesque that it would be needed in the first place.

  • ticho@mas.toT
    5
    0

    @julian While in general, I agree, you could implement some sort of heuristics, there is one huge difference - a NodeBB server is centralized and sees everything. With Mastodon, half of the posts in a conversation might not be visible to you, either because of being outright blocked, or the post simply not hitting your instance because of where the participants post from.

    Any heuristic based on unrelated metadata would be inaccurate at best, but more often than not outright misleading.

  • strypey@mastodon.nzoss.nzS
    4
    0

    @JessTheUnstill
    > Reply to a post, set the visibility to "Private Mention", remove everyone's username from the post. Post it. Then you can click "mute conversation" on THAT post, and it silently mutes you from the conversation

    That's a really smart hack. It never would have occurred to me. I'd never even noticed that you can only Mute Conversation in your own posts!

    (To be fair, that might not be the case in the third-party apps I use; Moshidon, FediLab and Enafore.social)


Citiverse è un progetto che si basa su NodeBB ed è federato! | Categorie federate | Chat | 📱 Installa web app o APK | 🧡 Donazioni | Privacy Policy

Il server utilizzato è quello di Webdock, in Danimarca. Se volete provarlo potete ottenere il 20% di sconto con questo link e noi riceveremo un aiuto sotto forma di credito da usare proprio per mantenere Citiverse.