LoqiIt looks like we don't have a page for "multitags" yet. Would you like to create it? (Or just say "multitags is ____", a sentence describing the term)
LoqiIt looks like we don't have a page for "multitag" yet. Would you like to create it? (Or just say "multitag is ____", a sentence describing the term)
kisik21I thought of a clever idea of encoding data as plain text and then passing a hash with it. If the data is tampered with, I easily notice. And nobody can pass me another hash without knowing a little secret!
[tantek]I think refinement (ands) is a more common case than unions (or), simply because you can "just" open multiple tabs to look at such unions, but a refinement can only work with explicit support
kisik21gRegorLove: what's up with your webmentions? You don't seem to be advertising an endpoint (but I have passed your challenge of mentioning you with getting your h-card!)
[kevinmarks]Refinement versus unions varies depending on the commonness of each term. If the intersection is empty, then the union is more useful. If one is super common, then the other is a good refinement.
[kevinmarks]The other thing that is handy is looking at which tags co-occur. That can be useful for further expansion if they found a rarer term with a more common one attached.
[jgmac1106], iasai and [pfefferle] joined the channel
ZegnatIf you want to go really fancy you could do both. Use comma for or, and slash for and. E.g. /tag/tech,indieweb lists all posts that have either tech or indieweb tags. If I want to refine that to only indieweb and tech posts that mention PHP I make it /tag/tech,indieweb/php
jeremycherfas!tell GWG there was an interesting discussion on location at IWC Nuremberg, and the use of, I think, a Google system that allows you to specify the area of interest from very large to very small. Maybe zegnat can remember it.
LoqiGWG: jeremycherfas left you a message 3 minutes ago: there was an interesting discussion on location at IWC Nuremberg, and the use of, I think, a Google system that allows you to specify the area of interest from very large to very small. Maybe zegnat can remember it.
kisik21!tell [eddie] your comments are doubled up because something's wron with your twitter syndication process. Same is on aaronpk's website, where my comments are shown with the birdsite syndication link below. Maybe webmention.io is to blame?
[schmarty]kisik21: many folks that show webmentions don't have any kind of de-duplication, so a response from your site and a response from you on Twitter are treated as two separate responses
[eddie]kisik21 If I read that right, my and aaronpk's comments show up twice on your website? It's probably because I syndicate all my content to twitter so you get both my indieweb webmention and the twitter syndication response
aaronpkwhen i get a webmention from eddiehinkle.com I also store any u-syndication URLs it claims. then when i get a mention from bridgy for a tweet, i can see that the canonical was already received from eddiehinkle.com
[eddie]My biggest thing holding me back was jekyll (because of the way I had it set up) Now that I'm using my own node.js rendering engine, I should be able to open and resave a post. Essentially the one thing that's holding me back is updating a post, I have to get that internal logic built out. Once I get that then when bridgy returns the syndication url from my webmentions I can update the post with the correct urls
[tantek]So when someone receives a Webmention from me, and retrieved my post, it already has all the automated u-syndication links in it. (IG POSSEing & syndication links still manual and sometimes not til hours later)
[jgmac1106]so can I embed an h-feed, and then a set of h-entries for each badge recipient so I could just make a recipients section instead of one page per badge issued?
[jgmac1106]so I can do single file webmention badges from the wiki now, but can't out the way no to display all the u-reply-of in the content obviously. In terms of a wiki would be better to have each badge a page and a list of recipients or some type of template:badge and use one file per badge
Zegnat[jgmac1106], the problem with the wiki is that the editable area is all marked as the content, so you are always putting the reply-to urls within the page content.
Loqifeatured is a proposed mf2 property (typically as u-featured) for h-entry that indicates a representative image for a primarily textual post https://indieweb.org/featured
ZegnatFeatured images are like those nice little hand-drawn-style images on A List Apart, or the big screenfilling images behind the post title on Medium. I tend to see them more as an illustrative addition to a post, possibly representing a post among other posts. They do not tend to be actual content.
ZegnatWiki doesn’t really care how many pages it has. I’d like to see all the “issuances” of the same badge on one page, fun way to see who has them. Just not sure *our* wiki has a simple way of supporting that
[tantek]aaronpk, jgmac1106, zegnat, re: the wiki auto sending webmentions etc., see the Wikipedia indieweb projects also — ideally we'd prototype this functionality and get it working on the IndieWeb wiki before Wikipedia: https://indieweb.org/MediaWiki#Building_Block_Proposals
jgmac1106sknebel I was trying to copy the way gRegorLove uses states on read posts…but <data class="p-category" value="$">$name </data> doesn’t parse as well
jgmac1106[skenbel] hat I really want is p-criteria and p-evidence so I would be able to quikcly parse and sort through posts…but trying to do this with existing properties
[jgmac1106][kevinmarks] do you mean the banner img behind someone's avatr. I would call that the u-featured of an author property....or just the u-featured of that page