"*" search results - search chat.indieweb.org

1709035 results for "*"

So the `h-cite` class isn't strictly required. However if you have any `e-*` properties like e-content, the p-name is *not* implied
gRegor at 2026-01-16 21:16
Ah, I see the edge case here. A minimal bookmark post like https://indieweb.org/bookmark#How_to_markup will imply the `p-name` as the link text
gRegor at 2026-01-16 21:16
You do have an issue for support of `h-cite`. I just saw it when I was looking though them
btrem at 2026-01-16 21:07
https://github.com/aaronpk/IndieNews/issues/60
gRegor at 2026-01-16 21:06
gRegor: it was definitely not what I wanted because it didn't fix the Indienews submission
btrem at 2026-01-16 21:06
I think I have an IndieNews issue for it to support `u-bookmark-of h-cite` to get the title from the link
gRegor at 2026-01-16 21:06
btrem, from a strict mf2 parsing perspective, yes, properties can be nested. It is probably not what you want, though, unless you definitely want the post title to also show up in the content. Example: https://php.microformats.io/?id=20260116200536351
gRegor at 2026-01-16 21:05
Generated a new draft of the newsletter! https://indieweb.org/this-week/2026-01-16.html
Loqi at 2026-01-16 21:00
i use that for everything
aaronpk at 2026-01-16 20:59
aaronpk: ha, just poked my nose under the hood of aaronpk/IndieNews, and found ` $xray = new p3k\XRay();`. So yeah, using the preview link you suggested would be rather helpful to the end results
btrem at 2026-01-16 20:58

Sort by:

Filter results by:

Tag

Query took 0.05s.

Exclusion: +foo -bar
Logical OR: foo OR bar
Exact phrase: "foo bar"
Partial words: foo*
Particular fields only: title:foo; domain:example.org; nick:somebody; after:2016-11-23; before:2016-11-23; date:2016-11-23