Show Navigation
Conversation
Notices
-
@maloki quit.im is my image sharing account, it is probably inappropriate/impractical to have any non-imagery discussion with that account :]
-
@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 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 never stored or distributed from #Mastodon (which relies entirely on thr:in-reply-to)
What we have is however a bit of a mess and I don't remember which part is what we actually use and which part just comes along from #StatusNet (where none of this worked and conversations were even more broken).
-
@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="https://social.umeahackerspace.se/conversation/690842"/>
<ostatus:conversation href="https://social.umeahackerspace.se/conversation/690842" local_id="690842" ref="https://community.highlandarrow.com/conversation/429650">https://community.highlandarrow.com/conversation/429650</ostatus:conversation>
Which is an incomprehensible mess that I fully understand if @Gargron hasn't bothered trying to understand. (though I have a vague memory of him asking me about it, or someone else, and I couldn't give an answer. Maybe if I have enough sleep tonight I'll give a go at clearing the mess up tomorrow).