LoqiIt looks like we don't have a page for "issue with it" yet. Would you like to create it? (Or just say "issue with it is ____", a sentence describing the term)
tantekand got error: "Error from Facebook API or your site: {"error":{"message":"(#100) User must be able to RSVP to the event.","type":"OAuthException","code":100,"fbtrace_id":"CpvibG9EmhI"}} HTTP Error 400: Bad Request"
tantek.comedited /want (-18) "drop fingers-crossed emojicon because it means either an out-of-control want, or possibly sign of deception (behind ones back), neither of which represent the "actionable want" that this post type is about" (view diff)
aaronpkreally it's there so that clients posting simple content can avoid having to use the nested json format and still expect to work with all servers, so most of the time that's going to just be h-entry
[cleverdevil]I am thinking of creating a very, very simple and compliant micropub server that essentially just stores every piece of published content either on disk or in an S3 bucket.
aaronpkI would recommend doing microformats json syntax validation before you store anything so that when you're reading it back you can be sure it's already valid mf2 json
aaronpkso for example, you'd reject a JSON request that looked like {"type":["h-entry"],{"properties":{"foo":"bar"}} since the value of "foo" is not an array and that's invalid mf2 json
aaronpkif you want to limit the vocabulary then I would recommend going further and really clamping down on what's allowed, which is essentially what i've done with XRay/Aperture/Microsub
[tantek]Gregorlove “want to read” or any “want to” is a /want post. /read/watch is for when you’ve done it, whether the whole thing or competed some number of pages / chapters / minutes / episodes etc
[tantek]Snarfed, so WDYT of Bridgy support of multi-rsvp? So I can post one rsvp post for multiple sessions instead of having to post one rsvp per session
snarfed[tantek]: API support isn't really documented, so i need to go learn more...but it looks like the API only allows RSVPing to individual sessions, not the whole thing
LoqiA passive post is a post that is created without the person taking an explicit action to create the post, such as listening to music that happens to be playing or watching a show that starts playing by itself, like YouTube's autoplay https://indieweb.org/passive
[manton][aaronpk] Following up on the IndieAuth issue... Did the authorization endpoint used to return the "me" parameter? The code checking that in Sunlit should be identical to what I do in Micro.blog iOS, and I haven't heard any problems about it.
aaronpkan early version of the spec had the "me" parameter returned at the callback URL, so Known implemented it that way, but the client can't safely rely on it at that point so we took it out
Loqi[Tantek Çelik] h-event is a simple, open format for events on the web. h-event is often used with both event listings and individual event pages. h-event is one of several open microformat draft standards suitable for embedding data in HTML.
h-event is the microfo...
Loqi[Aaron Parecki] Monocle just got real fancy. I can now set a default account for each channel from which responses should be sent. (Stored in my Microsub server, not in Monocle, so it can work across clients). Monocle recognizes when alternate accounts are available... https://aaronparecki.com/2018/03/08/13/monocle-account-chooser.png
[eddie]!tell aaronpk: I have actually added tentative support for checkin display to Indigenous, but I definitely still need to do more improvements when I get the chance