#kylewmif anyone else is curious, the 3rd answer is the best one there
#aaronpkso yeah I can't make my tests for XRay pass until I use the fixed mf2 parser
#aaronpkotherwise I either have broken HTML escaping handling, or the contents of <script> tags ends up in the plaintext
shiflett and wolftune joined the channel
#aaronpkAny objections to me merging gregor's PR? (We have to get barnaby to do an actual release of a point version, but ppl can use the master branch if they want in the mean time)
#aaronpkyeah it'll be a while til we can actually drop 5.4 support
#aaronpkohhh it removes it from p-content but not from e-content
#aaronpkwell that's another question actually. should <div class="e-content"><script>alert("hi");</script></div> contain the whole script tag in the html value?
#aaronpki think technically it should, but the plaintext value should not include the alert("hi"); text
benwerd and shiflett joined the channel
#tantekaaronpk that sounds like a reasonable resolution
#tantekI would also be ok with a blacklist of tags to strip from HTML
#aaronpkI think that gets into dangerous territory
#tantekso the point is, we don't make up our own list, we go by the list of things that CSP thinks are "special" (worthy of blocking), and thus has been reviewed by all the security people that worked ont hat
#aaronpkwell I will say that I am sanitizing the HTML returned from the parser anyway, so the first thing that happens is I remove script and style tags anyway
#aaronpkso it wouldn't hurt if the parser didn't include those in the first place
#KartikPrabhukylewm: KevinMarks snarfed tommorris: sorry for not looking deeply at the mf2py performance issue. been pretty busy with "IRL" work; though kylewm seems to have it under control
#voxpellisince it does two things: Both establishes the taxonomy that things are tagged with and aggregates things using that taxonomy then WebMentions is enough for it
#voxpelliif someone else would like to reuse its taxonomy then those would need to rely on feed subscriptions
#voxpellibut yeah, it feels like an evolution of the planet pattern
ttepasse joined the channel
#tantekI'm not sure how submission based aggregators evolved
#tantekthere does seem to be appeal to people for both kinds
#tantek.comedited /planet (+817) "dfn, move past content to brainstorming, add why, how, examples stubs" (view diff)
#tantekbear, I've tried to help out on /palala and /planet - please review and see if they make sense per your expertise / focus
#LoqiA planet, in the context of the indieweb, and blogs/feeds for even longer, is a site that aggregates feeds/updates from a variety of sources, typically focused on a particular topic or community https://indiewebcamp.com/planets
#voxpelliAre there any example of planets created past the introduction of Digg/Reddit/Hacker News-like sites?
#tantekvoxpelli: good question. I wonder if new planets have been another one of the casualties of the transition from feeds/readers to social media/silos
#tanteksince planets were all AFAIK cross-site in contrast to silo reading experiences
#voxpellithat's why I'm thinking IndieNews might be the new "planet", because it takes the social media approach to "planets" and and brings it back to the indieweb
#tantekit's not really a social media approach though
#voxpellithey require an account though, but yeah, more "silo" than "social media" I guess, but still a child of the social media era
#voxpellithe submission and votes are still siloed – unlike with IndieNews others can't find out whether an article has been submitted to eg. HN without asking HN
#tantekI don't know about that either. Digg/Reddit/Hacker News are all more derivatives of Slashdot than any social media / silo
#voxpelliI think Digg/Reddit/HN takes inspiration from both Slashdot, which are fully curated by non-authors, and Planets, which are fully curated by authors
#voxpellisubmission to eg. HN is done by both authors and users
#voxpelliwhile curation is crowdsourced through voting
tvn joined the channel
#voxpellistuff can be submitted by anyone to IndieNews so in a way it's like HN there, just without the voting part
#tantekvoxpelli: there's no curation of Planets other than the subscription list, which is typically done by hand by the owner / admin(s) of the Planet
#tantekMozilla planet was more about community than topic, so aggregates Mozillians blog posts in general, most which tend to be relevant to web technologies
#aaronpktantek: have you documented why your home page is an h-card with a child h-feed? (vs the other options of top-level h-feed, etc)
nitot joined the channel
#tantekbecause my site is me, ergo top level h-card
#tanteksign of community challenges, when "Content that doesn't fit Planet Drupal:" has to explicitly include " "I Love Drupal!" posts that don’t provide valuable, actionable content to readers. "
#aaronpkyou also have other pages that contain lists of posts, such as http://tantek.com/2015/08, which has no h-feed markup, nor a top-level h-card. is that intentional?
#tantek(I'm curious how many times that happened before someone decided an explicit rule was necessary, and that having such a "shutdown positivity" rule was not worse than the content showing up)
#Loqiarchive in the context of the indieweb refers to date-grouped (often monthly) sets of posts (AKA personal historical archives, a common form of navigation), but can sometimes mean archival copy, a copy of a web page made (often by someone other than the author) at a particular point in time https://indiewebcamp.com/archive
#aaronpka tag feed shouldn't have a top-level h-card like your home page, correct? it is primarily a feed, so the top-level object should be an h-feed?
#voxpelliI think "search" gives too much of a Google vibe – I'm trying to stay away from calling features of a web sites search as far as possible to avoid giving the wrong impression
#voxpelliI actively try to use terms like "filters" and probably "feed" and such rather than search
#aaronpk(you may notice the summary from Loqi on these is leaving something to be desired, which is where I'm actually going with this line of questions)
#tantekother attempts in the past have used things like "channel"
#Loqisnowflake in the context of the indieweb, is typically used to refer in a derogatory way to "snowflake APIs", APIs that are (often silo) website or service provider-specific (unique like snowflakes) rather than an open standard https://indiewebcamp.com/snowflake
#tantekI suppose I could add a rel=feed that linked to the fragement identifier of *just* the primary list of posts on the page
#tantekI wonder if that would help with discovery of posts for readers
#aaronpkI would rather the mf2 data structure have all the information it needs to know where the primary list of posts is, rather than relying on external information from the HTML
#tantekuser adds a URL to a reader to "follow", reader goes to discover the list of posts to from that URL, looks for a top level h-feed, then top level h-entry(s), then rel=feed which if it goes to a local frag ID, then parses that subtree for an h-feed, then h-entry(s)
#tantekinteresting, so you'd like to actively recommend *against* rel-based discovery of content?
#tantek(not questioning, but rather seeking clarification)
#aaronpkit makes it harder to implement when you have to handle both the parsed microformats and also raw HTML
#tantekbecause that has larger ramifications (we could consider that path)
#tantekthis is why the mf2 JSON included rels to start with
#aaronpkfor me, the whole benefit of microformats is that I don't have to think of it as HTML anymore
#tantekso all you needed was the mf2 JSON (the "parsed microformats")
#tantekah, even if you have the rel values, if they are URLs to things in the HTML, you'd have to look at the HTML again?
#tantek*interesting* this is implying that rel values in the mf2 JSON to local things in the page should somehow also provide references to those parsed microformats in the mf2 JSON!
#[kevinmarks]With html the id duplication problem is solved by going to the first in the document, but mf2 parsing doesn't preserve document order, so may add ambiguity
#tantekanyone coming along that wants to see if it is canonical has to go *get* that link and check it out to see what it asserts about itself
#ben_thatmustbemeyes, i know that, how do you refer to the data of that version though, thats still content that is parsable and referencable, just not trustworthy information
#[kevinmarks]You can assert that the current page is non-canonical with a rel=canonical link
#tanteknah, it's pointless to refer to it since it's not trustworthy information
#tantekall you can refer to is what is trustable, which is that it's a link, nothing more
#tantekKevinMarks: the dup id problem can be solved at parse time, since the document *is* parsed in document order even if the parsed result isn't guaranteed to be so (yet the algorithm pretty sure specifies that order)
#ben_thatmustbeme<div class="h-cite"><a class="u-url u-uid" href="twitter.com/t/00000000101010101">permalink</a><span class="e-content">I believe in creationism<span></div>
#ben_thatmustbemeIf i post this, how do you comment on it and call me out as a liar?
#ben_thatmustbemeany attempt to parse it says that it doesn't exist as the url is gone
#aaronpkI don't understand the problem? That post would have a URL on your site, so someone would just reply to that URL
#ben_thatmustbemejust because its not validated as having being correct (verifying the source) does not mean it isn't something useful
#ben_thatmustbemenot so much of how you comment on it, but how do you cite it
#[kevinmarks]Page with id was the original permalink model before posts got standalone pages
#[kevinmarks]Tantek: so that is an extra constraint for parsers, that first id wins?
#ben_thatmustbemeoh, i hadn't though of two IDs, that gets even messier
#ben_thatmustbemewhat i was trying to get at is that a syndicated copy should have and ID of itself and and ID of what it is claiming to be a copy of, whatever that ID of the syndicated copy is, thats what you should be parsing the id from html into
#tantekKevinMarks: yes, mf2 parsers should only look at first instance of any "id" attribute hence doing de-duping at parse time for id
#KartikPrabhuben_thatmustbeme: that example makes little sense, in that if you wanted to lie you could lie in the markup too ;)
#ben_thatmustbemeKartikPrabhu: save youself some time and ignore my whole convo section
#KartikPrabhuben_thatmustbeme: not to worry I am good at speedy parsing of relevant content ;)
#misa__well I'm working on a website related to cooking and gastronomy, it's going to be kind of a blog/recipe/discussion website, still working on the format
#ben_thatmustbemeaaronpk: also noticed your comment about JF2 ealier, what was it you were referring to specifically? the "refs:" ?
#snarfed(heh, sorry, i see that was already discussed)
#bearyea, I figure there will be some adjustments :)
j12t joined the channel
#aaronpkmaybe we should have explicitly stated goals with them that are different
#aaronpke.g. news.indiewebcamp.com is intended to be explicit submissions, not aggregated like a planet
#bearI feel that planet isn't the right term for indieweb.news to be honest - but I also have not staked out any firm position
#snarfedi was actually just thinking about the names/domains, even before i knew what they did (and definitely before i got anywhere near reading text goals anywhere)
#bearI haven't defined it yet gRegorLove precisely because right now it's just a way for me to explore some python code for displaying different posts, mentions, comments, etc
#bearone of my thoughts was that it would be a self-refreshing list of items someone is interested in, with the default being a list of activity from the indieweb community
#bearnot just posts from indieweb community members
#calumryantantek: I’m here :) I’ll try and get Barry to join in next time I see him and suggest this
#ikomihello, I was referred here by wolftune from snowdrift.coop, I have a question regarding html meta tags and was wondering if I could ask for opinions here
#tantekany idea how Barry got the idea of using old vcard microformats?
#ikomiI'm helping out at snowdrift.coop (a site focused on free/libre/open works) and looking into adding meta tags for better search/social visibility. Specifically considering opengraph tags and twitter cards. I noticed the IndieWebCamp website has opengraph tags, is this a "standard" and have you noticed any improvements in visibility and such?
#Loqimicroformats are extensions to HTML for marking up people, organizations, events, locations, blog posts, products, reviews, resumes, recipes etc https://indiewebcamp.com/microformats
#ikomiwe have a meta description tag for the 1-liner that appears in search engine results (though if we didn't add it some search engines would just take the body text for their description), so looking if anything else would be useful
#ikomitantek: okay, ty for the recommendation on microformats :)
#tantekikomi: exactly - taking the body text for description is *much* better because then you can just make sure your body text is up to date!
#ikomitantek: true. that works best if the first few lines of the body text contain the relevant keywords or does it not matter?
#tanteksearch engine keyword heuristics have become too complex to bother trying to jam/pack etc.
#tantekjust make sure your content has relevant prose with good valid semantic HTML markup
#ikomitantek: ty … and further to the body text question, is taking the body text common behaviour for all major search engines? I see a lot of large sites (index page) have no description in search results
#LoqiMetadata, specifically "descriptive metadata", is an umbrella term for all the different ways data (content) can be marked up or organized to facilitate machine-readability https://indiewebcamp.com/metadata
#ikomitantek: okay. sorry, one more question, is the current version of microformats w3c valid? just looking at rel=tag for links, the copyright says they intend to submit to standards body, is it still wip?
#tantekah - that should be updated, because rel=tag *was* submitted and incorporated into HTML5
#ikomitantek: great, ty … so microformats is a significant improvement worth incorporating, but not a "must"? will let the group know and see about incorporating it. ty again!
#tantekikomi: thank you for the question about rel-tag, I have updated the specification accordingly to note that rel-tag has been incorporated into HTML5: http://microformats.org/wiki/rel-tag
#ikomitantek: does it have any effect on accessibility as well or do readers prefer entirely different specifications?
#tantekikomi some readers use microformats. for *screen* readers you have to check each one individually as they all differ, however they do tend to make use of ARIA attributes.
#ikomitantek: and np (sorry for all the questions!)
#aaronpkas long as you don't mind the text of the link being rendered when the comment is displayed
tantek and yoowho joined the channel
#yoowhoi want to thank the san francisco indie web meet folks last week for their feedback helping me with creating a new homepage look http://moshecohen.net/
#tantekwelcome yoowho and great to meet you last week!
#tantekother folks you met last week: benwerd, KevinMarks, erinjo
#petermolnar"Today, we’re launching a new feature for Svbtle members: it’s a promise that the Svbtle service and your published content will remain available on the web forever."
#aaronpktantek: there's some mentions of "indieweb" at that page
#kylewmwow, that Svbtle announcement is cool. i think the most forcefully i've seen that sort of statement made
#aaronpkIt's nice, but I'm not sure how much I can believe it
#aaronpkThey did acknowledge "If Svbtle, its parent corporation, or any affiliated entities are acquired, purchased, or taken control of by a third party in a way that would negatively impact the service, we will do everything in our power to ensure that the above two promises endure as part of any legal agreements into which we enter."
#aaronpkbut it's hard to actually control what happens in that situation
#kylewmhmm, but then fine print: c. "Forever" means until the HTML "web" is no longer generally accessible or until Svbtle becomes financially insolvent (which we intend to avoid "
#kylewmI intentionally cropped out some context there :P but it's a pretty big hedge
#aaronpkin particular, "...we would work very closely with [archive.org] to archive all data. And perhaps even give them the domain name."
#aaronpkand "I'm working on a trust that will be created in the event of my death (or the company's death) that can keep the servers running for a very long time to come, even with no paying customers."
#snarfed1does known not support video posse yet? i know benwerd has lots of experience and opinions on video handling, maybe he's waiting until he feels like he can do it right?
#tantekthis is why it's important to push forward with what you want on your site, as hacky as it may be. show a broader set of people what is possible.