tantekaaronpk, I can't find where the Webmention spec says what to do with Fragmention target or source URLs, and I'm wondering if that's a possible extension
tantekA fragment in the context of the indieweb typically refers to a fragment identifier at the end of a URL preceded by a # but may also refer to a [[media fragment]] which may use a fragment identifier or a query string.
tantekA fragment is part of a URL in the context of the indieweb, and typically refers to a fragment identifier at the end of a URL preceded by a # but may also refer to a [[media fragment]] which may use a fragment identifier or a query string.
tantekaaronpk are there any editorial improvements you want to make to the summary of Micropub that may end up in the W3C blog post about it going to PR?
Loqi[chrisaldrich]: tantek left you a message on 2017-01-26 at 12:07am UTC: I'm confused by this section: https://indieweb.org/WordPress_with_Bridgy#Rel-me_links - because shouldn't the IndieWeb Plugin already take care of your rel=me links for you? This section doesn't even mention the IndieWeb Plugin, and that you need to set it up with the links to your social media profiles. It should mention that right?
Loqi[chrisaldrich]: tantek left you a message on 2017-01-26 at 12:07am UTC: I'm confused by this section: https://indieweb.org/WordPress_with_Bridgy#Rel-me_links - because shouldn't the IndieWeb Plugin already take care of your rel=me links for you? This section doesn't even mention the IndieWeb Plugin, and that you need to set it up with the links to your social media profiles. It should mention that right?
[chrisaldrich]I didn't manage to figure out what was causing that part of the admin UI to not appear last night, but in looking through all the rest, I don't know if I had more notes than what we'd discussed.
[eddie]Curious how you all treat pages. Are they just articles? Are they special articles? Are they something different entirely, and if so, do you use microformats (h-entry's) to mark them up? I know that, aaronpk, for example have a form for webmentions at the bottom of all of your stock pages.
Loqicode in the context of the indieweb, refers to source code, code files, typically in a revision control system, like Git, hosted on an indieweb site https://indieweb.org/code
aaronpkfederated code repositories is definitely solved. federated pull requests somewhat less so, but linux's patch via email is a good example of federated pull requests.
tanteka repository is a collection of typically [[code]] & other files, [[issue]]s & [[responses]], and a set of [[release]]s related to a specific [[project]], often hosted in [[source control]] such as [[Git]], on a service like [[GitHub]] or on independent sites using open source software.
Loqiissue is a special kind of article post that is a reply to typically some source code, though potentially anything at a source control repository https://indieweb.org/issue
tanteka release is a snapshot of the [[code]] & other files in a [[repository]] as of a particular datetime, often with an explicit name (commonly referred to as the tag for the release).
LoqiVersioning is the practice of keeping previous versions of a post or other item available (possibly through a record of edits) https://indieweb.org/Mercurial
LoqiAll text and images contributed to the IndieWebCamp.com wiki are released to the public domain per CC0, as they were required to be copyright owned by the contributor prior to contribution and agreed to CC0 upon wiki editing, or already in the public domain or equivalent when contributed https://indieweb.org/Copyright
tanteka license is terms under which you are allowed to (re)use a piece of work; in the context of the IndieWeb, for source code such as in open source [[projects]], or content, like the IndieWeb wiki itself which has a specific [[Copyright]].
tantekZegnat if you can get some sort of rough consensus in that issue 39 thread, it's also ok to incrementally work on updating the licensing of each project the way php-mf2 was updated
ZegnatIt’ll have to be done incrementally, as for every repo every contributor will have to give their consensus. I thought it would be good to get the discussion going at a central spot first.
tantek.comedited /report_abuse (+820) "note past Instagram info was as of 2015, and new UI as of 2017 (and more responsive), note anecdotal much faster response to spam reports" (view diff)
aaronpkand the reason they picked 3 months is for exactly this reason, because they want people to automate it from the beginning because it's too hard to remember all the steps
tantekaaronpk - both the vote to take Micropub to PR pending another implementation for that one feature, and subsequent implementation + report update are worth announcing at HWC!