@trwnh @tech_himbo so I guess the answer is I don't know lol.

And maybe one solution is just covering the use case(s) we have today, and then evolve it as more people implement / we run into limitations.

@trwnh @tech_himbo hah maybe not! I'm sure there's a clever way to combine existing properties and indicate "this is a quote post". But I can also imagine this making things more convoluted for implementers than just using a new attribute.

I also think there will be large UI / display differences across different content types, e.g. short Note vs long Article. So a new attribute might be too limited to cover all cases (like multiple embedded quotes).

@trwnh @tech_himbo I feel like it could easily be an `attachment`, especially since that can hold many objects (useful for e.g. an `Article` that quotes many different objects).

Overall, I think it's just embedding a full object inside another. But I assume a new property saying "this is a quote" for the UI would be necessary.

@berkough So glad you like Write.as / #WriteFreely!

I've actually talked to @johnonolan and the folks at #Ghost before, when they helped us integrate cross-posting.

I'm pretty excited for the social reader they announced, as it should mean *all* long-form content in the fediverse will get really interesting. I reached out to them this week about working together -- think we see it as more about collaboration than competition

@molly0xfff