KartikPrabhucweiske: a more detailed "critique" of the indieweb approach wrt previous approaches speaking to protocol agnostic way of doing things would be quite useful (specially for people who only knows the ins/outs of one approach, like me)
Loqiaaronpk: barnabywalters left you a message 1 hour, 11 minutes ago: http://waterpigs.co.uk/notes/new now has h-x-app/h-product markup and nascent Taproot logo. looking forward to seeing these used in authorization UI!
JeenaI had it always with the domain but just a week ago or something I found out that my own code doesn't work for some other website which only had /webmentions so I changed it to be able to test it. Then I forgot to change it back.
GWGbarnabywalters: The code I'm writing inserts the URL being responded to(hence referred to as the response URL) display above the content. A like would effectively not have anything in the content box, it would only have the display of the external URL marked up appropriately
GWGbarnabywalters: I'm trying to get the logic working correctly. So far, we've added in the fields for a response url, title, and citation. And I'm working on the display logic...as all three of those fields are optional
Jeenais it possible to let bridgy try to send older likes and comments from facebook? I missed that this was not working and now quite a lot of them have not been pushed, or will it retry automagically after some time even for one week old ones?
bret!tell cweiske the rel=me microformat is the key ingredient for setting up indieauth. I think maybe I misunderstood exactly what you did, but its interesting to see how indieauth can route around the rel me auth all toegether
Loqicweiske: bret left you a message 1 hour, 6 minutes ago: the rel=me microformat is the key ingredient for setting up indieauth. I think maybe I misunderstood exactly what you did, but its interesting to see how indieauth can route around the rel me auth all toegether
aaronpkGWG: I definitely have a plan. But rather than making a bunch of flashy talks about it or writing up a "manifesto" I'm trying to demonstrate it piece by piece by documenting it and building out implementations
acegiakso a job I applied for has asked for a php code sample which includes an class with at least two functions one of which has to be a mysql query and the second of which can do "something magical of your choosing" so I'm trying to decide what to do