Don't show duplicate posts in timeline #78

Open
opened 2023-08-02 18:40:50 +02:00 by aylamz · 5 comments
Member

Replies to posts in timeline also show the post being replied to which results in duplicate posts. That makes it quite annoying to read the timeline and keep track of the conversation as you have to get through a bunch of duplicates.

Some examples:
duplicate_posts.png
duplicate_posts2.png

Replies to posts in timeline also show the post being replied to which results in duplicate posts. That makes it quite annoying to read the timeline and keep track of the conversation as you have to get through a bunch of duplicates. Some examples: ![duplicate_posts.png](/attachments/ec2427e1-2d7f-4d7c-a4f7-fddbeca24de1) ![duplicate_posts2.png](/attachments/3ba589de-225b-4359-ade6-827c9a414160)
aylamz added the
enhancement
label 2023-08-02 18:40:50 +02:00
Member

This is probably something that I like about *key, dealing with threads on mastodon or *oma isn't pleasant when you scroll by, since you don't really see context, and both feel like making the conversation clean and easy to understand is not a goal of both

This would be the best as an option I feel like

This is probably something that I like about *key, dealing with threads on mastodon or *oma isn't pleasant when you scroll by, since you don't really see context, and both feel like making the conversation clean and easy to understand is not a goal of both This would be the best as an option I feel like
Author
Member

I don't mind that it shows the posts being replied to (actually quite like that), the problem is duplication. Maybe if there is a post and reply to that post on a timeline then these could be combined in the UI, so you see each post only once? Same with boosts: if someone you follow makes a post and then someone else you follow boosts it, you see it in your timeline twice in a row which is unnecessary - in this case the the original post and "Boosted by $USER" should be combined into one.

I don't mind that it shows the posts being replied to (actually quite like that), the problem is duplication. Maybe if there is a post and reply to that post on a timeline then these could be combined in the UI, so you see each post only once? Same with boosts: if someone you follow makes a post and then someone else you follow boosts it, you see it in your timeline twice in a row which is unnecessary - in this case the the original post and "Boosted by $USER" should be combined into one.
jeder added the
frontend
label 2023-08-03 19:28:23 +02:00
Member

I've implemented this custom css which I'm happy with.
I'm sharing it with you, in case it might give you ideas for a new feature.

.notes .reply-to {
    opacity: .5;
    max-height: 50px;
    overflow: hidden;
}
.notes .reply-to:hover{max-height: initial;}

View Demo (.gif)


Update :

.notes .reply-to {
  max-height: 72px;
  opacity: .5;
  box-sizing: border-box;
  overflow: hidden;
  transition: max-height .3s, opacity .3s;
}
.notes .reply-to:hover{
  max-height: 100vh;
  opacity: initial;
}
I've implemented this custom css which I'm happy with. I'm sharing it with you, in case it might give you ideas for a new feature. ```css .notes .reply-to { opacity: .5; max-height: 50px; overflow: hidden; } .notes .reply-to:hover{max-height: initial;} ``` **[View Demo (.gif)](/attachments/c8019675-4168-4c07-89c8-2071ebf5f9ed)** --- Update : ```css .notes .reply-to { max-height: 72px; opacity: .5; box-sizing: border-box; overflow: hidden; transition: max-height .3s, opacity .3s; } .notes .reply-to:hover{ max-height: 100vh; opacity: initial; } ```
Member

Last night I was at a mastodon user meeting in Paris.
I took the opportunity to talk about Iceshrimp, as people didn't know about it but had heard of Firefish.

The general response was "It's very nice, but the timeline is unreadable with 2-post threads for replies".

This reinforces my idea that, by default, you shouldn't be able to see the posts for which the reply is intended.

Last night I was at a mastodon user meeting in Paris. I took the opportunity to talk about Iceshrimp, as people didn't know about it but had heard of Firefish. The general response was "It's very nice, but the timeline is unreadable with 2-post threads for replies". This reinforces my idea that, by default, you shouldn't be able to see the posts for which the reply is intended.
Member

Akkoma has "Reply to" which I think we should replicate, you can hover (desktop)/click (mobile) on it and it will show the post that was replied to
Screenshot_20231001-143210~2.png
Screenshot_20231001-143236~2.png

Akkoma has "Reply to" which I think we should replicate, you can hover (desktop)/click (mobile) on it and it will show the post that was replied to ![Screenshot_20231001-143210~2.png](/attachments/bf4ab93f-9fcb-42b3-9ed5-505adb761939) ![Screenshot_20231001-143236~2.png](/attachments/90c5bb65-ba79-457a-860a-37d613dd17b6)
zotan self-assigned this 2023-10-01 17:46:56 +02:00
AntoineD added this to the (deleted) milestone 2023-12-03 00:45:51 +01:00
AntoineD added this to the Frontend rewriting project 2023-12-12 18:20:23 +01:00
Sign in to join this conversation.
No milestone
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: iceshrimp/iceshrimp#78
No description provided.