Email or username:

Password:

Forgot your password?
Dr. Quadragon ❌'s posts Post Back to profile
Top-level
Dr. Quadragon ❌

@mo There could, or could not be. It's up to the people involved.

@mittorn @BigFoxBoss

29 May 2024 at 15:40 | Open on mastodon.ml
4 comments
Мя :sparkles_lesbian: replied to Dr. Quadragon ❌

@drq how would you render such a mess if they will?

@mittorn @BigFoxBoss

29 May 2024 at 15:41 | Open on mastodon.ml
Dr. Quadragon ❌ replied to Мя

@mo No idea how to render this one-dimensionally (maybe someone more clever than I am can), but we probably could use time and do something akin to what @mittorn proposes, and show an "also a reply to:" field in such message.

@BigFoxBoss

29 May 2024 at 15:49 | Open on mastodon.ml
mittorn replied to Dr. Quadragon ❌

@drq @mo @BigFoxBoss ok, as you want you answer show multiple times, this could be rendered as reply, but with link to another thread point with first reply source, instead of rendering all children. That duplication will allow keep consistency and even work with "polytree" model.
But in that case only one reply source will be rendered, other only referenced
And this will not show single thread as "Polytree", there will be 2 separate threads, but with "weak" junction point, so all next replies will go to thread, where first reply source was

@drq @mo @BigFoxBoss ok, as you want you answer show multiple times, this could be rendered as reply, but with link to another thread point with first reply source, instead of rendering all children. That duplication will allow keep consistency and even work with "polytree" model.
But in that case only one reply source will be rendered, other only referenced
And this will not show single thread as...

29 May 2024 at 15:57 | Open on masturbated.one
Dr. Quadragon ❌ replied to mittorn

@mittorn Basically, joining two adjacent threads into one down the line. Yes, that's what I want.

@mo @BigFoxBoss

29 May 2024 at 16:04 | Open on mastodon.ml
Go Up