It's weird when people say "you can't predict the future" when that is literally the only thing you can predict.
-
It's weird when people say "you can't predict the future" when that is literally the only thing you can predict.
-
It's weird when people say "you can't predict the future" when that is literally the only thing you can predict.
@evan haha yeah feels like it needs to be qualified with like a "reliably" or something
-
@evan haha yeah feels like it needs to be qualified with like a "reliably" or something
@doriantaylor even that's not true. You can reliably predict a lot of things!
-
It's weird when people say "you can't predict the future" when that is literally the only thing you can predict.
@evan I now know you were going to say that!
Gli ultimi otto messaggi ricevuti dalla Federazione
-
darius@friend.camp but to answer your initial query, I feel that summary is always going to be subservient to content. It's either a truncation or derivative of content, so if you have the capabilities to parse content, just use that in its entirety and pass over summary
(Until T&S standardize CWs, but that's a different story)
-
@julian @darius Hugo does the same by default, taking the first ~70 characters to the nearest word boundary (or something like that).
i'm just pointing out that there might be some needed disambiguation with how `summary` is used, to account for this kind of "excerpt vs subtitle", "duplicative vs additive" usage.
-
@criminalerin I like the joke but that's easy, 0 is female and 1 is male.
-
UE leader nei supercomputer (il secondo è italiano). Sull’Ai però va piano, Draghi: “Il divario con gli altri è netto”
@news
https://www.eunews.it/2025/09/16/ue-leader-nei-supercomputer/
L'HPC6 di Eni è il sesto computer al mondo. Ursula von der Leyen lo cita nel suo discorso a un anno dal rapporto dell'ex presidente della BCE
-
trwnh@mastodon.social end of the day. I think it's up to each implementor as to how they wish to populate summary.
NodeBB takes the first few sentences adding up to but not exceeding 500 characters, and uses those. It does change the HTML because simple truncation would leave you with broken or unfinished tags.
That's probably why darius@friend.camp said they were almost the same.
-
@darius @julian @technical-discussion one thing this suggests is that there is a semantic difference between "summary" in the sense of providing a short blurb that is additive to the content (kinda like a subheading!), vs "summary" in the sense of providing an excerpt to be used as a kind of preview (as in a list of articles)
-
I can't speak to whether using this field this way is good or not.
I would set some kind of threshold for a similarity metric (eg Levenshtein distance, maybe divided by string length) below which you only display one. Maybe that's too clever. But it would also catch cases where there was just some punctuation mark difference or something.
-
@darius @julian @technical-discussion interestingly https://indieweb.org/post-type-discovery#Algorithm suggests that you check if the `name` is a prefix of `content`, and if it is, then it is a Note. perhaps similar logic can be used to check if `summary` is a prefix of `content` in some way?
i don't think this is particularly *wrong*, as generating summaries from excerpts of content is a common pattern in e.g. static site generators like Hugo. it is indeed duplicative, though!
