Yeah, reasonable take. To be clear, this wouldn't detach these replies in any way, they'd just show up in a separate section like "Hidden by interaction settings" or similar. So the reply chain would not be broken.
it's easy to see this as a way for people to squash commentary they don't like or aren't interested in, but that's also kinda implicitly what threadgates do
yeah there's a flipside though — maybe the user's intent was to apply a threadgate and they forgot to do so, so applying one after the fact "resets" to the state it would have been in had they remembered
this is a good point too — we reuse the rkey of the post record and overwrite the threadgate record each time, so the latest threadgate would be what's used
Thanks for your thoughts on this! Just clarifying in case it sounded like we might break context: yeah this would essentially work the same as hiding individual replies, as you already said.
Yeah, reasonable take. To be clear, this wouldn't detach these replies in any way, they'd just show up in a separate section like "Hidden by interaction settings" or similar. So the reply chain would not be broken.
Yeah, reasonable take. To be clear, this wouldn't detach these replies in any way, they'd just show up in a separate section like "Hidden by interaction settings" or similar. So the reply chain would not be broken.
Yeah, reasonable take. To be clear, this wouldn't detach these replies in any way, they'd just show up in a separate section like "Hidden by interaction settings" or similar. So the reply chain would not be broken.
in my opinion this ended up being a great thing for react. if you chase “adoption” as a primary metric in your open source project, you’ll make different choices than if you just want the project to meet its use cases and be useful to other people
i worked on react at meta for eight years, and there was literally never a moment when the management would ask what we’re doing to increase “dominance” or “market share”.
if anything, the pressure was always slightly nudged towards internal use cases, and the team successfully pushed back on that
In your opinion, do you think it'd be enough to include a little blurb in the dialog like "FYI this will apply to existing replies", or should we provide a checkbox to make it optional?
Or is it clear and correct that an update to interaction settings post-facto does not affect any replies received before those settings were updated? (This is the current handling)
> user posts something > gets a ton of replies, some low quality > user restricts interactions to people they follow only > pre-existing replies from non-follows still appear
