Gregory's Server@mittorn
1. What loop, in the first place? How do you *make* a loop?
2. We overhauled protocols in 2017. We can fucking do it again.
3. Up to the implementer, I guess. We can have an option to show additional parents or not, I think.
|
3 comments
 1. Well, this is not really a loop, is it. The graph still goes in one direction. Rendering is another question entirely, it may be up to the implementer. Maybe someone will actually build a graph view instead of linear feed. Who knows. The options are there, earlier you even suggested a few. 2. Everything breaks eventually. Ostatus broke. So will AP. |
@drq @mo @BigFoxBoss
1. Here you posting link to other posts in THIS thread. So if you make this like multy-reply, it will be loop, not polytree. Even if it not looped really, this means rendering 2 same branches. Both is useless.
We need hard-break or soft-break this. I suggested ideas how it may be done, but this means not multy reply, but one reply and junction points. Only render first branch, second just link, junction point.
2. Do you really want break just working thing? Maybe we do not need AP at all, but you know, if we break what works now, then it will be very hard to build community again in this world when everybody get addicted to whatsapp/tiktok/etc. And you know how this addiction is strong. And again, all might be done without breakage using extension. JSON-LD is pain of AP, but this is not catastrophe and may be worked around in way, compatible with all implementations.
@drq @mo @BigFoxBoss
1. Here you posting link to other posts in THIS thread. So if you make this like multy-reply, it will be loop, not polytree. Even if it not looped really, this means rendering 2 same branches. Both is useless.
We need hard-break or soft-break this. I suggested ideas how it may be done, but this means not multy reply, but one reply and junction points. Only render first branch, second just link, junction point.