@pratik I'm trying to test this right now. I appear to have stumped Micro.blog (at least on Windows with Firefox) so I don't have the result just yet.
@pratik The quoted text stays as it is just text formatted in HTML (as far as I have seen so far). The link when clicked would give the appropriate errors.
@chaitanya Ok. That’s how I would want it to behave. I guess like regular blockquotes with a broken link.
@pratik Current status is the original, quoted post is staying on my blog. It's either taking Micro.blog a while to process the deletion or there's a caching type issue. As soon as the original post resolves correctly -- I guess to an error page -- I'll be able to see for sure how the Quoteback is affected.
@simonwoods Ok. So on your blog, the post A in which you quote post B stays intact with the blockquote even when you delete post B?
@pratik It is working exactly like that. For some time I used to use Quotebacks without giving it any URL just for posting a good looking quote.
@pratik So far, yep. However, it doesn't look like post B has been entirely deleted since you can still see it:
... so I'm going to keep the test going until I am confident post B has been entirely deleted and then consider the Quoteback post a credible test.
@simonwoods Yup. Makes sense now. This seems to be a Micro.blog issue more than a Quoteback issue. I just wanted to be sure that my blockquote stays on my blog even when the original post is deleted. @chaitanya confirms this will happen. Looking at the embed code, I too think this is true.
Now next question, would the styling of the blockquote go away if Quoteback gets shut down? I'm guessing it will if the javascript is no longer accessible. I'm loathe to host any more external javascripts on my posts. My only remaining concern with an otherwise excellent service.
@pratik Micro.blog hosts its own JS file for Quotebacks when you embed through the timeline. Though, since Quotebacks is open-source and people can host their own JS files, I think we can use it forever!
@pratik Am with you. I don't want to host and serve any more javascript - especially of something so early in dev. And risk of losing the ability to render quotebacks once the externally hosted js goes away of course is always there. So am not currently using quotebacks. It's a nice project that I will check back later.
@pratik this question is tending towards the philosophical (…trees falling and no one hears them kind of stuff) ... and I have no idea - but I don’t think the web will break ... just the post :-)