You are reading content from Scuttlebutt
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
@Matt Lorentz %eMmIdiGGhXZSSpeXCkLqaNeg6ijao/68RdWn7t8C5Fo=.sha256

This thread prompted some good discussion at Planetary yesterday. We are going to change our block button to say ignore. We are also going to add a short confirmation message that makes it clear what ignore does and that it's publicly visible who you are ignoring (for now).

I would love to support forget someday, but I don't think we're there yet. Planetary nulls out the feed of someone you block in go-ssb but doesn't fully purge them from the SQLite cache. Furthermore we don't have db compaction so you don't get any disk space back which would be a big part of forgetting I think.

Follow is trickier to change I think, because it's an action with a lot of transitive consequences right now. You already remember the profile of lots of people you don't follow, so remember isn't quite right. I like listen a lot. The people you follow/listen to show up more prominently in many clients, and it's an echo of "freedom of listening".

OTOH follow is one of the only familiar social concepts in ssb that works exactly how users expect. Unlike blocks, rooms, public posts, etc. which are terms that new users know from other platforms but mean something different on ssb. So maybe that's one point in favor of keeping it.

User has not chosen to be hosted publicly
@Matt Lorentz %Hch0I7kETtI2Uzfyg4lLFxgjuNV0v8xKwZFNDF+F5/E=.sha256

@moid oh, no I didn't remember that. In fact Patchwork uses both "listen" and "ignore" already.

Screen Shot 2022-06-14 at 11.40.44 AM.png

Thanks for bringing that up. I'm going to bring it up again with Planetary folks because I don't think we considered it. But my inclination is to still make the change, because the baggage block carries seems more harmful than the baggage that accompanies ignore.

User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
@Rabble %h27t9Wn8cS83y8aN4/zkPxF1nxL59pZ/8HXc9SIcKVM=.sha256
Voted > maybe instead of "follow" and "block" it should be **"remember"** and **"
@Rabble %dF+Njr2LaxfqoPvFGScNY2q8u3UA+B/ydn4Bbal71iw=.sha256

There are several concepts to convey here.

  • do I want to see this person’s feed
  • do I want to convey their feed to my followers to be in their extended network
  • do I want to stop seeing their stuff
  • do I want to tell others that they might not want to follow or replicate this feed.

Sometimes we want to do things for ourselves and others for our network. I could imagine someone who wanted to follow a person who posts erotica but doesn’t want to either be public about that or at least not convey that feed automatically to others.

The block language is just wrong because it doesn’t work like users have come to expect.

Private follows / unfollows / “blocks” should help. The question is just what to call it and how to show it to users so they understand.

@zoo [planetary] %I5EGzDSpipQo92FNvs9GhFk91NIdd1eSzejSDuDO5lk=.sha256
Voted > maybe instead of "follow" and "block" it should be **"remember"** and **"
@cel %yNiQNffG+ZEXQH2TgsD0TWN8NXUj29LOEp3cpXC9LCU=.sha256

"Fork group to continue without this person"
"Fork group to add this new person"

User has not chosen to be hosted publicly
Join Scuttlebutt now