@blag check out common place by @dajbhttps://commonplace.dynamicskillset.com/

@darius I had a typo in there. It should have said:"It separates the user's content FROM the front-end related functionality"

@dmathieu @mariusor Thank you, I successfully followed the actor.

@christopher Yes, I think so.

@smallcircles @nik @reiver JSON vs JSON-LD is a red herring tbh. The real question is, "do you recognize that other people might do things differently"? If you do, then you recognize that conflicts may arise, and you can try to resolve the conflict. But if you don't recognize even the *possibility* of a conflict, then it's painful for everyone involved.

@light Phanpy client has "Catch-Up" page which is an interesting step in the direction of non-chronological feeds. I am thinking about implementing something similar.

@fresseng@universites.social @hci@micro.blogs.princeton.edu I've been using Bonfire daily for months now. It's fantastic and if you want to help shape an incredible piece of emerging technology, this is a great opportunity!

@seanm Since you're obviously smarter than the Masto team, why don't you code that up? The API is stable and well documented.

Thanks everyone. It's a key ID. The reason you think it's an actor ID is that Mastodon uses a fragment id for it. But the id is for the key, not the actor.I appreciate the conversation!

@hongminhee ah so you had already implemented Quote Posts but not using the FEP-044f, does other server software supports your current style of QPs?

Oh, and if you're using an AS2 type, you don't have to worry about the extra context URL, obvs: { "@context": "https://www.w3.org/ns/activitystreams", "type": "Person" }

@yezanek Post about your thoughts and progress.If you use the #FediDev hash-tag, other Fediverse developers will see it, too.