Hey, Micropub is a protocol that apps and sites can agree to allow posting to your site using various apps that you don’t have to build. A Micropub endpoint is the url that the Micropub app needs to use to communicate with the site. More here https://indieweb.org/Micropub/Clients
No worries! Feel free to join the #indieweb irc or Slack channels if you have any questions! We’re always happy to help 🙂 https://indieweb.org/discuss
Anyone have any concerns or questions around the latest Facebook Data Breach issues?
https://futurism.com/abuse-facebook-data-cambridge/
Feel free to ask and I’ll try to help talk it through and what your options are.
@dentonjacobs Just FYI, On your homepage’s h-feed, your h-entry’s children have children: http://pin13.net/mf2/?url=https://www.dentonjacobs.com/ which causes issues with h-feed parsers being able to follow your website
Congrats! Welcome to Micropub land! #indieweb
Congrats! Welcome to Micropub land! #indieweb
I think an important aspect of the IndieWeb to remember is that even though one uses a domain as their primary identity, that doesn’t preclude the use of multiple domains for different aspects of your identity. In fact this is something that was discussed in the Identity and the IndieWeb session at IWC Baltimore 2018
In order to align native comments with webmentions I wanted to remove the need for a commenter to enter an email address but still have 'Name' as a required field. Unfortunately, the setting in WordPress is for both or neither.
By hooking into preprocess_comment I could prevent a comment being posted if $fields[comment_author] was blank but, unfortunately, this seems to stop the processing of webmentions - presumably because at the point of processing the author field hasn't yet been filled from the webmention data - so have had to revert the change.
I was making some changes to the way comments work - specifically with regards to required fields - and think It might have had a knock on effect with webmentions. This post will serve as a test.