Jamie Thingelstad Profile Photo

Jamie Thingelstad

Writer of the Weekly Thing. Explorer of tech, the open web, AI, and a good escape room. Minneapolis is home.

POAP2RSS

Here I document building and refining POAP2RSS, a service that turns POAP claims into RSS feeds. Posts range from praising updown.io’s monitoring to a deep dive on “vibe coding” where AI assisted me in writing the service’s AWS Lambda functions.

    ∞

    I decided to declare POAP2RSS officially launched. It seemed fitting for Independence Day!

    How do you celebrate creating a service to make POAP activity available in RSS? You make a POAP of course! Now drop — POAP2RSS Created! 💥

    ∞

    I cleaned up the RSS items that POAP2RSS outputs this morning. I decided to remove the titles on the items and add the POAP images which makes it great for adding to a micro.blog timeline. Now I can share my POAP claims automatically!

    ∞

    Collected POAP 7386503 for POAP2RSS Created.

    ∞

    I’ve created my first project using AI to write nearly all of the code with me!

    Introducing POAP2RSS!

    For years I’ve wanted to get updates for POAP events and users in RSS. Now with the help of AI I’ve created it!

    Still cleaning to do. Check out the code on Github.

    ∞

    POAP + RSS = Awesome?

    Update: I created POAP2RSS to fill this gap!

    I’m a big fan of POAP, and I’m a big fan of RSS. Sadly, these two things don’t know about each other, yet! This blog post is my take on a great start for RSS and POAP. Maybe there is a chance that the amazing folks at Open RSS could bridge this gap in the meantime!

    First, why should POAP add RSS? I think there are dozens of use cases, but some examples…

    1. As someone that issues POAPs a lot I would love to subscribe to the RSS feeds for each of my events and see via the feed when a new token is claimed.
    2. It would be powerful to use automation on claims along by connecting the RSS feed for an event to IFTTT or any of the hundreds of services to take an action when an RSS feed is updated.
    3. There are several friends that are active in the POAP ecosystem and I can aggregate a feed of all their claims in the POAP Home app, but I would rather subscribe to an RSS feed of each of their addresses and get updates that way.

    There are two items that RSS feeds would be useful for: Events and Collectors. There is a POAP API that would make both of these pretty simple to get, and avoid any screen scraping. An API key would be needed but I think that would be easy to get. These use cases are all read only as well.

    Events

    Anybody can create an event the RSS feed would be specific to that event. Events have a simple ID, and there is a Token Event API method for /event/{id}/poaps that would get exactly what is desired. The URL’s for an event are https://poap.gallery/drops/{eventid}, my 53rd Birthday POAP is at https://poap.gallery/drops/183305 is an example.

    In this case, the eventid is easily found and using the API could get the data to populate the RSS feed.

    Addresses

    Getting an RSS feed for new tokens that people claim is centered around a wallet address. Here we are looking for an address or ENS name. An example of this is my collection at https://collectors.poap.xyz/scan/0x111accebf9d70d9c06de2d38f9392522e82ecf29. This can also be accessed via the ENS name at https://collectors.poap.xyz/scan/poap.thingelstad.eth.

    The Token Scan API method /actions/scan/{address} returns the list of tokens for that address and could build the RSS feed.

← Newer Posts