I'm very happy to announce that `meetup-mf2.jvt.me` is now live and provides a Meetup.com translation layer for [Microformats](https://indieweb.org/Microformats). This makes it possible to integrate with your favourite Microformats parser and get programmatic access to a meetup's metadata.
I'm very happy to announce that `meetup-mf2.herokuapp.com` is now live and provides a Meetup.com translation layer for [Microformats](https://indieweb.org/Microformats). This makes it possible to integrate with your favourite Microformats parser and get programmatic access to a meetup's metadata.
Having Microformats available is incredibly useful because it is a standardised format that makes it possible to use a wide range of clients to understand what i.e. a Meetup event is without having to either use the Meetup API or understand how Meetup's specific HTML works to render their events, and then parse out the data we need.
...
...
@@ -44,9 +44,9 @@ I've not yet worked on handling / avoiding rate limiting, nor anything around ca
It's still a little rough around the edges, and is still v0.1, but I hope to improve it over time. I'll likely convert it to an AWS Lambda so I can avoid having it running on some infrastructure, and I know <spanclass="h-card"><aclass="u-url"href="https://aaronparecki.com/">Aaron Parecki</a></span>[was interested in adding it to XRay](https://chat.indieweb.org/dev/2019-08-30/1567184835706900), as well as hopefully some other implementations available elsewhere.
~~As [Ryan Barrett noticed](https://snarfed.org/2019-08-31_introducing-a-microformats-api-for-meetup-com-meetup-mf2-jvt-me) the API only responds to requests on certain routes following the meetup's URL, as I've not yet created i.e. a landing page.~~
~~As [Ryan Barrett noticed](https://snarfed.org/2019-08-31_introducing-a-microformats-api-for-meetup-com-meetup-mf2.herokuapp.com) the API only responds to requests on certain routes following the meetup's URL, as I've not yet created i.e. a landing page.~~
**Update 2019-09-14**: The landing page for the meetup itself is this blog post - so if you're trying to hit `meetup-mf2.jvt.me` and keep coming back here, that's why!
**Update 2019-09-14**: The landing page for the meetup itself is this blog post - so if you're trying to hit `meetup-mf2.herokuapp.com` and keep coming back here, that's why!
# Demo
...
...
@@ -74,7 +74,7 @@ GET https://api.meetup.com/PHPMiNDS-in-Nottingham/events/264008439/
But if we rewrite the host and hit my API instead (noting that the path in the URL remains the same), we get a handy [h-event](http://microformats.org/wiki/h-event):
Note: This post is very similar to [Introducing a Microformats API for Meetup.com: `meetup-mf2.jvt.me`]({{<ref"2019-08-31-microformats-meetup">}}), so I'd recommend a read of that post for some more of the context of why I'm doing this.
Note: This post is very similar to [Introducing a Microformats API for Meetup.com: `meetup-mf2.herokuapp.com`]({{<ref"2019-08-31-microformats-meetup">}}), so I'd recommend a read of that post for some more of the context of why I'm doing this.
I'm happy to announce that `eventbrite-mf2.jvt.me` is now live and provides a Eventbrite translation layer for [Microformats](https://indieweb.org/Microformats). This makes it possible to integrate with your favourite Microformats parser and get programmatic access to a event's metadata.
I'm happy to announce that `eventbrite-mf2.herokuapp.com` is now live and provides a Eventbrite translation layer for [Microformats](https://indieweb.org/Microformats). This makes it possible to integrate with your favourite Microformats parser and get programmatic access to a event's metadata.
This was partly due to the [recent community concerns about Meetup.com charging organisers for each RSVP to an event](https://www.theregister.co.uk/2019/10/15/meetup_fee_increase/), but I've also been thinking that I need to extend my Micropub support for different events, and as Eventbrite does not provide Microformats2 data for their events, I'd have to do it myself.
...
...
@@ -62,7 +62,7 @@ Notice that this `venue_id` needs a separate API request, which I won't display
To make the API easy to use, we can rewrite the host of the Eventbrite URL, and add my host instead (noting that the path in the URL remains the same), we get a handy [h-event](http://microformats.org/wiki/h-event):
In August I [announced a Microformats API for Meetup.com: `meetup-mf2.jvt.me`]({{<ref"2019-08-31-microformats-meetup">}}) to act as a translation layer between the silo and the IndieWeb.
In August I [announced a Microformats API for Meetup.com: `meetup-mf2.herokuapp.com`]({{<ref"2019-08-31-microformats-meetup">}}) to act as a translation layer between the silo and the IndieWeb.
I've been using this as a core part of my own workflow for RSVPing to events, but that's usually when I see the event actually on Meetup.com and then manually RSVP from my website.
...
...
@@ -23,7 +23,7 @@ To make it so I could discover new events from my [Indie reader](https://indiewe
With the [v0.2.0 release](https://gitlab.com/jamietanna/meetup-mf2/-/tags/0.2.0)(now in production!) this is now available for usage, which you can do with the following request to get the upcoming events for a given Meetup.com group:
After many months of running Microformats API for Meetup.com and Eventbrite.com from my own infrastructure, I'm moving it over to Heroku.
This is more to simplify my hosting setup, and because Heroku is a nice platform to use.
As a consumer, please note that you'll need to move to the new URLs, `meetup-mf2.herokuapp.com` and `eventbrite-mf2.herokuapp.com`. I think redirects may be working for now, but it won't be there forever.
I've updated my previous articles to reference this, but if you're using it, please update your references too!