@evan I’ve been slowly building a client side blogging tool and it’s targeting ActivityPub first.

@evan considering the big drive currently building up on the #ATProto protocol, and given the proximity between AP and AT, would an #ActivityPubAPI service make any sense for #Bluesky / #Eurosky ?

e.g. an AP-API enabled PDS – if that would mean anything

cc: @eurosky.social

Agent at correspondents' dinner was hit by bullet from suspect's shotgun, prosecutors say
https://www.cbc.ca/news/world/white-house-correspondents-dinner-suspect-secret-service-agent-buckshot-9.7186105?utm_source=flipboard&utm_medium=activitypub

Posted into World @world-cbcnews

Anyway, social API haters have no place in my inbox.

Servers that support their own API, plus RSS, can definitely handle adding the full ActivityPub API.

There's more to do -- OAuth, rate limiting, and so on -- but it's not huge.

People seemed to get caught up on the idea that implementing the ActivityPub API requires dumping any other API that is implemented. Definitely untrue!

Even considering the maintenance load, it's not a huge lift. The read-only part of the API has to be implemented for the federation protocol anyway.

Implementing the read-write part of the API just means adding a single POST endpoint for the actor outbox, with some kind of switch statement on the 10 activity types (and ~3 undo types).

@evan assuming the post was public, sure.

How else would we convince people who use other platforms that there's actually stuff worth looking at on here?

I'd include a link to the original but wouldn't count on the viewer's platform interface to parse it.

For webpage content, I'll embed, which preserves the original author's ability to change privacy settings.

I'm half way to understanding Zeno's paradox

@6lr61 🙏🏼