-
-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reply lines become misleading #4
Comments
Yes, it's intentional.
Yeah it's made to look like Twitter, but the lines have no actual relation to the actual replies because there's no helpers for that (Mastodon doesn't support threading at the moment). They just feel so "empty" without any indication or relation to each other: I understand it's the same way than in the default UI like this, but I still kinda like it has "something". I'm not going to instantly remove the reply lines, but will think about it. I'm open to ideas here. Faded or dashed line or something? 🤔 |
Horizontal lines between the posts? Vertical lines indeed create an illusion of related posts. |
The current structure allows only for them all to be linked or none of them. In my opinion neither is good. Some day I'd like it to be like this: I'll try to get helper classes modified to my instance first and then make styles for them. After this I'll revert the default to non-lined version. I hope Mastodon core will have some helper classes in the DOM in the future. Right now they are all on the same level. |
Changed the structure to be more reliable, see the commits. |
I'm going to close this for now as the fallback is implemented by default (with lines) and adding the threading support is well documented. We'll see what happens in the Mastodon core in the future. |
The lines are usually supposed to show that a reply is a direct reply to the one above, however this reply below isn't responding to the one above it, it's replying to another post above the rest.
Although it does look more like Twitter, I feel it's probably best to remove them for now because Mastodon's way of handling replies don't work for it
The text was updated successfully, but these errors were encountered: