#LoqiAn RSVP is a reply to an event post that says whether the sender is or is not attending, might attend, or is just interested in the event https://indieweb.org/rsvp
#aaronpkitll look like a reply and there will be an additional property "rsvp"
#TheGillies> When you receive a webmention from a URL that is a reply (has an in-reply-to URL that is the event URL), also check if the entry contains an rsvp property.
#Zegnatcweiske, does GitHub render anything else by default? I would not be surprised if the choice for the #-headers was made to get better display on GitHub. (Assuming you are still talking changelog)
#petermolnardid you summarise why? I'm just curious.
#voxpellikeepachangelog never actually says you _should_ use Markdown and Markdown being the most widely used format for such files nowadays makes it the natural choice for examples
#cweiskeno, I wrote no summary. it is: markdown is not enough for complexer documents that want .. tables, and it's fragmented. so I always use rST because I don't have to switch document formats once I need more structured elements
#voxpellipersonally I think Markdown works great for readmes and changelogs
#ZegnatTo be fair to cweiske’s criticism, petermolnar, you are sticking to a specific Markdown compiler that dictates what formats you can use (e.g. for tables) rather than saying you use just Markdown
#petermolnarthe Gruber Markdown is way to "simple" - stupid, one might say -, there is commonmark, flavours, markdown this, markdown that
#ZegnatYeah, I think that is cweiske’s argument, re fragmentations. You have solved that by picking a specific interpreter/compiler/whatchamacallit
#petermolnarwell... what I'm doing is more or less the github flavour markdown
#petermolnar``` code blocks, definition lists, strikethrough, footnotes are the most important "extras", and sometimes I use link attribures ({.class #id}) to align images, that's all
#petermolnarI'm tempted to call it reasonable markdown
#tantek"I’m fed up with Disqus. It’s been useful, easy to plug on this blog, but it’s a mess for web performance, and I don’t own my data, so… bye bye. "
#aaronpki'm really curious if this can work with IndieAuth
j12t and [eddie] joined the channel
#[eddie]aaronpk I haven’t looked at it too in-depth, my initial goal had been to get Indigenous out during iOS 10, so I was trying to ignore iOS 11 stuff until I got 1.0 out the door, however I’m getting very close to iOS 11 land. ? So, yeah that worked well.
#Loqi[eddie]: tantek left you a message 2 weeks ago: but if you have micro.blog access/account, can you then use the Micro.blog app with any Micropub server? (like your own site?)
#[eddie]From what I read initially I thought it was really focused on auto-sign in, but that article seems like ther emight be more to it
#[eddie]I think it’s for two main things: make people not worry about OAuth flow (which isn’t that hard) and help with auto-sign in if you have credentials stored in your iCloud Keychian
#[eddie]But there might be some extra goodies in it
#aaronpktheir AppAuth library is meant to work with any OAuth 2 provider, which is why i'm thinking this might be useful
#[eddie]Also, in regard to iOS indieweb frameworks, I think I’m going to just release a single indieweb iOS framework, because based on some stuff I’ve been reading, adding a lot of frameworks to an app has negative performance implications on bootup and other things.
#[eddie]Instead of my initial approach which was to try to do everything separate (relMe, IndieAuth, Micropub, mf2) like you might on the web for simplicity and performance sake, I’m gonna just have a single indieweb framework, at the most two potentially splitting it into two if there can be two clear groupings.
#aaronpkdoes this mean you're writing a ObjC/Swift microformats2 parser??
#aaronpkthat one i think might be better published separately
#[eddie]Yeah, I had this feeling like Xcode didn’t want me having these things so modularized it felt like it was fighting against me and then I read up on some stuff around performance and frameworks and such. I haven’t yet, but it’s on the list…. probably the end of the list
#[eddie]Okay, so an mf2 parsing framework and an IndieWeb framework? that could make sense.
#[eddie]IndieWeb would then be IndieAuth, Micropub and RelMe stuff, which does all kind of work together well
#[eddie]like if you are doing IndieAuth it’s a good chance you’ll do Micropub, etc)
#[eddie]So yeah, I’m gonna merge that repo code into the IndieAuth one, rename it IndieWeb. Then put the micropub code in there and one day we can even put Microsub code in there ?
#LoqiMicrosub is an early draft of a spec that provides a standardized way for clients to consume and interact with feeds collected by a server https://indieweb.org/microsub