@bix I’m uncertain if I want my replies appearing on someone else’s blog. I’m afraid it may have a chilling effect on my replies behavior. Appearing just on the timeline has an ephemeral feel to it.

@bix Hmm...let’s see. Although it serves different purposes. The existing one lets me display my replies on my blog whereas the new feature puts them on someone else’s blog. If I delete my response, will it also disappear from that blog? If yes, then I am interested.

@pratik @bix Yes, if you reply to someone's post, then delete your reply, it will disappear everywhere. Your reply isn't included in an export of someone else's blog either. I think it's okay without an opt-out setting for now, but it's a good discussion and something to revisit after more time with the new feature.

@manton That already makes me feel better @bix

@bix @pratik @manton All of the above sounds great and even looks beautiful on bix.blog, flowing nicely from the original post.

@bix @pratik @manton Now I throw a wrench into things: if a reply to me is deleted from micro.blog it won’t be automatically deleted from an external blog like mine, right?

I’d like to support an option like this but doubt that’s a feature of IndieWeb plugins on WordPress.

@fgtech @bix @pratik If you're using this new feature (which I'll officially announce tomorrow) the deleted reply won't show up. If you're using WordPress and getting Webmentions from Micro.blog, I think the reply will stay because it's copied. But that is probably fixable if Micro.blog can notify WordPress about the deletion. I'll check.

@manton Awesome. Please let me know what you find.

This seems like an area that could be abused (by forging delete messages to wreck someone’s comments, for example) so may not be implemented. Would love to see it done right.

@manton I have to moderate incoming comments, so maybe that would work for delete requests, too. I would love a way to “whitelist” micro.blog so it’s all automatic. That feature of WordPress doesn’t work right now with Webmentions.

@manton @fgtech @bix @pratik Not sure I want my name and comments displayed on any „random“ website. I’m strongly in favor of an opt-out option 😐

@manton if you serve a 410 from the orginal url and resend the webmention then the other end should remove it. www.w3.org/TR/webmen...

@hutaffe Thanks, I want to give it a little time before adding any settings, but I won't rule it out either. It's not exactly a random site since you're actively replying to someone's blog post. I can see how it gets confusing in a long thread like this one, though.

@kevinmarks Thanks. I need to add a little more information for deleted replies before I can support that, but I plan to.

@hutaffe It’s not at all random unless you send replies in a random fashion. Your act of replying sends a note (webmention) to the blog hosting the original post.

Playing devil’s advocate now: would you want people talking about your blog post online without telling you?

@kevinmarks @manton Excellent. Thanks!

@fgtech @manton „random" is probably too much, yes. My point is: Here at Micro.blog I currently have the control over where my replies stored. It’s what makes this a „social network" for me. As far as I understand this new feature at the moment, when it publically lands on a blog I replied to, I have no control at all. My name might be on a website in 10 years, even if I wouldn’t have an account here anymore. Maybe I just don't understand it correctly. When I ask for my data to be deleted (e.g. GDPR), there's just no way it will be deleted everywhere. I would have to remember every blog I replied to and ask for my comments to be removed. This might work automatically for some sites, but it can't be guaranteed for all.

I totally understand the usefulness and openness about this feature and why people might like it! I also think that this is what an open web should be like. But sometimes I want to define for myself how "open" I want to be 😉 For me personally, I would probably have to stop replying to posts.

@hutaffe Agreed. I am hoping to at least ensure that delete requests are handled on WordPress the way they are natively on micro.blog.

This is an interesting curveball in the “own your content” ethos. In some ways @manton’s job presents challenges the silos never had to face.

@hutaffe @fgtech Good feedback. Let me clarify one thing: the reply is not copied for blogs hosted here, it's included dynamically with a script. So if you delete your account here, your replies will disappear from all hosted blogs that were showing replies. For external blogs like WordPress, it's different... But that's separate from this new feature.

@bix I hadn't considered it, but now that you suggest it that does seem useful. Or maybe some other screen in M.b that shows conversations on your posts.

@manton @fgtech thanks! I think I got it wrong. The way this works seems like something I could actually like 😉 At least based on the Micro.blog community. My issue with external blogs and my name on them for „eternity“ is probably a general one with webmentions then. I guess I need to think a bit more about where I stand here, personally. Thanks for the clarification, and good job 🙂

@hutaffe @manton @fgtech Also thank you from my side. I am happy to see that M.b. thinks carefully about any new changes! I am a true laymen when it comes to hardcore blogging, but one reason for me to move to M.b. is that I can be creative and have a platform to show this while the M.b. infrastructure ‘offers’ the blog to a wider audience. If readers would like to respond they can do so via M.b. and I do not have to set up and manage registration of my site’s users and their replies. Especially the latter in light of GDPR makes me refrain from even having a ‘form’ on my site so that I do not violate any rules. Perhaps I am overly cautious here, but I simply like to continue with what I like doing most: show my creations on my own site and not overly concern myself with management of the site itself. If people can opt out from having replies included on a website outside M.b., it would be great so that no (GDPR) is infringed.