#dev 2018-02-26

2018-02-26 UTC
tantek, KartikPrabhu and [eddie] joined the channel
#
[eddie]
ohhh, that’s true. After nginx, my website does hit my node.js server before being directed either to static files (jekyll) or dynamic files. So I could add my list in to the node.js side of things
#
[eddie]
aaronpk: Do you feel like it was more performant to do it in PHP? or you just liked being able to maintain it there easier
#
aaronpk
I'm sure it's faster in nginx but I like being able to just add stuff to a text file
[miklb] joined the channel
#
[miklb]
could split the difference and put the redirects in a separate nginx .conf file and use an include
#
aaronpk
Sure but still have to reload nginx when you change the file
#
[miklb]
ah, true
#
aaronpk
This way i can do it from my ftp client with no command like access
tantek joined the channel
#
tantek
has anyone opened a new GitHub issue from their site and had the issue closed? and how has the issue closure shown up as backfeed?
#
tantek
is looking at https://github.com/snarfed/bridgy/issues/794 and now going to dig through his webmentions to see if anything special happened
#
Loqi
[tantek] #794 Bridgy Publish to GitHub: support images and hyperlinks
#
tantek
whoever wrote https://commentpara.de/comment/169.htm (I'm guessing someone here?) I noticed after the fact that the links were not hyperlinked in my GitHub issue and updated the post :)
#
Loqi
[Anonymous] I wish that your blog would support hyperlinks :/
#
tantek
drat I had forgotten to enable listening for responses (now enabled)
#
tantek
oh dear now that I enabled Bridgy listening to GitHub for my account, it's sending webmentions of specific comments *to other people* / sites 😂
#
tantek
like these: https://adactio.com/journal/12585#comment56543 (literally that comment and every one after it is from the same GitHub thread that I just happen to be participating in, and that happened to have earlier linked to adactio's post)
#
Loqi
[Wilto] Wilto
#
tantek
adactio is going to wake up to a lot of new comments on his Container Queries article and wondering *why* they are being sent to him (since none of them directly link to his post)
#
tantek
!tell snarfed you may want to take a look at all these comments generated by Bridgy Backfeed from GitHub to adactio's post: https://adactio.com/journal/12585#comment56543 (note that adactio himself is not signed up on Bridgy GItHub, this is a side effect of me opening the issue and linking to adactio's article in the middle of the issue description)
#
Loqi
Ok, I'll tell them that when I see them next
#
Loqi
[Wilto] Wilto
snarfed joined the channel
#
aaronpk
oof whoa
#
aaronpk
Something about that seems not quite right but I can't put my finger on it
radicaledward102 joined the channel
#
tantek
yeah... it's part of the "liberal" original post discovery that Bridgy does on supposedly POSSE copies
#
tantek
which sorta made sense for Twitter since it was usually just *a link* in a tweet, and it's likely the tweet / thread / replies are regarding that link
#
snarfed
yup. makes less sense for github.
#
Loqi
snarfed: tantek left you a message 10 minutes ago: you may want to take a look at all these comments generated by Bridgy Backfeed from GitHub to adactio's post: https://adactio.com/journal/12585#comment56543 (note that adactio himself is not signed up on Bridgy GItHub, this is a side effect of me opening the issue and linking to adactio's article in the middle of the issue description)
#
tantek
but not so much for GitHub issues IMO, especially when there's several links!
radicaledward102 joined the channel
#
tantek.com
edited /Indieweb_Podcast_Club (+79) "update dfn etc per new usage"
(view diff)
renem joined the channel
#
snarfed
also tantek: no, closing issues isn't backfed yet
#
tantek
I don't even know *how* you would backfeed it!
#
snarfed
u-close-of
#
tantek
since GitHub treats it special (not just a reply)
#
snarfed
(kidding)
#
tantek
wonders just how big a can of issue tracking worms has been opened
#
tantek
in many repos, there's an etiquette of "letting" or giving some amount of time for the original issue creator to close the issue
#
tantek
so we actually kinda need this on the *publish* side
#
tantek
since I can *open* issues from my site, I should be able to *close* them too
#
tantek
aaronpk, have you run into this with any of the issues you've POSSEd to GitHub?
#
tantek
or did you just close them in GitHub (and not on your site?)
snarfed joined the channel
#
aaronpk
If you look at a GitHub thread it kind of looks like "closed the issue" is a post itself
#
tantek
right
#
tantek
it's a new response type
#
snarfed
actually before we get into this too far, mind helping me with the OPD question?
#
tantek
sure!
#
snarfed
i agree that we shouldn't consider every link in the issue, like we do with other silo posts
#
aaronpk
Visually it's smaller than a comment but still has properties like an author and a date
#
snarfed
...but then...so do we just require a synd link on the original post?
#
snarfed
or look for specific text like "Originally published at"?
#
snarfed
or...?
#
tantek
snarfed maybe that's a good conservative way to start?
#
snarfed
yeah probably
#
aaronpk
eddie has been doing the opposite
#
tantek
PESOS?
#
aaronpk
Including his canonical url at the end of the github comment but not including the syndication link on his site
#
aaronpk
Via bridgy publish I think
#
aaronpk
Tho in that case bridgy should know the url because it created it
#
tantek
do we treat issue comment OPD differently than issue OPD?
#
snarfed
i'm not even trying to backfeed to issue/PR comments right now
#
tantek
ok cool
#
tantek
snarfed: new idea: use the issue creator's domain as a filter for OPD
#
snarfed
happy to try, but let's figure out issues/PRs first
#
snarfed
tantek: i do
#
tantek
not in the example I cited!
#
snarfed
...and that already failed on my domain, heh. an issue had a link to my home page
#
snarfed
i demote non-author domains to mentions, as opposed to nothing
#
snarfed
could be to nothing for github...but i expect lots of people file issues with links to example posts on their site that *aren't* the issue post
#
snarfed
so i'm inclined to start with requiring synd link
#
aaronpk
I think that only makes sense for the one comment/issue that mentions the link, but not all the follow up comments after
#
snarfed
right, for mentions, definitely
#
aaronpk
For example I would appreciate knowing if a GitHub issue or comment linked to one of my blog posts, but I don't want the whole GitHub thread to end up there
#
tantek
snarfed, re: text like "Originally published at", maybe if the last link in an issue is parenthesized ( http... ), and if it is a non-home-page link to the issue author's domain?
#
tantek
or is that too much work?
snarfed joined the channel
#
tantek
aaronpk, that is a *very* good subtle point that is worth documenting here: https://indieweb.org/GitHub#Backfeed
#
snarfed
basically how normal (non-silo) posts and replies behave
#
snarfed
tantek: yeah even then i'd be curious to see how many parenthesized author links like that are eg bug examples vs original issue posts
#
snarfed
worth a survey!
#
tantek
worth trying and seeing if/when someone complains
#
tantek
at least it won't go from author1 authorizes bridgy -> author2 gets bridgy backfeed
#
snarfed
eh that happens with other silos now too
#
snarfed
just feels a bit more appropriate
#
tantek
yeah especially Twitter. I think your intuition there was correct
tantek, snarfed, AngeloGladding, barpthewire, cweiske and jeremycherfas joined the channel
#
jeremycherfas.net
edited /Indieweb_Podcast_Club (+200) "/* Ask the Indieweb about the Indieweb */ Add thoughts for first episode"
(view diff)
Sumudu, loicm and [markmhendrickso joined the channel
#
[markmhendrickso
Are folks here fans of Docker? And are there any IndieWeb projects that use it? I'm considering it for mine after one request to do so, but I haven't explored it before
#
cweiske
we're using it at work extensively
#
[markmhendrickso
[cweiske] cool, pros and cons in your mind?
#
cweiske
docker makes it easy to get complicated projects running, that have a lot of dependencies
#
cweiske
I personally don't use it on my server because it's overkill
#
cweiske
on a normal server, you use the system package manager to install and update packages. with docker, you lose that advantage because you can't just "apt update && apt upgrade" to get security updates
#
cweiske
you have to get new versions of each of the containers you're running, which is tedious. and unless you're building the containers yourself, you have to wait for the maintainer to update them
#
petermolnar
I still share the view that docker is a very complicated package management system
#
vanderven.se martijn
created /User:Vanderven.se_martijn/h-entry-using-property (+3324) "Start collecting my thoughts and prior art."
(view diff)
#
vanderven.se martijn
edited /User:Vanderven.se_martijn/h-entry-using-property (+158) "Add screenshots for proper documentation of prior art."
(view diff)
#
vanderven.se martijn
edited /User:Vanderven.se_martijn/h-entry-using-property (+243) "Add source links, you know you are going to want them in the future."
(view diff)
#
sknebel
Zegnat: maybe something like "authored-using" would be clearer?
#
Zegnat
Yes, that’s one of the alternatives I was keeping in mind. I should probably add some alternative names to the page
#
Zegnat
sebsel uses “via” rather than “using”. Documenting that now.
#
vanderven.se martijn
edited /User:Vanderven.se_martijn/h-entry-using-property (+1080) "/* Prior Art */ Add example of {{sebsel}}’s HTML, using the word “via”."
(view diff)
#
vanderven.se martijn
edited /User:Vanderven.se_martijn/h-entry-using-property (+1651) "Add some thoughts on the property name"
(view diff)
#
cweiske
aaronpk, indieauth.com tells me that "something went horribly wrong" when signing into webmention.io with http://cweiske.de/, with no more infos. could you check the logs?
leg joined the channel
#
vanderven.se martijn
edited /User:Vanderven.se_martijn/h-entry-using-property (+851) "Document Twitter’s “via” use."
(view diff)
deathrow1 joined the channel
eli_oat joined the channel
#
vanderven.se martijn
edited /User:Vanderven.se_martijn/h-entry-using-property (+112) "/* Twitter */ posting client still available in the API, per {{aaronpk}}"
(view diff)
snarfed joined the channel
#
snarfed
anyone know if microsub has a logo yet?
#
aaronpk
micro*pub* doesn't even have a logo yet
#
aaronpk
cweiske: weird, looks like some internal ruby RestClient error, probably happened when I updated Ruby versions
#
aaronpk
cweiske: just updated the gem and I think that fixed it
#
vanderven.se martijn
edited /User:Vanderven.se_martijn/h-entry-using-property (+535) "Add [[10Centuries]] for API prior-art, with screenshot of a client that exposes the information"
(view diff)
#
vanderven.se martijn
edited /User:Vanderven.se_martijn/h-entry-using-property (+255) "/* Property Name */ client / client_id"
(view diff)
[manton] and [eddie] joined the channel
#
cweiske
aaronpk, still the horribly error when signing into webmention.io
#
aaronpk
"#<NoMethodError: undefined method `code' for nil:NilClass>"
#
aaronpk
it's the RestClient gem trying to retrieve the http status code
#
aaronpk
oh wait I think I know what's going on...
#
aaronpk
try again?
#
snarfed
Zegnat: you've seen how facebook indicates apps used to author posts, right? e.g. https://www.facebook.com/tantek.celik/posts/10103728023138543 , https://www.facebook.com/aaronpk/posts/10103579720238856
#
cweiske
still horrible
#
aaronpk
aha now there's better info
#
aaronpk
it got http 400 back from your server
#
aaronpk
and now same error
#
Zegnat
I am not sure how I completely missed that one, snarfed! Will have to add. Too bad they don’t use any words around it so it will not be helpful in narrowing down a possible property name.
#
snarfed
Zegnat: their API field is 'generator'
#
snarfed
wait sorry no, that's AS1
#
snarfed
the FB API field is 'application'
#
Zegnat
Do you have a source for any AS* specs that may have a name for it, snarfed? That’s definitely prior art!
#
cweiske
aaronpk, still horribly and no 400 error
#
cweiske
(the 400 only occurs when I re-load the indieauth.com error page. my server then says "validating token failed")
#
Zegnat
Interesting stuff snarfed! I have to take a moment’s break from wiki editing but will add that later! Do you happen to have any thoughts on how we could express this best in mf2?
[kevinmarks] joined the channel
#
[kevinmarks]
generator in Atom+RSS, text name +URL
#
Zegnat
been going a bit back and forth between the main channel and dev on this :)
#
Zegnat
I don’t know what I think of the term generator. If I see parsed mf2, I would almost expect the generator to tell me which parser was used, rather than what software was used by the author of an h-entry to create said h-entry.
#
[kevinmarks]
that seems weird to me. generator has been for the original tool as long as I remember
#
[kevinmarks]
I'm pretty sure it showed up as generator in the twitter feeds when they existed'
#
Zegnat
You might be right that generator as a name has been around so long that it makes sense, [kevinmarks]. I’m just always thinking: if I see the mf2 JSON of an h-entry and I read the properties will I instantly understand what a property expresses without going to the wiki?
#
Zegnat
And just not sure if things like client and generator actually do for me.
#
[eddie]
Between client and generator, client definitely feels more natural IMHO. Generator feels like it was created by an AI or algorithm. Client at least feels like it was the tool that was used to create it.
#
[eddie]
That said, I personally would probably push more towards the verb style: via, using, etc.
#
[eddie]
Considering the plain text design that you outlined. It’s how we’ve naturally been describing it
#
Zegnat
Yes, using and via are definitely winning in the text design so far.
#
aaronpk
I think twitter used to say "via"
#
Zegnat
Yes, I have documented Twitter, with screenshot, on the page
#
Zegnat
It used to say via
#
Zegnat
Even though (right now) it is called “source” in the API
#
aaronpk
generator--
#
Loqi
generator has -1 karma
#
aaronpk
generator isn't the same as the app used to post anyway. Generator was always more about the software the server is running
#
Zegnat
They may be the same of course, could easily see WordPress stating you used WordPress to author a post.
#
Zegnat
I think “via” makes sense for things like OYG, but does it make sense for e.g. tanteks usecase of just “BBEdit”? How does that sound to the native English speakers?
#
aaronpk
Sure but generator was around before third party posting apps were common
#
aaronpk
I was always unclear on how BBEdit relates to Tantek's posts but that's because I don't really know what BBEdit is. In 2010 when Tantek had a blackberry I thought it was a blackberry app.
#
Zegnat
It is a text editor for macOS
#
Zegnat
I always thought he had that there because he manually writes the text files behind his posts in there and uploads it over FTP.
#
sknebel
via sort of seems fitting for PESOS services, less so for direct clients. and has conflicts with "found via" (which admittedly isn't as common anymore, and also hasn't been marked up)
#
aaronpk
I think it makes sense for clients too. "via Indigenous" seems natural for example
deathrow1 joined the channel
#
aaronpk
I wouldn't say "via Coda" if I use my ftp editor to create a post directly on my server tho. I just leave it blank.
#
Zegnat
Yeah, that’s the double meaning of via that I also remark on the wiki page sknebel.
#
[eddie]
Yeah, same here. I leave my client_id blank when I create a post by hand.
renem, snarfed, snarfed1 and globbot joined the channel
#
KartikPrabhu
I use "via Bridgy" for webmention replies that come through Bridgy
#
KartikPrabhu
no special markup to discover it though
#
Zegnat
Oh, I never even looked at how people were displaying reactions!
#
Loqi
[Emil Björklund] Emil Björklund replied on Twitter with Thanks for the heads up! Will fix it. Cheers...
snarfed and [kevinmarks] joined the channel
#
[kevinmarks]
via is tricky as it's also used to credit people that you got the link from
#
[kevinmarks]
I think that may be a more common human use than the tool. 'using' is clearer.
#
Loqi
[Kartik Prabhu] Kartik Prabhu liked http://vimeo.com/108650530 because devoid of any dial...
#
[kevinmarks]
atom has rel="via" for that too
snarfed joined the channel
#
[kevinmarks]
it looks like app-generated posts tend to end with "via @[appname]" on twitter now
#
jeremycherfas.net
edited /pnut (-48) "Changed terms of access, and minor gardening"
(view diff)
#
[kevinmarks]
hm, bridgy already uses via [link to site] on POSSEd comments to blogger etc
[colinwalker] and [manton] joined the channel
#
Zegnat
I wonder if some of those app-generated posts using “via” aren’t more like a person saying “found via Person than “posted using Application”. E.g. “via Buzzfeed” may be expressing the former more than the latter, even if the Buzzfeed application was also responsible for the push.
#
Zegnat
Need to collect more examples of such use
#
[kevinmarks]
nuzzel does it too by default
#
KartikPrabhu
examples++
#
Loqi
examples has 2 karma in this channel (5 overall)
#
[kevinmarks]
Nuzzel example "How Trump Conquered Facebook Without Russian Ads - WIRED http://nzzl.us/ju9rNhM via @nuzzel thanks @EmilyDreyfuss" - that's what they prompted me with when I share an article via twitter in their app.
snarfed joined the channel
#
aaronpk
whoa weird timezone bug... something is double-counting the timezone offset
[tantek], KartikPrabhu and [markmhendrickso joined the channel
#
[markmhendrickso
[cweiske] @petermolnar thanks for the input re: docker above!
tantek joined the channel
#
tantek
hey Zegnat remind me of the use case for marking up the 'using' or 'generator' of posts?
#
tantek
and yes the human-to-human use of "via" IMO overrides any use of "via" in formats
#
tantek
or in Twitter's UI
#
tantek
realizing I'm just agreeing with kevinmarks on this
#
tantek
realizes he needs to read the logs here first
#
aaronpk
I never marked up mine because I didn't have a concrete use case for it to be machine readable yet
[tantek] joined the channel
#
tantek
right
#
tantek
surprised there's a microsub bridge before a micropub bridge ;)
#
aaronpk
There is already a Micropub bridge!
#
aaronpk
silo.pub
#
tantek
e.g. site -> webmention -> Bridgy -> micropub -> any micropub server
#
tantek
aaronpk: in Bridgy
#
tantek
Publish specifically
#
snarfed
augh so many arrows
#
aaronpk
I'm not quite sure what that solves
#
snarfed
also i have *not* created a microsub bridge. just a design sketch. :P
#
tantek
my server not having to implement micropub in order to syndicate to a micropub supporting 3rd party service
#
aaronpk
lol whoa so many proxies
#
tantek
snarfed FTFY: indiewebsite --Webmention--> Bridgy Publish --Micropub--> Micropub server
#
snarfed
can't even
#
KartikPrabhu
what's the last micropub server if not you own site?
#
Zegnat
Any other site, an aggregator/planet site possibly, a backup system, Sink.
#
KartikPrabhu
do those things support micropub?
#
aaronpk
or silo.pub 😂
#
tantek
KartikPrabhu: a micropub supporting 3rd party service
#
KartikPrabhu
yeah, as in... examples?
#
KartikPrabhu
aaronpk: lol
#
tantek
KartikPrabhu: what aaronpk said, silo.pub would be a first use-case for that
#
tantek
then whatever silo.pub added support for, Bridgy Publish would be able to plug into
#
KartikPrabhu
then one would just use silo.pub instead of bridgy to silo.pub
#
tantek
without having to implement yet another proprietary API
#
tantek
KartikPrabhu: no, silo.pub expects this:
#
tantek
indiewebsite --Micropub--> silo.pub --SnowflakeAPI--> proprietary service
#
Zegnat
Oh, interesting, getting an TLS warning on silo.pub
#
KartikPrabhu
right, so you want to sub in webmention for micropub
#
KartikPrabhu
that is whole lot of overloading of webmention and bridgying of things
#
tantek
KartikPrabhu: I can combine the two into one longer flow diagram if it helps :)
#
snarfed
(somehow my microsub post generated a micropub discussion?! ces't la vie?)
#
tantek
KartikPrabhu: Bridgy Publish already overloads webmention that way, no new overloading
#
tantek
and Bridgy Publish is already adding one proprietary publish API at a time, if it added Micropub as a publish "target" then it reaches everything silo.pub already supports publishing to
#
KartikPrabhu
yeah I know, and I don't like that overloading either
#
snarfed
me neither
#
tantek
snarfed: didn't you invent that overloading in the first place?!?
#
snarfed
nobody's perfect
#
tantek
I remember thinking it was "weird", but then seemed to fit the need so well!
#
snarfed
yeah it works badly in theory but well in practice
#
tantek
I think it was a testament to the reusability of Webmention as a building block, beyond the original use-cases that the designers/developers envisioned
#
tantek
*is a testament
#
tantek
BTW this is why *building blocks*, not "API stacks"
#
snarfed
this bridgy->silo.pub idea may also be good in theory but not in practice, since hosted silo.pub itself is dead and maybe unlikely to return anytime soon
#
aaronpk
Indienews uses the same webmention overloading mechanism
#
snarfed
indienews++
#
Loqi
indienews has 1 karma
#
tantek
what is Webmention overloading
#
Loqi
It looks like we don't have a page for "Webmention overloading" yet. Would you like to create it? (Or just say "Webmention overloading is ____", a sentence describing the term)
#
tantek
two real world examples is good enough to define
#
aaronpk
I don't remember if I based that off of Bridgy or just came to the same idea
#
snarfed
um, if anyone has microsub bridge thoughts, uh, i'm all ears :P
#
tantek
looks for a wm -> mp bridgy issue
#
snarfed
i don't remember one, feel free to file
#
tantek
shall I file one for BP to reactions to comments too?
#
sknebel
snarfed: you seem to have covered it pretty well ;) I had the same thought with reusing the the token, but Inoreader uses refresh tokens so it doesn't work for my specific scenario
#
snarfed
sknebel: thanks! if you don't have any other thoughts, i'll also gladly accept implementations :P
#
snarfed
[tantek]: i don't quite follow but sure
tantek, [eddie] and snarfed joined the channel
#
[eddie]
Ultimately I hope to get to the point of being able to syndicate via micropub rather than webmention (as I’m doing now). I enjoy bridgy, but for my workflow, definitely would rather use micropub. That said, silo.pub is down (so I’m glad I never started using the public instance). I’m thinking long-term the likely solution is a PHP version of silo.pub. So the question is: is silo.pub in another language silo.pub (for language) or is it some
#
[eddie]
#NamesAreHard
#
KartikPrabhu
if someone wants to pick up development of the python silo.pub I am sure kylewm will hand it over
#
[eddie]
loathes python
#
KartikPrabhu
[eddie]: back at you with PHP ;)
#
[eddie]
lol maybe I should develop swift.pub 😆
#
KartikPrabhu
[eddie]: this is one of the things I really like about indieweb; you can use Swift/PHP and I can use Python and we don't really have to fight over it :)
#
[eddie]
Exactly 🙂
#
[eddie]
And our websites can still talk 😉
[cleverdevil] joined the channel
#
[cleverdevil]
Hmm... having a lot of trouble figuring out how to use Together as my Micro.blog client. Primarily having issues determinding sending replies.
#
[eddie]
Yeah, aaronpk and I are in the same boat
#
[eddie]
I write the reply on my site and then copy and paste it into the micro.blog app
#
[cleverdevil]
Right now, I have a rule in my Micro.blog feed generation template that *only* adds replies that are in-reply-to micro.blog URL.
#
[cleverdevil]
In those posts, I automatically add the appropriate @-mention with hyperlink to the mentioned person on Micro.blog.
#
[cleverdevil]
Works great.
#
[eddie]
That’s cool
#
[cleverdevil]
BUT, it doesn't handle people who are hosted extrnally.
#
[cleverdevil]
I've decided that @-mentioning is probably the hardest fundamental issue with Indieweb for me.
#
[eddie]
Well i think there are two different issues at play here
#
[eddie]
The first is cross-site replies in micro.blog: https://github.com/microdotblog/issues/issues/75
#
Loqi
[EdwardHinkle] #75 Adding support for cross-site replies
#
[eddie]
The second is @-mentioning in the IndieWeb, and yeah that is hard
gobengo and snarfed joined the channel
#
snarfed
[eddie]: i'
#
snarfed
er sorry...
#
snarfed
i'd recommend thinking critically about ROI on reimplementing silo.pub
#
snarfed
diversity is good and all, but i think we as a community get less value and learn less from reimplementing n silo APIs than from implementing things on our own sites or protocols
#
[eddie]
That makes sense,
#
snarfed
a micropub frontend to bridgy would definitely be nice though. you could make it a standalone proxy if you don't like python :P
#
[eddie]
How would a micropub frontend to bridgy work hypothetically?
#
snarfed
inside bridgy would be easy, it'd just handle micropub in bridgy publish
#
[eddie]
Gotcha. So then one could essentially either send a micropub post to bridgy or a webmention to bridgy
#
snarfed
a standalone proxy would accept requests, generate temporary html pages from them, send bridgy a webmention, and serve the temporary page as the wm source
#
[eddie]
with micropub the post wouldn’t have to exist at a url yet it would just contain the object you would normally get after the webmention fetch
#
[eddie]
Ohhhh interesting
#
snarfed
proxy would be significantly more work, but you wouldn't have to write python :P
#
[eddie]
While I joke on my dislike for Python, I have programmed very little python
#
[eddie]
as in a single college class 8 years ago
#
snarfed
it's pretty easy to pick up, but up to you!
#
[eddie]
So it’s more a lack of expertise than a strong dislike
#
[eddie]
hmm okay that definitely seems like a better optio
#
[eddie]
either the frontend proxy or the internal extension
#
[eddie]
But definitely better than building something from scratch on the silo side
#
snarfed
on the downside, if people switch to it from silo.pub, it increases our dependence on bridgy as a community even more :/
#
snarfed
tradeoffs whee
#
[eddie]
It’s tough, like what you said though, I’m more happy to rely on a single source for external silos than for independent functioning
#
[eddie]
So moving forward microsub and other things that decrease reliance on silos is definitely higher priority
#
snarfed
i've always wanted a real backfeed alternative implementation, for diversity. ah well
#
snarfed
(https://ownyourswarm.p3k.io/ does it for one silo at least. mailchimp social used to a bit iirc, but it's dead now.)
[keithjgrant] joined the channel
#
dgold
heh. I got stuck in the weeds on my prototype reader app
#
dgold
made a reader alright, but for my books database for my own website.
KartikPrabhu joined the channel
#
loqi.me
created /Vero (+287) "prompted by [keithjgrant] and dfn added by sknebel"
(view diff)
#
kaja.sknebel.net
edited /Vero (+1) "linkify ('… is <url>' pattern)"
(view diff)
leg joined the channel
#
Loqi
[snarfed] #796 micropub for bridgy publish
#
[eddie]
hahaha
#
Loqi
[EdwardHinkle] #797 Bridgy Publish micropub frontend
#
Loqi
[eddie]: lol
#
[eddie]
We literally must have been typing at the same time
#
[eddie]
I’ll close mine
#
snarfed
heh sorry!
[manton] joined the channel
#
[manton]
[cleverdevil] Can you explain more about the "BUT, it doesn't handle people who are hosted externally" comment?
#
[eddie]
haha no worries snarfed!
#
[cleverdevil]
[manton] sure. The way I decide whether or not to syndicate a particular in-reply-to post to my Micro.blog JSON Feed is by looking at the in-reply-to URL. If the user is hosted at Micro.blog, that URL will be "https://micro.blog/username", and I can also use that to pull the username and inject the hyperlinked @-mention into the feed.
#
[cleverdevil]
However, if they'
#
[cleverdevil]
If they're hosted elsewhere, the in-reply-to URL will be their domain.
#
[cleverdevil]
Which means I can't really tell that its a Micro.blog @-mention.
#
[manton]
Got it.
#
aaronpk
I have the same problem trying to reply to people
#
aaronpk
Even just sending webmentions for those since I don't have a special micro.blog feed
#
[manton]
One of my concerns is that there are too many ways to do the same thing. So in Micro.blog I want to focus on just 2: being smart about detecting replies and threads in a feed, and Webmention. Both have some holes as [eddie]'s GitHub issue points out, but I think they can be improved.
#
[manton]
Or to put it another way: I want to fix those holes before moving on to a 3rd option.
#
aaronpk
Sounds reasonable
#
[manton]
I was improving the Webmention support this morning and was reminded of some of the limitations.
#
[cleverdevil]
I don't honestly view this as a Micro.blog specific problem. Its really an IndieWeb problem.
#
aaronpk
It's an aggregator problem
#
[cleverdevil]
Well, @-mentions are, by nature, silo specific.
#
[cleverdevil]
I honestly would prefer to see them be based upon domain name.
#
[cleverdevil]
But, maybe I'm wrong 🙂
#
[manton]
Me too. That's where I want to go with Micro.blog eventually too. @manton.org instead of just [manton], so it works with people who haven't registered. That's the reason I created the test @nytimes.com Micro.blog account.
#
[manton]
But that's a ways off. I think we can improve this in the meantime with more traditional @-mentions.
#
aaronpk
Pure indieweb @-replies are just hyperlinks
#
[cleverdevil]
I definitely would prefer that, as it would make it much easier to implement things on both the CMS and the Micropub client side.
#
aaronpk
you don't need to have an account anywhere to say <a href="http://Manton.org">@manton</a>
#
[cleverdevil]
@-replies are just a lot more convenient to write than a full hyperlink 🙂
#
aaronpk
Right, so:
#
aaronpk
what is nicknames cache
#
Loqi
A nicknames cache is a way indieweb sites store information about people to improve the user experience of the site owner referring, mention, and/or linking to those people https://indieweb.org/nicknames-cache
#
[manton]
[aaronpk] Yeah, I view the @-mentions as more of a UI convention and shortcut.
#
[cleverdevil]
Indeed, another thing I'm interested in.
#
[cleverdevil]
But, its yet another thing to build.
#
loqi.me
edited /Vero (+136) "Zegnat added "http://orbitaloperations.cmail19.com/t/ViewEmail/d/1B72DF75601AC2EB2540EF23F30FEDED/6381983141E8A2A40F8C96E86323F7F9" to "See Also""
(view diff)
#
[manton]
To back up a bit... [cleverdevil], if you had an in-reply-to in your feed that pointed to an external site, what would you expect it to look like in the Micro.blog timeline?
#
[manton]
For those posts that you are currently filtering out.
#
[cleverdevil]
I wouldn't want to send it to Micro.blog.
#
[cleverdevil]
Unless it was a longer-form post.
#
aaronpk
Same, even if it's a long post
#
[cleverdevil]
That said, if Micro.blog *did* make it a bit easier to see the full context, maybe that wouldn't be true.
#
[manton]
Hmm. Your "BUT" comment made it sound like you were filtering those out because it was confusing, but that maybe they should be included.
#
aaronpk
If micro.blog were to consume my replies feed it would be able to match up my in-reply-to URLs whether they're micro.blog URLs or canonical URLs and id want it to ignore things it didn't match
#
[cleverdevil]
Thinking about it more, if Micro.blog actually rendered the replies in a nice way in the clients, I think I'd send them all.
#
Zegnat
tantek, I somehow missed your question about use case for marking up using/generator/etc for posts in between all the micropub and webmention talk! Woops.
#
Zegnat
With implementing Micropub I am taking the mf2 JSON it submits and storing that as the data for every post. I want to merge the details about the application I used into that same JSON. And would also like to be able to recreate said JSON (with an mf2 parser) from the outputed HTML.
#
Zegnat
So I was looking into how people (and silos) are already displaying said data, and whether there is some comonality in their markup, that I can copy.
#
[eddie]
I think aaronpk hit the nail on the head. The goal is to consume all the replies that are for posts within the micro.blog system, regardless of their canonical URL
#
aaronpk
I also like that option because it's the least work for both people with their own website
#
[manton]
Yeah, most people shouldn't need to have separate feeds at all.
#
[cleverdevil]
The less transformation I have to do on my end, the better.
#
[cleverdevil]
But, I do tend to filter out certain types of information that would make my feed noisy, like checkins and likes.
#
[manton]
I'd lean toward wanting to process all the replies and improve how they look for external sites. Piggybacking on the domain name discussion above, maybe even adding @someone.com for replies to external sites that Micro.blog has no idea about.
#
[cleverdevil]
(That said, that was always my vision with Together: let people send everything they have, and let the user decide if they want to see it or not).
#
[eddie]
Yeah, if there is some reply context for those posts, then I think taking them all in is great
#
[manton]
Related [eddie], I think there's another choice in your GitHub choices... I'd call it 2b: pull the source for a permalink in a feed and check it for Microformats. That is a lot more work for the server to do, though.
#
[eddie]
Yeah, 2b seems like a good option as well
#
[eddie]
I’d perfer 2b to 3
#
[eddie]
oops 2*
#
[manton]
It would make it more consistent with Webmentions.
#
sknebel
(what issue are you talking about?)
#
Loqi
[EdwardHinkle] #75 Adding support for cross-site replies
#
[eddie]
The thing that is nice about “2b” is that works with all feeds with no changes
#
[eddie]
As you said, definitely more server work 🙂
#
[eddie]
Whereas 3-6 all require changes to the feed
#
[cleverdevil]
(bbiab, lunching)
#
[manton]
[eddie] Right. It might be the most complete out-of-the-box. Just a little concerned about the performance impact.
#
[manton]
Maybe it's fine, though. I'll think about it a little more.
rainbow-zsh joined the channel
#
[eddie]
Yeah, that’s a valid concern. Definitely something to think about and look into. If you can swing it, seems like the most complete. If it’s not tenable, then I guess it’s back to the list with the question of what is “second best” but still performant
#
sknebel
since you recently talked about reporting back syndication URLs, if those are there a posting interface could automatically decide to syndicate the reply to micro.blog as well
#
sknebel
(although there is the issue that it'd have to know what the syndication targets mean, which they don't generally now)
#
sknebel
and it of course requires more tooling support than something that micro.blog can do on it's own
#
rainbow-zsh
jeremycherfas messaged me re: client attribution. I maintain Macchiato for 10Centuries AKA 10C. The API automatically attaches client info based on the token used to create a post. Docs are at: https://docs.10centuries.org/content
#
[eddie]
Yeah sknebel, having syndication urls would definitely help some of the instances
#
[eddie]
Still leaves some loose ends though since not everyone lists syndication targets on their pages
#
rainbow-zsh
Client chunk is just name and hash: "client":{"hash":"84e2bf4445b3c706309301e137ddf32cc3a2379e","name":"Macchiato"}
#
Zegnat
rainbow-zsh, thanks for the confirmation on the client object, I actually couldn’t find what that meant from the docs!
#
Zegnat
10Centuries documentation on client attribution I ended up with: https://indieweb.org/User:Vanderven.se_martijn/h-entry-using-property#10Centuries
#
rainbow-zsh
The docs are not terribly complete, but the creator is responsive to questions, and the first-party Web clients are unminified, so they’ve been sufficient for me.
#
rainbow-zsh
(It’s sneaky when not-WikiWord-text can still be marked as linking to non-existent pages. Completism, oy.)
[tantek] joined the channel
#
Zegnat
Taking all that in account when I run through the logs tomorrow and update with stuff people have commented. Thanks!
#
www.boffosocko.com
edited /Drupal (+376) "Webmention.io integration for Drupal 8"
(view diff)
j12t and [jeremycherfas] joined the channel
#
[jeremycherfas]
Rainbow-zsh++ for responding to my call for help.
#
Loqi
rainbow-zsh has 1 karma
#
[manton]
Quick correction from the earlier discussion about in-reply-to in feeds: I meant "3b", not "2b". "2" is Micropub syndication, "3" is MF2 in feeds.
KartikPrabhu joined the channel
#
aaronpk
I was wondering
[emilykager] joined the channel
#
[eddie]
ohhhh that’s it
#
lo.hn
created /User:Lo.hn (+57) "Created page with "<span class="h-card">[https://lo.hn/ Josemar Lohn]</span>""
(view diff)
KartikPrabhu, tantek and leg joined the channel
#
AngeloGladding
aaronpk is posting an issue on GitHub the best way to resolve a sign-in issue at indieauth.com?
renem joined the channel
#
aaronpk
Yea, that way I won't lose it
snarfed and theReal33mhz joined the channel
#
AngeloGladding
aaronpk thankfully just a duplicate of Zegnat's from Dec -- rel="authorization_endpoint" set to a relative path -- experienced the same with micropub.rocks not too long ago
#
aaronpk
hm I just tried with a relative URL and it seemed to work
#
aaronpk
oh nvm my site has both on it :P
#
AngeloGladding
ahh yes! i believe i did notice that when scratching my head.
#
aaronpk
cool I can reproduce the problem \o/
#
AngeloGladding
awesome thanks
#
aaronpk
theReal33mhz: the p- vs e- prefixes are parser instructions
#
aaronpk
e- means parsers will return an HTML value
#
aaronpk
p- means return plaintext
#
aaronpk
so <div class="e-content"><b>foo</b></div> will result in {"html":"<b>foo</b>","value":"foo"} and <div class="p-content"><b>foo</b></div> will result in just "foo"
#
theReal33mhz
handy
KartikPrabhu joined the channel
#
theReal33mhz
Why would a person would choose p-content?
#
aaronpk
if you don't have any significant html in your content perhaps
#
theReal33mhz
great - thanks!
[keithjgrant] joined the channel
#
GWG
So, what is everyone working on tonight?