#tantek!tell Zegnat I like this new "get it done by Friday" policy for HWC pages / venues. Anything posted by Friday 17:00 Pacific Time I'll add to the Mozilla announcement for the next Monday, but otherwise no promises. In addition I think /next-hwc should always point to the next "regular" Wednesday evening HWC. Like usual fortnightly or a reliable regular city (e.g. Portland).
#eli_oatI think you are right about their endpoing not limiting characters. I've been scrolling through manton's timeline, and it seems like the truncation is happening as a secondary process.
tantek, ben_thatmustbeme, deathrow1, barpthewire, AngeloGladding, j12t, sebsel, KevinMarks, [miklb] and KevinMarks_ joined the channel
#ZegnatKevinMarks, you were there for the first Virtual HWC right? On Hangouts? Could you add a point about Hangouts to /Virtual_HWC ?
#LoqiZegnat: tantek left you a message 15 hours, 21 minutes ago: I like this new "get it done by Friday" policy for HWC pages / venues. Anything posted by Friday 17:00 Pacific Time I'll add to the Mozilla announcement for the next Monday, but otherwise no promises. In addition I think /next-hwc should always point to the next "regular" Wednesday evening HWC. Like usual fortnightly or a reliable regular city (e.g. Portland).
#GWGI have a mf2 parsing issue I need brainstorming help on.
#GWGMany WordPress themes include mf1 entry-content or entry-summary around the post content block. Many third party plugins add to the content block dynamically, as it is the only way to dynamically add things like metadata, ads, etc to WordPress posts.
#GWGThis is the only way I can add things to posts as well, which results in properties nested inside e-content, such as reply-contexts. I have modified themes to work in such a way that this isn't an issue, but I can't modify every theme. I'm trying to think of an alternative solution.
#GWGThe only way I can think of is something in the markup that tells the parser to ignore mf1 and only parse mf2.
#GWGThen it would ignore the entry-content in favor of the e-content.
#ZegnatTo be fair, if plugins can only put stuff inside entry-content I imagine a lot of plugins exist that add stuff that isn’t supposed to be content either. Which then means it is a bug on the themes to have entry-content in that location in the first place :/ But I see how that would be hard to fix.
#sknebelif it is mf2 parsing (as in, the root element parsed is an h-entry) entry-content should be ignored. if it is mf1 parsing, then e-content doesn't do anything
#sknebelbut I guess the issue is that all templates have "hentry" and you can't force it to add "h-entry"?
#ZegnatSo, yes, GWG, adding h-entry next to the existing hentry (which you probably want to keep for possible CSS reasons) should do exactly what you want and ignore entry-content
#ZegnatGWG, you are right, though I have never seen it. You might want to add to https://indieweb.org/like if you have a usecase for liking non-URLs.
#ZegnatNeed to finish the dishes, then I’ll have another look at the parser, brb
tommorris, KartikPrabhu and gRegorLove joined the channel
#gRegorLoveHowdy. I saw talk of php-mf2 backcompat?
#sknebelgood morning gRegorLove. For some reason, semantic-linkback (WP plugin) uses mf1 when available, but on php.microformats.io it parses correctly (preferring the also-existing mf2, as it should)
#GWGgRegorLove: Yes. I built a debugger function that echos it to the screen to check URLs without having to actually mention something
j12t joined the channel
#gRegorLoveOnly thing I can think is that Mf2\Parser is included elsewhere before this plugin's files load, so the check at the beginning fails to include the php-mf2 included with SL
#GWGThat is possible. Post Kinds also uses it. I can update that version and check.
#GWGWordpress is horrible with dependency management
#Zegnatin my experience, refactoring is a lot of moving bits and bobs around, creating new files whenever you think it is better. But it doesn’t sound as bad as “increasing complexity”
#[miklb]interesting. I’ve always thought refactor meant to simplify and clean up.
#GWG[miklb]: Sometimes it is about making it easier to work with
#[miklb]sure. I’m just asking general questions. Not questioning decisions.
#ZegnatA lot of refactoring I did at my previous job involved writing new libraries next to legacy code. With all the extra files and documentation it felt like I was making the project more complex. But overall it became easier to find where code was.
#[miklb]but I don’t think of making easier to work with increasing complexity ¯\_(ツ)_/¯
#ZegnatI expect GWG referred to the same sort of thing when he said increasing complexity.
#ZegnatThe number of people who equal “more files” to “more complexity” is staggering, in my experience.
#GWGIt is hard to have a plugin try and do what that plugin does. It's very simple and needs more.
#Zegnatsknebel, re: vouch, I also tried to work rel scanning into my vouch flow. If you say trusted.example.com linked to you, my backend will verify that said link does not have nofollow on it.
#sknebelhm, didn't we have proposals for signed webmentions somewhere?
#[miklb]Zegnat, I believe WP adds the rel=“nofollow”
#ZegnatI’d rather keep it general, sknebel, keep mf2 parsing out of my vouch verification
#Zegnat[miklb], I seem to recall that it does. I think most CMS will. It is people pulling in comments from webmentions on their indie sites that I am uncertain about.
#sknebelZegnat: copyleft is GPL-style, so nothing is copyleft there
#ZegnatOh. My reason for not going GPL-style is virility. If you want the microformat and indieweb specs to be pickedup everywhere and parsers in the indieweb repo to be leading implementations, no reason to force users into specific licensing. That’s why I would like to see more CC0.
#schmartypossibly wrong or confusing but i am going to sit with it for a bit
#schmartyhaha, even my explanation just now was confusing. i meant that unlike a "u-in-reply-to h-cite", it's just an "h-cite". there's still a "u-url" inside w/ the url of the cite.
[eddie] joined the channel
#[eddie]schmarty: That sounds pretty cool! I don’t fully understand what you are talking about though ? Do you have an example?
#Loqi[Marty McGuire] Thanks to our guest Jeffrey Toppe for showing us the money in this week’s We Have to Ask Podcast! We Have to Ask PodcastWe Have to Ask Podca...
KartikPrabhu joined the channel
#schmartywelp, i already hate loqi's previews for them. :|
#[eddie]ohhh So your post is the text at the top and the embed below is the link preview?
#schmartyyep, and the link previews can go anywhere in a post, they're denoted by a URL on its own line.
#[eddie]ohhhh, that was my next question. So the link preview is not actually extracted from the text above, it’s specifically you putting a URL and nothing else that it knows you want to “embed” that post
#[eddie]I was wondering how you kept un-wanted previews from showing up when you mentioned something off-hand ?
#[eddie]But that makes sense. Almost like a Twitter card embed
#schmarty[eddie]: yep, i chose that because i think i'd be unlikely to do it by accident
#schmartyyeah, it brings posting to my own site much more inline with how i post to twitter or FB.
#Loqischmarty has 4 karma in this channel (16 overall)
#schmartyhaha, thanks! i have been letting my site improvements drag a bit recently and was glad to get back to it before IWS next weekend.
#schmartyi need to reload my itches for my site and tools like /Screech into my head and try to prioritize them
[miklb] joined the channel
#[miklb]schmarty what did you use to parse the content for the preview?
eli_oat joined the channel
#schmartyin general, the ruby microformats gem. i have special cases for soundcloud and youtube (to embed a player) and twitter (using XRay as a service). i fall back to simply displaying a link if none of those produce something usable.
#LoqiXRay is an open source API that returns structured data for a URL by parsing microformats and following other indieweb algorithms, and is part of the p3k suite of applications https://indieweb.org/XRay
gRegorLove joined the channel
#tantekschmarty - yes, you want to make sure that any link-preview you put in your posts, doesn't show up when someone else shows a link-preview of YOUR post.
#tanteke.g. when Loqi does a "link-preview" of something here in IRC like you saw :)