#dev 2017-06-17

2017-06-17 UTC
kline joined the channel
#
tantek.com
edited /2017/Leaders (+86) "/* Schedule */ lunch after, then afternoon activities outside"
(view diff)
#
tantek.com
edited /next-hwc (+0) "redirect to page that exists, for the next regular one"
(view diff)
#
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).
#
Loqi
Ok, I'll tell them that when I see them next
#
tantek.com
edited /events/2017-06-28-homebrew-website-club (+80) "move Virtual to West Europe section since that's its timezone alignment"
(view diff)
eli_oat joined the channel
#
eli_oat
oh, it is u-like-of, isn't it, not just like-of?!
#
tantek
right
#
tantek
for the mf2 property: microformats.org/wiki/h-entry
#
eli_oat
hmmm, I just double checked and I seem to be applying the right class in my markup
#
eli_oat
I'm trying to determine why my posts don't always appear in the woodwind
#
eli_oat
Would including an h-card within the h-entry throw things off?
#
tantek
should not be a problem, especially since that's a common way to indicate /authorship !
#
eli_oat
hmmm, intriguing. I will continue to dig in. Thanks tantek
#
tantek
I just checked that pin13 link eli_oat and it seems fine - what's "not working" ?
#
eli_oat
just that all of my title-less posts come up blank on woodwind
#
tantek
ohh interesting
#
tantek
I'm not sure if Woodwind supports and shows /like posts
#
eli_oat
that may very well be the issue, :P
#
tantek
however even if that is true, it highlights a need for fallbacks
#
tantek
which we have discussed in part in the past, just never fully formalized
#
tantek
there is a bit on /like about POSSEing and plain text design
#
tantek
e.g. I show and markup a plain text fallback as "summary
#
eli_oat
oh, interesting
#
eli_oat
I wonder if that is how your posts are able to circumvent micro.blog's character limit?
#
tantek
and it's linked in the HTML version if they click through: http://tantek.com/2014/365/f2
#
Loqi
[Tantek Çelik] likes Aaron Parecki's post
#
tantek
interesting, had no idea I was breaking any micro.blog limits :)
#
eli_oat
by a lot sometimes!
#
Loqi
[Tantek Çelik] a jpg. a jpg. a jpg. a jpg. a jpg. a jpg. a jpg. a jpg. a jpg. ? #sunrise vs #fog on 4 summits before 6:40, then #NPSF #hillsforbreakfast. 1552' in 4.7mi. 51d til #TSFM2017, my longest race so far @THESFMARATHON. Photos from / by / of: 1. Twin Pe... https://igx.4sqi.net/img/general/original/476_XKESZJ1fzJwrMcsMWNR82TQhNpWIQ1nhzoIK2n9V0NE.jpg
#
eli_oat
(no way to link directly to it on micro.blog, it seems)
#
tantek
I think their micro.pub endpoint also has no length limit
#
eli_oat
yeah, I've been unable to get my endpoint to play nice with micro.blog
#
eli_oat
Or, I guess, I have been unable to get my endpoint to play nicely with their client would be more accurate
#
eli_oat
but my endpoint works on a hopes and dreams more than anything else, because I have no real clue what I'm doing there :P
#
tantek
I mean their endpoint
#
eli_oat
I 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
#
vanderven.se martijn
edited /2017/Leaders (+918) "/* HWC Organizing */ more notes, thoughts, and expressing interest"
(view diff)
KevinMarks joined the channel
#
www.svenknebel.de
edited /2017/Leaders (-340) "/* Discussion Channels */ now leaning towards +1"
(view diff)
#
sknebel
!tell aaronpk: I wrote some notes about the automatic wiki login: https://indieweb.org/non-interactive_IndieAuth#implementation_in_Kaja
#
Loqi
Ok, I'll tell them that when I see them next
j12t joined the channel
#
vanderven.se martijn
edited /Portland (-4) "Portland is once a month."
(view diff)
#
vanderven.se martijn
edited /Homebrew_Website_Club (+31) "/* Portland */ Link to scheduled dates"
(view diff)
[cleverdevil], [miklb] and KevinMarks joined the channel
j12t joined the channel
#
vanderven.se martijn
edited /2017/Leaders (+373) "/* Events Organizing */ More thoughts"
(view diff)
KevinMarks, KartikPrabhu, j12t, KevinMarks_ and ejd joined the channel
#
www.svenknebel.de
edited /Virtual_HWC (+606) "notes about tested chat tools"
(view diff)
#
vanderven.se martijn
edited /Virtual_HWC (+43) "/* talky */ Screen sharing is great for demos"
(view diff)
#
Zegnat
KevinMarks, you were there for the first Virtual HWC right? On Hangouts? Could you add a point about Hangouts to /Virtual_HWC ?
#
Loqi
Zegnat: 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).
[kevinmarks] and j12t joined the channel
#
alanpearce.uk
created /User:Alanpearce.uk (+64) "Add h-card with name"
(view diff)
KevinMarks joined the channel
#
GWG
I have a mf2 parsing issue I need brainstorming help on.
#
GWG
Many 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.
#
GWG
This 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.
#
alanpearce.uk
edited /User:Alanpearce.uk (+468) "Add Current Setup and first Itch"
(view diff)
[miklb] joined the channel
#
GWG
[miklb]: Want to weigh in on this?
#
sknebel
GWG: so you can not influence the outer markup, since it is part of the theme, correct?
#
GWG
Exactly
#
GWG
In my theme, I can address that. But not in 100% of themes.
#
[miklb]
I haven’t given it much thought, but should considering what I’m working on.
#
[miklb]
but ultimately, I’m not sure ever going to fully solve it.
#
GWG
I wonder if this is a microformats parsing question.
#
Zegnat
It isn’t a limit of parsing though, is it?
#
sknebel
since value-class-pattern doesn't apply for e- properties, I have no idea how you'd hide stuff inside e-content
#
GWG
If you have an h-cite nested inside e-content by necessity...
#
Zegnat
No reason you can’t have .u-in-reply-to within .e-content
#
Zegnat
I think I do that myself, actually
#
GWG
Except for the display issues.
#
GWG
I have to put a full reply-context in there.
#
GWG
It parses correctly, but the parsed content html and plaintext also includes it.
#
Zegnat
Yes, people who parse your site and want to display your comment might have issues. That’s not really inherit to mf2 parsing
#
GWG
I meant, is there a way to mark it up that it wouldn't be an issue?
#
GWG
Without moving the in-reply-to outside of the e-content?
#
GWG
Hard issue there.
#
sknebel
I can't think of a way
#
Zegnat
You can hide it, but then people reading the wordpress blog might not understand it to be a reply
#
Zegnat
<data class="u-in-reply-to" value="URL">My reply right here!</data>
#
GWG
I'm talking about hiding it only from the parser, not visually.
#
GWG
That is the issue.
#
Zegnat
There isn’t unless we can use VCP :(
#
GWG
The only way I can think of is something in the markup that tells the parser to ignore mf1 and only parse mf2.
#
GWG
Then it would ignore the entry-content in favor of the e-content.
#
Zegnat
To 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.
#
sknebel
if 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
#
sknebel
but I guess the issue is that all templates have "hentry" and you can't force it to add "h-entry"?
#
[miklb]
that can be filtered I believe
#
GWG
This is going to be a significant usability issue in the long-term for onboarding new users.
#
GWG
sknebel: You can, because that property is filterable.
#
sknebel
if it has "h-entry" and i'm reading the parsing algo right, entry-content should be totally ignored
#
Zegnat
I confirm sknebel’s reading of the algo.
#
[miklb]
that would be nice to confirm
#
Zegnat
On an element with .h-entry.hentry (both), the .hentry must be ignored and “backcompat properties” are ignored as well
#
Zegnat
So, 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
#
GWG
Hmm...
#
GWG
Time for a new wordpress-uf2 then
#
GWG
The auto-enhancer.
#
[miklb]
GWG, that’s in the indieweb repo, yes?
#
GWG
[miklb]: No. But pfefferle isn't actively maintaining it.
#
GWG
He authorized me as a secondary maintainer. It's years old and could use a serious refresh.
#
[miklb]
oh, I thought I read he transferred it.
#
Zegnat
Oh. sknebel beat me to it...
#
[miklb]
either way, wondering if working on that would give more bang for the buck before IWS
#
Zegnat
GWG, my example shows separate e-content and u-in-reply-to packed within entry-content
#
Zegnat
PHP, Go, Python, and Ruby, all the parsers agree on the interpretation! (sknebel, good news, no bugs there :p)
#
sknebel
oh, apropos, maybe the comparison site we talked aobut would be a nice IWS hackday project?
#
GWG
That is interesting
#
GWG
pin13.net/mf2 when I try that shows correctly, but Semantic Linkbacks doesn't...even though they both use php-mf2
#
Zegnat
Is SL on the latest version?
#
sknebel
current version?
#
Zegnat
That could be a fun hackday project sknebel! Something you would want to work on together?
eli_oat joined the channel
#
GWG
It's maybe a week or two back.
#
GWG
Will update.
#
Zegnat
Wasn’t there an issue filed somewhere for doing comparisons?
#
Loqi
[veganstraightedge] #11 Add /compare
#
GWG
Updated. Didn't help.
#
Zegnat
That was it, thanks sknebel
#
Zegnat
bookmarks issue
#
Zegnat
GWG, that’s really weird :o
j12t joined the channel
#
GWG
And that compare site showed all parsers getting it right.
#
GWG
Except it still isn't parsing it correctly.
#
sknebel
the code in semantic-linkbacks *looks* right
#
sknebel
doesn't it see the content attribute and falls back to name?
#
GWG
I'm looking at the output in the debugger I installed to output the parsed version to the screen
#
sknebel
"isset( $node[ $key ][0])" - is that true for the "content":[{"html":..., "value":...}] ?
#
GWG
But the output from php-mf2 is coming in differently.
#
GWG
Here it is.
#
GWG
If I turn off support for parsing classic microformats markup, it renders correctly.
#
[miklb]
I thought the parser should do that automatically
#
sknebel
is that something extra, or is that backcompat?
#
Loqi
[gRegorLove] #111 Improve backcompat parsing
#
[miklb]
ah, so that classic mf option is deprecated now?
#
GWG
No.
#
GWG
It's on by default
#
[miklb]
then I’m confused
#
GWG
I have to have it ignore classic microformats to parse correctly.
#
[miklb]
I can’t find that option
KevinMarks joined the channel
#
[miklb]
oh, I thought you meant it was an option in Semantic Linkbacks
#
GWG
No.
#
GWG
I'm filing a proposal.
#
sknebel
the parser code looks right, as in having that only as a switch for backcompat
#
sknebel
GWG, what exactly are you trying to parse?
#
GWG
WordPress sites.
#
sknebel
specific example I can look at?
#
Zegnat
https://github.com/indieweb/php-mf2/blob/master/Mf2/Parser.php#L1267 - looks right too, if the current root is an mf2 class it should not apply bc parsing
#
sknebel
Zegnat: exactly
#
Zegnat
can’t really read much more code, jumping around on phone is not working very well :p
#
GWG
I've introduced a temporary situation...a stock WordPress theme, and wrapping the appropriate information in e-content inside entry-content.
#
GWG
h-entry is a top level item.
#
sknebel
same element as the hentry?
#
GWG
sknebel: Correct.
#
sknebel
and php.microformats.io *also* has backcompat enabled
#
[miklb]
and it parsed that scenario correctly, e-content inside entry-content inside wrapper with h-entry & hentry right?
#
Zegnat
if php.microformats.io has it enabled and runs the same version as SemanticLinkback then it must be the HTML mark-up...
#
sknebel
GWG, can you post the HTML as a gist or something?
#
Zegnat
Or put the entire HTML in php.microformats.io
#
GWG
This is the page I used. I changed the theme to a stock one and enabled wordpress-uf2 to auto-add e-content.
#
GWG
pin13.net parses content correctly. SL doesn't. Both using the same parser.
#
Zegnat
I was just going to say, that parses correctly on php.microformats.io … really odd
#
GWG
There is something I'm missing
#
GWG
But it has inspired me to update wordpress-uf2.
#
GWG
It's been on my list for ages
#
GWG
Zegnat: If I toggle the classic to false, it does it correctly
#
Zegnat
You want u-like-of there btw, not p-like-of as it has now
#
[miklb]
GWG I just forked it myself. if nothing else, will help me better understand for my theme. Spinning up a test site for it now
#
Zegnat
But that prefix change doesn’t fix your issue of course
#
GWG
Zegnat: You can like things without a URL. But that's another issue.
#
GWG
I will make a note of that. I can add the logic to swap between them.
#
sknebel
installs php
#
Zegnat
GWG, 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.
#
Zegnat
Need to finish the dishes, then I’ll have another look at the parser, brb
tommorris, KartikPrabhu and gRegorLove joined the channel
#
gRegorLove
Howdy. I saw talk of php-mf2 backcompat?
#
sknebel
good 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)
#
[miklb]
both use php-mf2
#
gRegorLove
Ah. Which particular fork / commit on github are we looking at for semantic linkbacks?
#
gRegorLove
Or is this GWG's local dev?
#
GWG
gRegorLove: I'm looking at the Github master version
#
[miklb]
I think with master
#
GWG
Same thing happened on stable though.
#
gRegorLove
pfefferle or acegiak's?
#
gRegorLove
Is there a gist of what SL is parsing?
#
GWG
pfefferle's.
#
GWG
gRegorLove: I'm testing the theory with this page. https://tiny.n9n.us/2016/09/11/like-of-hydrox/
#
GWG
I modded it to embed e-content inside entry-content to see how classic backcompat worked.
#
gRegorLove
What is SL retruning that it shouldn't, though?
#
GWG
gRegorLove: It was parsing entry-content instead of e-content.
#
GWG
Giving the whole context as a result.
#
GWG
I just started working on updates to wordpress-uf2.
#
GWG
I've decided to move that up ahead of other things. Might be able to write it more effectively. It's been idle for 2 years.
#
GWG
[miklb]: Watch the dev branch in the current repo
#
[miklb]
yeah, I forked from pfefferle’s repo so I’ll keep an eye out.
#
GWG
[miklb]: I'm in his repo.
#
GWG
I have the ability to add branches, but merging to the master branch requires review
#
GWG
I thought he gave me that permission.
#
GWG
But I'll worry about that when I have something worth merging.
#
GWG
I just gave it a proper README, language file, etc. The same structure we use for all the plugins. I've matched him on it for a while now.
#
GWG
gRegorLove: 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
#
gRegorLove
Only 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
#
GWG
That is possible. Post Kinds also uses it. I can update that version and check.
#
GWG
Wordpress is horrible with dependency management
#
gRegorLove
Yeah, it's frustrating sometimes
#
[miklb]
yeah, but you are getting a shiny new js editor…
#
sknebel
so my horribly hacked carcass of that file finds the right content
#
sknebel
to check if it uses the right parser you temporary could rename the class to something else, to make sure you get the right one?
#
gRegorLove
Wonder if php-mf2 should have a version-check method
#
[miklb]
what is uf2
#
Loqi
It looks like we don't have a page for "uf2" yet. Would you like to create it?
#
gRegorLove
You mean the WordPress plugin?
#
[miklb]
there is a plugin called wordpress-uf2
#
gRegorLove
uf2 should probably point to /microformats
#
[miklb]
what does uf2 mean
#
[miklb]
how would someone new to IndieWeb know to look for a plugin that adds “uf2”. Just thinking through the name
#
[miklb]
also realizes it can eventually be added to the IW plugin loader, but still.
#
sknebel
gRegorLove: version-check method sounds like a good idea for these situations
#
gRegorLove
uf2 as a plugin name is probably sub-optimal
#
loqi.me
created /uf2 (+25) "prompted by [miklb] and dfn added by gRegorLove"
(view diff)
#
gRegorLove
uf2 is just a shorthand, "u" being easier to type than μf2
#
gRegorLove
What is WordPress uf2?
#
Loqi
It looks like we don't have a page for "WordPress uf2" yet. Would you like to create it?
#
sknebel
although "mf2" is the way more common styling
#
sknebel
and really, letters in plugin-names aren't expensive
#
gRegorLove
Agreed. uf2 seems overly techy/nerdy
#
sknebel
"wordpress-plugin-that-injects-mf2-into-pages" would be easier to understand :P
#
gRegorLove
WordPress uf2 is a [[WordPress]] plugin to add microformats2 to your WordPress theme https://github.com/pfefferle/wordpress-uf2
#
loqi.me
created /WordPress_uf2 (+155) "prompted by gRegorLove and dfn added by gRegorLove"
(view diff)
#
Loqi
[pfefferle] wordpress-uf2: add microformats2 classes to your WordPress theme
#
[miklb]
wordpress-mf2-theme-helper would be the direction I would go
#
gregorlove.com
edited /WordPress/Plugins (+20) "/* Other Indieweb Plugins */ +WordPress uf2"
(view diff)
#
gregorlove.com
edited /WordPress_uf2 (+7) "link dfn, WordPress template"
(view diff)
j12t joined the channel
#
[miklb]
ok, well I opened an issue to discuss renaming, especially if possibly moving to the indieweb repo and pushed to wp.org repo.
#
gRegorLove
Isssue for php-mf2 version check method: https://github.com/indieweb/php-mf2/issues/133
#
Loqi
[gRegorLove] #133 Consider adding a version check method
#
GWG
I am going to update the plugin and then we can argue the name
#
[miklb]
well. ok then…
#
GWG
The Post Kinds version is 4 months old
#
GWG
That may explain it.
#
gRegorLove
Definitely. 0.3.2 is only weeks old
#
gRegorLove
Which revamped backcompat
gRegorLove_ joined the channel
#
Zegnat
returns
#
Zegnat
Do we have confirmation that it is dependency hell and not a parser bug?
#
GWG
I will push an update. And look at mf2 conflicts between plugins
#
Zegnat
GWG++ for keeping WP rolling :)
#
Loqi
gwg has 10 karma in this channel (233 overall)
#
sknebel
Zegnat, did you implement actual vouch logic, or "just" the data collection for it?
#
sknebel
(in your new webmention endpoint)
#
Zegnat
I have logic, but don’t yet do anything with it because I haven’t thought of how I am going to keep a record of who is allowed to vouch yet
#
Zegnat
I started with a list of hostnames, but that wouldn’t do for sites hosted in subfolders, so I need to change my thinking
#
GWG
Okay. Indieweb Post Kinds php-mf2 updated....problem fixed.
#
Loqi
gwg has 11 karma in this channel (234 overall)
#
Zegnat
(This was an interesting piece of debugging, makes me believe WP dev work should continue in -dev and not be split off to a different channel)
#
[miklb]
imagine though someone editing the wiki at the same time
#
[miklb]
GWG do you provide a markdown and txt version of the README?
#
GWG
[miklb]: In what plugin?
#
GWG
I usually do.
#
[miklb]
I’m doing the readme for pressthis
AngeloGladding joined the channel
#
GWG
[miklb]: I took pfefferle's approach of writing a txt version and using Grunt to convert it
#
[miklb]
for pressthis?
#
GWG
No, in general
#
[miklb]
ah, ok. Not sure a plugin like the press-this needs a grunt task. D
#
GWG
I just run it manually.
#
GWG
I'm increasing the complexity of the uf2 plugin right now.
#
GWG
Dividing the different sections into files so the logic of loading them can be better enhanced.
#
[miklb]
whenever I read “increasing complexity” I get itchy ?
#
Zegnat
s/increasing complexity/refactoring/
#
Zegnat
that better, [miklb]?
#
[miklb]
dunno, do they mean the same thing?
#
Zegnat
in 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.
#
Zegnat
A 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 ¯\_(ツ)_/¯
#
Zegnat
I expect GWG referred to the same sort of thing when he said increasing complexity.
#
GWG
Basically, that's it
#
Zegnat
The number of people who equal “more files” to “more complexity” is staggering, in my experience.
#
GWG
It is hard to have a plugin try and do what that plugin does. It's very simple and needs more.
#
Zegnat
sknebel, 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.
#
sknebel
Zegnat: interesting
#
Zegnat
So people adding rel="nofollow" to dynamic content like comments will help keep vouches spam free :)
#
Zegnat
Someone who commented to a blog I trust can’t suddenly pass my vouch by claiming the blog linked to them.
#
Zegnat
Though I am not sure if Indieweb comment displayers add rel="nofollow". Need to do more research on that.
#
sknebel
for indieweb sites, it makes sense to mf2-parse and check sites that way. everything that's not a property or in the content can be ignored
#
sknebel
of course, that's another step to do
#
sknebel
hm, didn't we have proposals for signed webmentions somewhere?
#
[miklb]
Zegnat, I believe WP adds the rel=“nofollow”
#
Zegnat
I’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.
#
sknebel
what is nofollow?
#
Loqi
nofollow is a rel value meant to stop search engines imputing endorsement from a link https://indieweb.org/nofollow
#
sknebel
^^^ another example of a vouch implementation on there
#
Zegnat
And I thought I was being original! Oh well.
#
Zegnat
Time for me to sleep. Have a good one all!
#
sknebel
good night!
#
Loqi
laila tov!
#
[miklb]
so what is the argument for code in the indieweb repo to not be copyleft?
#
Zegnat
[miklb], what is not copyleft, almost everything is open-source, though there is https://github.com/indieweb/wiki/issues/39 to look at
#
Loqi
[Zegnat] #39 Normalise licensing for projects in the IndieWeb GitHub org.
#
Zegnat
just closes IRC now before he keeps idling
#
sknebel
Zegnat: copyleft is GPL-style, so nothing is copyleft there
#
Zegnat
Oh. 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.
#
Zegnat
started reading on phone
#
Zegnat
has a problem
#
sknebel
Zegnat: go sleep
#
sknebel
Zegnat: sudo go sleep
#
[miklb]
Is ASL not copyleft?
#
[miklb]
not sure why I thought it was
#
sknebel
v2 is compatible with GPLv3 in terms of patent rules, maybe you remembered news about that?
#
[miklb]
quite possibly
#
[miklb]
TIL the MIT license isn’t really the MIT license rather X11 or at least that’s what gnu says.
#
martymcgui.re
edited /User:Martymcgui.re (+25) "/* What Works */ now displaying link previews for some mentions \o/"
(view diff)
#
martymcgui.re
edited /User:Martymcgui.re (+57) "/* My IndieWeb Setup */ Notifications from Pushbullet to Riot + Matrix + Hubot"
(view diff)
tantek joined the channel
#
tantek
how's the devving going #indieweb-dev?
#
tantek
one week til IndieWeb Summit!
#
schmarty
is excited about IWS! is also getting over a head cold. :|
#
tantek
feel better soon!
#
schmarty
thanks! i used some of my downtime today to implement /link-preview display on my site
#
schmarty
i had been abusing in-reply-to because likes/replies/etc would show previews but plain mentions would not.
#
schmarty
so i now auto link preview any URL on its own line, using the same mechanisms i use to show reply contexts.
#
tantek
nice!
#
tantek
and yes, while similar in components / building blocks, a reply-context is very different from a link-preview!
#
schmarty
oops. i just noticed that page has no "display" section.
#
schmarty
i display link previews similarly to reply-contexts, as a nested h-cite.
#
schmarty
with no u-*
#
schmarty
possibly wrong or confusing but i am going to sit with it for a bit
#
schmarty
haha, 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
rofl
#
schmarty
[eddie]: sure! thanks for asking. here's an example where i am talking about a recent ep of my comedy podcast: https://martymcgui.re/2017/06/13/152026/
#
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
#
schmarty
welp, 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?
#
schmarty
yep, 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
#
schmarty
yeah, it brings posting to my own site much more inline with how i post to twitter or FB.
#
[eddie]
Yeah, definitely. That’s awesome ?
#
[eddie]
schmarty++
#
Loqi
schmarty has 4 karma in this channel (16 overall)
#
schmarty
haha, thanks! i have been letting my site improvements drag a bit recently and was glad to get back to it before IWS next weekend.
#
schmarty
i 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
#
schmarty
in 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.
#
[miklb]
what is xray
#
Loqi
XRay 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
#
tantek
schmarty - 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.
#
tantek
e.g. when Loqi does a "link-preview" of something here in IRC like you saw :)
#
schmarty
kind of stumped by that, at the moment.
#
gRegorLove
You could close the p-name before the link preview, but that's not very flexible if you have [content] [link preview] [more content]
#
tantek
schmarty - perhaps take a look at existing examples of link-previews of posts with link-previews inside themselves!
#
tantek
e.g. silo examples, and see how they are doing it
#
tantek
e.g. xray applied to tweet permalinks, where the tweet permalink itself has its own embedded link-preview
#
tantek
perhaps a pattern will emerge