Gregory's Server@drq @mo @BigFoxBoss
1. When you replying to post in this thread, this is not tree or polytree, just looped graph. To make polytree you need break loop, losing connection
2. Unlikely, very unlikely. Just because of technical solutions in implementations. It's more, more safe to send second and next replies in separate fields. This will just work with current implementations.
3. ok, that is possible way to compose such message. I suggesting here specify if we should show reply copy here or just embed it as forward (with link to original) so we may avoid flooding when do not want extra reply to be shown
4. Connecting many threads with different ideas may produce even more dramas. But if it will be secondary replies, not showing whole thread (not connecting it techincaly, not mergin replies and leaving visual split between threads), then ok.
|
Top-level
 4 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. |
@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.
@mo @BigFoxBoss