Conversation:
Notices
-
@maloki Right, that thing could probably be fixed by doing a remote-fetch of parent (which I believe #Mastodon does for replies to unknown posts, right?). I haven't checked whether the feed is fixed yet (@Gargron mentions the Suprrrfeedrrrrr "sanitation" with thr:in-reply-to) We stitch together instances in !GNUsocial based on the conversation URI though, which is nev…
-
@maloki I read the above discussion and just want to let you know that I'm always ready to know if something on our side should be improved or fixed. I've noticed already that the underscore-in-nick thing causes some confusion and I'm surely going to see if I can take care of the confusing UX around it on !GNUsocial's side.
-
@maloki The part of the federated Atom feed that tells !GNUsocial which conversation (if the in-reply-to is unknown) it should be stitched into looks like this: The part of the <link rel="ostatus:conversation" href="http://status.hackerposse.com/url/14849"/> <ostatus:conversation href="http://status.hackerposse.com/url/14849" local_id="690842" ref="http://status.hack…