One Twitter feature I *clearly* miss here on mastodon is restricting people's ability to reply to a post.
That was an absolutely killer feature on Twitter and I very much want it.
One Twitter feature I *clearly* miss here on mastodon is restricting people's ability to reply to a post.
That was an absolutely killer feature on Twitter and I very much want it.
*Is* it hard? I think the original author's server just refuses to add certain, or all, replies to the replies collection.
Remote servers can still generate replies, although the better-behaved ones won't, but any replies generated won't be compiled on the original post.
@charlesrandall it's extremely hard to do in an enforceable way, less hard to do in a "respect these technical norms or we block you way". Something I'm thinking about for the longer term for hometown
@darius @charlesrandall I think a good remote server would let the user know that their reply won't behave as expected. It might offer to quote toot instead!
@evan @charlesrandall if you want to make it literally not possible in the UI of a remote server for someone to reply, that is hard
But you're right, you could simply neither advertise replies nor render them to the author - again though that is more like a mute than a permission model (I like it though!). The Twitter model is a permission one
@mariusor @darius well, @charlesrandall mentioned the case of replies to replies, or even farther down in the thread. That might be tough, if the rogue reply was never saved or recognised!
@darius @charlesrandall I think I agree with @evan 's sibling comment the thread, it's not hard at all.
The server where the object that is being replied to is the place where this enforcement can be done. An object can claim that it is inReplyTo another object, but the server of the original object has authority to act on this fact. If the server doesn't add it to the replies collection of the original object, then it's other instances should not see it there. Am I missing something?
@mariusor @darius @charlesrandall We had a thread identifier in OStatus specifically for this purpose, but I don't remember if it survived into ActivityPub. I'll take a look. Obviously, it could also be an extension.
@evan I think building reply trees would be much more simple if besides the parent, all the grandparents would be included in the "inReplyTo" of an object. It's sad that nobody does this in any of the fediverse software.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.