WIP: Add ability to pin posts #2009

Closed
Dave wants to merge 17 commits from gitlab-mr-iid-739 into develop
Member

Closes #468

Screenshots

unpin_status

pin_status

Closes #468 Screenshots ![unpin_status](/attachments/1abd5fa2-a942-4aa9-b531-870476bec4b5) ![pin_status](/attachments/7d647350-6c77-4b48-81a4-f5d41cf38b22)
Owner

would it be appropriate to use the $status-margin defined in this file for the 0.75?

would it be appropriate to use the $status-margin defined in this file for the 0.75?
Owner

The [+] icon become fatter somehow

The [+] icon become fatter somehow
Owner

I'm thinking, maybe it would be an appropriate place to add an ellipsis button in the status-actions, and put pin, delete and maybe "open original" in the ellipsis menu, the top corner is getting a bit too cluttered as it stands.. @hj thoughts?

I'm thinking, maybe it would be an appropriate place to add an ellipsis button in the status-actions, and put pin, delete and maybe "open original" in the ellipsis menu, the top corner is getting a bit too cluttered as it stands.. @hj thoughts?
Owner

I don't think direct messages should have the pin icon, maybe only public/unlisted ones should have them?

I don't think direct messages should have the pin icon, maybe only public/unlisted ones should have them?
Owner

ellipsis was an idea for a long time. Putting it where "open original is" is a neat idea, but I'm not sure. I do like idea of adding "open original" into ellipsis menu tho

ellipsis was an idea for a long time. Putting it where "open original is" is a neat idea, but I'm not sure. I do like idea of adding "open original" into ellipsis menu tho
Owner

i'm ok with DMs having pins tbh, one could just leave a note to themselves this way

i'm ok with DMs having pins tbh, one could just leave a note to themselves this way
Member

The backend limits pins to public/unlisted

The backend limits pins to public/unlisted
Owner

oh, ok, thanks @rinpatch

oh, ok, thanks @rinpatch
Author
Member

That was why I got Could not pin error code. thank you for the confirmation @rinpatch

That was why I got `Could not pin` error code. thank you for the confirmation @rinpatch
Owner

I'm not sure if treating pinned statuses as a timeline is worth it, especially here it shows that we add some completely different behavior to this function just for pinned statuses. I know they're fetched like a timeline in the API but the way they're dealt with in the application is fairly different, we don't really need to poll for them, updating pinned statuses is fine if done only when opening a user profile or when pinning/unpinning something yourself.

I'm not sure if treating pinned statuses as a timeline is worth it, especially here it shows that we add some completely different behavior to this function just for pinned statuses. I know they're fetched like a timeline in the API but the way they're dealt with in the application is fairly different, we don't really need to poll for them, updating pinned statuses is fine if done only when opening a user profile or when pinning/unpinning something yourself.
Owner

@hj oh I meant putting it in status-actions, meaning where "delete" is now

@hj oh I meant putting it in status-actions, meaning where "delete" is now
Author
Member

@shpuld do you mean at the bottom?

@shpuld do you mean at the bottom?
Owner

yes, right from favorite star, replacing delete on your own statuses (and putting delete into that menu instead)

yes, right from favorite star, replacing delete on your own statuses (and putting delete into that menu instead)
Member

moved to #2039 since it is not allowed to edit this MR.

moved to https://git.pleroma.social/pleroma/pleroma-fe/pulls/2039 since it is not allowed to edit this MR.

Pull request closed

Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
5 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
pleroma/pleroma-fe!2009
No description provided.