Skip to content
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

Quoted highlights #1438

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

jb55
Copy link
Contributor

@jb55 jb55 commented Aug 22, 2024

This is in preparation for Damus' highlight implementation. We have a new quote highlight variation. This is to prevent the creation and multiple notes (highlight + kind 1) for a single highlight action that wishes to add a comment along side a highlight, which looks bad in micro-blogging clients where these notes may appear in succession.

This is backwards compatible with existing highlights, except for the situation where clients might not properly handle the mention attribute.

Since @pablof7z has already mentioned he does not like this approach, we will create a DIP if/when this is not accepted.

@vitorpamplona
Copy link
Collaborator

The tricky part is determining whether Highlights should be on a kind1 feed or not. Amethyst has always shown them, but it hasn't been super well received. Highlights are seen as personal notes + notes for others following the original page/post. It's not about letting my followers know all the highlights of the book I am reading as I mark them. Users might be highlighting lots of things for their future selves and those just pollute their feed.

Derek posted 20+ highlights from an article he was reading last week. All highlights showed up to his followers. It was all fine, but it felt very weird. It looks like the user forgot that each highlight is a note and they are just spamming their followers with notes.

Otherwise, this looks ok to me.

@staab
Copy link
Member

staab commented Aug 22, 2024

This is backwards compatible with existing highlights, except for the situation where clients might not properly handle the mention attribute.

This seems like the main problem to me. I agree with Vitor's UX critique as well. Maybe a new kind would be better? I do agree that having a comment go with a highlight would be an improvement.

@vitorpamplona
Copy link
Collaborator

I do agree that having a comment go with a highlight would be an improvement.

Agree as well. I just don't know if this is a comment for future me, for public view in this site or for my followers.

Maybe a new kind would be better?

To me, it's either this or a regular kind1 quote with the highlight's nevent inside of it. I am not sure if there is a need for a new kind.

@staab
Copy link
Member

staab commented Aug 22, 2024

To me, it's either this or a regular kind1 quote with the highlight's nevent inside of it. I am not sure if there is a need for a new kind.

The problem with this is that you get duplicate notes, which is the original problem Will is pointing out. A new kind that is "highlight with comment for public viewing" vs the current "highlight without comment for private use" has pretty different semantics.

@vitorpamplona
Copy link
Collaborator

The problem with this is that you get duplicate notes, which is the original problem Will is pointing out.

Yeah, but if we all agree that the Highlight is supposed to be quoted by a kind1 to display on Kind1 feeds then we would never show the highlight event itself (or only show it as a "reply")

@pablof7z
Copy link
Member

I'm not vehemently against it, I mainly don't see the issue this addresses as a big problem, as clients already need to be aware of the other stuff they're rendering in a feed (i.e. reposts/quotes).

The drawback I see is that if you repost, are you reposting the comment? the highlight? I mean -- you're reposting both, but you can't repost just the highlight.

@staab
Copy link
Member

staab commented Sep 16, 2024

Coracle now supports rendering comment (in next release)

This is to prevent the creation and multiple notes (highlight + kind 1)
for a single highlight action, which looks bad in micro-blogging clients
where these notes may appear in succession.

Signed-off-by: William Casarin <jb55@jb55.com>
@jb55 jb55 force-pushed the quoted-highlights branch from 374ab01 to 270d1bc Compare November 11, 2024 20:18
@jb55
Copy link
Contributor Author

jb55 commented Nov 11, 2024

published DIP04 to document damus' implementation of this:

https://github.com/damus-io/dips/blob/master/04.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants