#tantek.comedited /rel-author (+951) "How to publish and How to link to ActivityPub followable profile subsections, IndieWeb Examples, add self" (view diff)
#vanderven.se martijnedited /footnote () "(-4650) /* See Also */ Template-ify JSTOR link and remove Loqi’s full copy-paste of the article, felt like spam" (view diff)
#aaronpklol oops. missing pname on that article's microformats
#Zegnataaronpk: the problem happens even if there is a p-name. There is another link there to one of tantek’s posts, where the entire post is inside the p-name ;)
#ZegnatHow does Loqi handle that for chat preview?
#aaronpkthe p-name in that post from tantek is the entire contents of the post
#aaronpkthe rule for the wiki is use the name if present, otherwise assume it's a note and use the content
#ZegnatWhich probably works most of the time, but when you get towards article length, it just starts to feel like copy-pasting external posts onto the wiki
#aaronpkbut also people should stop putting the full text of notes in the p-name
#vanderven.se martijnedited /footnote () "(-3719) /* See Also */ Template-ify tantek example for multiparagraph footnote and remove Loqi’s full copy-paste of the article, felt like spam" (view diff)
#ZegnatSo. Now the See Also section is a bit readable again
#LoqiZegnat has 5 karma in this channel over the last year (18 in all channels)
#[tantek]I guess the question is what I am doing "wrong" and what I should be doing instead
#ZegnatDo not think anything is wrong there. It just happens to be a multiple paragraph note (note: p-name === p-content). It is probably only solvable with a max length, as aaronpk says.
#[tantek]Ok nothing "wrong" per se, then, however maybe there's a use-case here for p-summary, though it may be strange for the p-summary to be shorter than the p-name
sp1ff joined the channel
#aaronpki thought we changed the recommendation ages ago to not have p-name on notes at all
#LoqiPost Type Discovery specifies an algorithm for consuming code to determine the type of a post by its content properties and their values rather than an explicit “post type” property, thus better matched to modern post creation UIs that allow combining text, media, etc in a variety of ways without burdening users with any notion of what kind of post they are creating https://indieweb.org/post-type-discovery
#aaronpki think we should remove the algorithm from the /note page since it should be covered in post type discovery
#[tantek]IIRC we changed the recommendation to not have an empty p-name, not no p-name at all
#[KevinMarks]We used to have the problem of assuming the whole post was the name with fallback parsing.
#[KevinMarks]There is a sort of implied length rule where content length >summary length > name length but I don't think we have enforced or fully documented that, it's more a thing we got from blog and feed historic use
#[tantek]I think in general we want to always encourage explicit p-name in non-reaction posts because that's what readers / aggregators can/will display as the "short" representation of the post
#[tantek]Otherwise such apps look "broken" with an empty line (empty p-name) in their UI, so then they start making things up which leads to more weird coding for specific apps behaviors