#Loqi[jgmac1106] has 4 karma in this channel over the last year (52 in all channels)
#[jgmac1106]yeah you are right webmentions, but its built...just not scalable...have to do it manually one html file at a time, I do hope to hope to leave NYC with a system...or atelast directions for piggybacking off of third party stuff, attached to my mf2 course templates that others can use
#tantek__[jgmac1106]: sounds like it's *prototyped*, not really "built" yet for easy use :)
#Loqi[Greg McVerry] I have been playing with webmentions for badging. I think we can do this all from our own domains, allowing learners to own evidence, and just creating a ledger of 2-3 permalinks. No backpacks, issuers, etc. Just two websites talking together
tantek, tantek__ and sandGorgon joined the channel
#Loqi[Greg McVerry] I just added Literacy, Technology, Policy, Etc….A Blog by @jenroberts1 to my following page at https://jgregorymcverry.com/following #BeYourownSocialNetwork
#ZegnatSo .h-card.p-title inside .h-entry actually means the .h-card is the value for the .h-entry’s .p-title.
#ZegnatWhenever an h-* and a p-* class exist on the same element, it means to use the h-* as the value of the p-* attribute on the parent.
#[jgmac1106]wow there is an esoteric rule I never knew
#ZegnatThat’s why something like .u-like-of.h-cite or .u-follow-of.h-card will work. Because you want those h- objects as values on the entries like-of and follow-of properties.
#Loqi[Zegnat] <a class="u-follow-of h-card" href="$url">$name</a> - should be enough for following a person
#[jgmac1106]yeah that is where I started, the problem for me is i am sepearting the hcard to also @ mention them on twitter, mastodon, or microblog
#[jgmac1106]so I am linking to their website on the u-follow but trying to link to the twitter account in their h-card
#Zegnat<a class="h-card" href="$url">$name</a> is enough to mention someone then.
#ZegnatWithout any p-name and u-url classes, those properties will be implied by the parser to be the element’s content and the element’s href respectively.
#Zegnat(Plus some other heuristics and things, but you don’t have to care about those for this example.)
#Loqi[Kevin Marks] @Gargron do you verify links in a profile mirrored from another instance ? Or do you trust that instance to verify them and put them in the api?
#[kevinmarks]It looks like changing the profile links triggers the rel-me crawl, but I don't know how it works with mirrored profiles
#Loqi[Eugen] @postmasterdoggo @qubyte @moonman What's wrong with the blue check mark is that it gatekeeps useful features and that it's selectively provided.Voluntary identity verification that does not involve real names or documents is fine, and more than that,...
#[kevinmarks]hm, could indieauth.com use mastodon to verify a domain now? They have rel=me links and an oauth api
#aaronpkAlso I rely on matching "twitter.com" and "github.com" in rel=me URLs to find the user's username and know which OAuth provider to use, but there's no way to tell by looking at the URL that it's a mastodon profile so it would also take an additional check to test if the hostname is running mastodon which id have to run on every rel=me url
#aaronpkSo no it's not practical to add mastodon to indielogin.com :-)
#ZegnatYep. That is always going to be an issue with these self-hosted OAuth things. Until they all implement IndieAuth
[jgmac1106] joined the channel
#[jgmac1106]....goes to delete post saying can't wait to log into site with his mastodon account..actually will just update with link to this chat
#[kevinmarks]you could check for the rel="salmon" link
#aaronpkI would really rather not hack up a less than ideal solution for a project which is in active development which also fits the goals and model of IndieAuth
#aaronpkAnything I do along those lines would be specific to mastodon whereas we could create a solution that actually works in a way that the other fediverse projects could also adopt
#[kevinmarks]you don't currently check for indieauth endpoints on linked sites, do you?
#aaronpkI don't think known can be a standalone auth endpoint
#aaronpkbut I could add support for second level IndieAuth which would enable things like that
#[kevinmarks]yes, thats what I meant, sorry - rel=me linking rather than auth/token linking
#[kevinmarks]so silos are less special than they are now
#[kevinmarks]hah. That could also mean that if you rel-me from twitter to your indieweb site you could prove it's your twitter without logging into twitter
#[kevinmarks]I heard you like auth, so I put auth in your auth
[manton] joined the channel
#[manton][aaronpk] You can register an app (and get back a client ID and secret) with an Mastodon API call. You're suppose to do this once per instance and then cache the results.
#aaronpkThat's too bad, it would be easier to use the app's url as the client ID like IndieAuth does
#[kevinmarks]instead of having to respond to an SMS to a number that now belongs to someone else
#ZegnatThe git submodules will atleast keep your report somewhat clean. No need for it to track all the files in the external dependency. But it doesn't help at all with the shared dependency issue, right?
#GWGIt does as long as jackjamieson and I update the plugins whenever we update the dependency
#ZegnatRight. Yes, if all the plugin authors make sure to keep their dependencies synched...
#jackjamiesonI'm not very well-versed with managing dependencies like this, and WordPress makes things difficult, but could the best option be that we each assign parse-this a namespace in our respective plugins? That way each instance could run separately, right?
#ZegnatNot if you are using the same base files. Namespaces are per file. So you would both need a separate clone of parse-this in your respective plugins
#ZegnatThere is no way to dynamically load files under a different namespace. I tried ~month ago when we discussed this during vHWC
#ZegnatIf you share a dependency, whoever loads it first picks the version. Plugins that load later can either hope their usage is compatible, or choose to not call upon that code at all.
#ZegnatI am still a bit surprised WordPress doesn’t have a way to solve this themselves
#jackjamiesonI agree, I wonder if there has been any work to implement a dependency manager in wordpres
#swentelsnarfed, when I hit follow (from @swentel to @realize.be), does that mean a request should've come in at fed.brid.gy ? I wonder whether you're able to see that coming in ?
#snarfedswentel: yes, i expect your mastodon instance tried to send an AP Follow to Bridgy Fed, which it doesn't currently handle
#Loqi[snarfed] yes! here it is. bridgy fed responded with HTTP 501 Not Implemented.
`POST https://fed.brid.gy/realize.be/inbox`
```json
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://w3id.org/security/v1",
{
"manua...
#swentelsnarfed, so basically, need to figure out to send a reply now in activitypub.py .. will see if I can figure that out, my python is quite rusty :)
#snarfedswentel: definitely possible locally! i usually develop first with unit tests, but then you can run it with eg `dev_appserver.py --log_level debug app.yaml`
#snarfedand yes, you don't have permissions on the prod instance, so you can't deploy to it
#swentelsnarfed, does this ring a bell to you 'ImportError: No module named future_builtins' - getting 500 even on even a simple GET request - apologies for the possible noob question :/
#snarfedodd. can you post the full stack trace? anywhere
#doubleloopIs it be possible to use Bridgy Fed in the same way as it works with twitter? (rather than my site be its own instance.) I have an existing Mastodon account that I'd like to keep, but it'd be cool for the syndication to happen via bridgy (rather than my hack), and would be amazing to get the backfeed too
snarfed, lachm, jackjamieson, [schmarty], benwerd and [manton] joined the channel
#@AndreJaenisch↩️ I likely forget some links over today's writedown.
Will add those at a later point.
Since I have a static site, either reply to me here or write me an email.
(Plan is to implement #webmention properly for comments) (twitter.com/_/status/1042911455534829569)