#GWGI think I'll stick to making pfefferle and snarfed review my stuff. Much more open audience.
snarfed joined the channel
#[miklb]how would that PR benefit webmentions? Or would it?
#[miklb]if it does, I would mention that in the ticket
#GWG[miklb]: I implemented the same approach for webmentions.
#[miklb]so the PR doesn’t effect webmentions one way or another? Gotcha. Still think it’s a good idea. Just thought if it were to help with webmentions, that *might* help
#GWG[miklb]: You think they care about Webmentions?
#@royscholten↩️ yep. WebmentionIO calls it Web Hook. If that terminology is reflected in the Drupal settings, that would already help. Also, making a clearer distinction between "on your site" vs. "use this on http://webmention.io". Fun to see it working though! :) (twitter.com/_/status/1003607285288132609)
swentel, [Vanessa], loicm, [jgmac1106], leg and snarfed joined the channel
#aaronpkusing the private key from your blockchain wallet instead
#aaronpk"this login process does not actually need the blockchain: It only needs its cryptography functions"
[xavierroy], [schmarty] and [kevinmarks] joined the channel
#[kevinmarks]Yes, most wallets have a "sign this" option
#ancarda[schmarty]: Can you give me the link to your granary.io atom feed? I could add that to my website as a quick win, and self-host some h-feed to atom tool at a later date
#ancardaI'd imagine it wouldn't be too hard to use X-Ray to parse each post. If I split out the page construction to a function, I can just run that for each post, parse it, and output some XML
#tantekis anyone else besides aaronpk, chrisaldrich, and me posting GitHub issues, comments, reactions on their own site first, and then POSSEing them to GitHub?
#tantekjalcine: it took a little bit of tweaking to my site too beyond just adding a new post type
#tanteke.g. I had to add the ability to NOT POSSE to Twitter, since I decided GitHub issues/comments made very little sense on Twitter outside the context of the repo/thread that they were on
#jalcineyeah - this would be a bit more trickier since my site's completely static
#jalcinethat's becoming more and more of a burden the more I want to add content to it (outside of Note posts)
#tantekjalcine: do you show comments on any existing posts?
#tantekshowing comments / responses on an /issue post is not much (if any?) different
#jalcinecurrently, yeah: classic (via isso) and replies
#tantekand FWIW, at least just start with owning your issue / comments
#aaronpkwhat the heck, I just got the weirdest email from twitter
#aaronpk"Your Twitter account (or accounts associated with you) currently has multiple registered applications, in potential violation of Twitter's rules on the use of multiple API keys for a single use case."
#aaronpksnarfed: did you get one of those? I know there are a ton of bridgy apps
#sknebelkind of funny that /issue only acknowledges Github as a place where issues can be. no bugzilla, no Gitlab, ...
#sknebelaaronpk: do they say which apps they mean?
#aaronpk"If these applications do not serve distinct use cases, please log into your existing account on https://apps.twitter.com/ and delete any applications which are in violation of our rules. "
[chrisaldrich], snarfed, [JaredEwy], tantek, gRegorLove, KartikPrabhu and [grantcodes] joined the channel
#[grantcodes]Firefox it pretty hardcore about what it blocks if you switch on tracking protection, took me a while to realise it wouldn't even load twitter avatars! I thought there was an issue on my site 😛
snarfed joined the channel
#loqi.mecreated /X-marks (+139) "prompted by chrisaldrich and dfn added by chrisaldrich" (view diff)
[eddie] joined the channel
#[eddie]Super excited, Apple gave a pre-announcement that iOS apps will be able to be converted into mac apps in 2019! So, Indigenous for macOS will definitely be a thing. For the rest of this year I need to get it functioning on the iPhone, and then improve iPad support, which will pave the way to transition it to macOS in 2019
#[eddie]They can continue to exist, they didn't announce any kind of depreciation of the existing frameworks (at least for now), but they essentially created UIKit on the mac
#[eddie]and they are testing it with 4 new apple apps coming to macOS (Stocks, News, Voice Memos and Home)
#[eddie]Where Apple literally built iPad apps and then transitioned them to the mac as well
#[eddie]so you have two potential frameworks you can use on the mac for now
#Loqiaaronpk has 147 karma in this channel (1641 overall)
#Loqi[Aaron Parecki] What we really need is federated authentication, but that doesn't exist yet.
This sounds like a great use case for IndieAuth. w3.org/TR/indieauth
IndieAuth is an OAuth 2.0 extension, which avoids the centralized problems with existing OAuth soluti...
#Loqidogfood in the context of the indieweb, refers to the software practice of "eating your own dog food" but in particular with using your own creations on your own personal site that you depend on, day to day https://indieweb.org/dogfooding
#snarfedif you have in-reply-to an indieweb post, and it has the synd link to a silo post, bridgy will infer that it's (also) in-reply-to that silo post
#snarfedyeah, same org permissions error. i added a nice error message for comments, since they get a 403 with useful error from github
#snarfedreactions get a 404 that's identical to when the issue doesn't exist :(
#tanteksnarfed, however I still have to include the link to bridgy to cause it to try right? so my site still needs to do the work of finding out if there is a silo synd link, to know whether to bother with providing a github link for that silo
#tantekso at that point I might as well make it a multi-reply with the silo synd link as an additional explicit in-reply-to
#Loqi[aaronpk] > What we really need is federated authentication, but that doesn't exist yet.
This sounds like a great use case for IndieAuth. https://www.w3.org/TR/indieauth/
IndieAuth is an OAuth 2.0 extension, which avoids the centralized problems with ex...
#tantekI tried to POSSE a reacji to that via Bridgy Publish and got a 404
#tantek(should be a 403 instead but that' s a separate github api bug)
#tantek.comedited /GitHub (+540) "/* Tantek */ add more different types of posts, and permalinked dates" (view diff)
snarfed joined the channel
#tantek.comedited /Gitea (+301) "update dfn for how it's actually useful rather than history, stub features, stub history with old dfn info, see also" (view diff)
#sknebelfiguring out that one of the rel-me's is a gitea instance (or any other thing that's not a central silo) is an interesting problem. I guess with caching (so you don't have to do it each time a user uses indielogin) it'd be not too much overhead to fetch each linked page and run checks identifying what's running there
#tanteksknebel, to be more precise, start with detecting try.gitea.io just like detecting github.com
#aaronpkbecause normal OAuth requires registering a client with the instance
#sknebeltrue, and the current password auth is maybe not something to implement
#tanteksknebel: I don't understand - all the indielogin silo providers have password auth
#sknebelbetween user and silo, with OAuth between indielogin and silo. If I saw correctly Gitea doesn't have Oauth yet for applications, so it'd have to use the API with the users username and password
#sknebelbut aaronpk is of course right, for normal OAuth it doesn't work either, at least not without a site admin adding indielogin
#tantek.comedited /IndieAuth (+60) "ways people might be asking for IndieAuth without actually saying it like OAuth2 login OAuth-based login etc., update dfn, naming a bit" (view diff)
#tantekaaronpk should https://indieauth.net/ now link to indielogin.com instead of indieauth.com as a "Public IndieAuth Provider" ?
#tantekthis in particular: If you’re familiar with writing an OAuth client, then you're familiar with the problem of having to register your client manually with each OAuth provider. IndieAuth uses DNS as a replacement for client registration, thereby eliminating the need for any manual registration with providers.
#Loqitantek has 34 karma in this channel (439 overall)
#tantek!tell aaronpk,chrisaldrich,gRegorLove,jalcine,schmarty What do (features on your website) do you want to finish / launch / start using *before* IWS? Can you add to your entry in https://indieweb.org/2018/Guest_Book ? See mine for example: "Working: for IWS 2018(link)"
#tantek!tell ancarda re: what to work on after you get indiewebify.me stuff working, check out https://indieweb.org/IndieMark for step by step new things to add support for to your site, in incremental increasing order of challenge / functionality