Hey, all! I’m seeking some help testing an application I whipped up for the Geosocial task force of the W3C Social Web Community Group. It’s called https://checkin.swf.pub/ , and it’s a barebones checkin service, similar to Swarm, but implemented as a pure Web client. You can watch the application in action.

It logs into your account on an ActivityPub server using OAuth 2.0. It then reads your inbox, filtering the activities there to only show geosocial ones. You can use the geolocation services in the browser, and the places.pub service for a place vocabulary, to find nearby places. You can then “check in” to one of the places, with a note, and control of the privacy of the activity.

Geosocial activities are part of the core Activity Vocabulary that underlies ActivityPub. But, they’re not as widely implemented as other activities in the vocabulary. This app is trying to change that, by making them available on the network, and making it easy to create them.

To test the client, your service will need to support:

• Webfinger (for login)
• ActivityPub API (“client-to-server”, “C2S”)
• FEP-d8c2 (OAuth 2.0 profile for ActivityPub API)
• proxyUrl (for fetching data from remote servers)

To test federation, your service will need to support:

• Receiving Arrive, Leave, and Travel activities
• Showing those activities to users

As of this writing, Mastodon does not work for either of these. If you want to test receiving federated messages, follow me on evan@onepage.pub . I’ve been using it a lot!

Code for the checkin application is here: https://github.com/social-web-foundation/checkin

This is my second ActivityPub API client (ap, the command-line client, was my first), and my first one for the Web. I found this process really fun and invigorating. I was able to create a new kind of social networking application (well, new on the Fediverse…) purely from the client side. The app saves no data to the server; everything is done in the browser.

Please reach out on GitHub or comment here if you want to work on interoperability. I’m happy to help debug connections if needed.

Hey, all! I’m seeking some help testing an application I whipped up for the Geosocial task force of the W3C Social Web Community Group. It’s called https://checkin.swf.pub/ , and it’s a barebones checkin service, similar to Swarm, but implemented as a pure Web client. You can watch the application in action.

It logs into your account on an ActivityPub server using OAuth 2.0. It then reads your inbox, filtering the activities there to only show geosocial ones. You can use the geolocation services in the browser, and the places.pub service for a place vocabulary, to find nearby places. You can then “check in” to one of the places, with a note, and control of the privacy of the activity.

Geosocial activities are part of the core Activity Vocabulary that underlies ActivityPub. But, they’re not as widely implemented as other activities in the vocabulary. This app is trying to change that, by making them available on the network, and making it easy to create them.

To test the client, your service will need to support:

• Webfinger (for login)
• ActivityPub API (“client-to-server”, “C2S”)
• FEP-d8c2 (OAuth 2.0 profile for ActivityPub API)
• proxyUrl (for fetching data from remote servers)

To test federation, your service will need to support:

• Receiving Arrive, Leave, and Travel activities
• Showing those activities to users

As of this writing, Mastodon does not work for either of these. If you want to test receiving federated messages, follow me on evan@onepage.pub . I’ve been using it a lot!

Code for the checkin application is here: https://github.com/social-web-foundation/checkin

This is my second ActivityPub API client (ap, the command-line client, was my first), and my first one for the Web. I found this process really fun and invigorating. I was able to create a new kind of social networking application (well, new on the Fediverse…) purely from the client side. The app saves no data to the server; everything is done in the browser.

Please reach out on GitHub or comment here if you want to work on interoperability. I’m happy to help debug connections if needed.

@evanprodromou Is fep-d8c2 compatible with an oauth2 server like keycloak? I'm still having trouble understanding this, but my first guess is no. Hopefully I am wrong.

@evanprodromou Is fep-d8c2 compatible with an oauth2 server like keycloak? I'm still having trouble understanding this, but my first guess is no. Hopefully I am wrong.