pdx.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
pdx.social is a community for the Portland, Oregon, USA region. 🌲 Established April 6th, 2017 🌲

Server stats:

184
active users

question mainly to proponents of quote posts, but anyone can respond:

what would you say is the semantic relationship between a “quote post” and “the post being quoted”?

Are there any semantics at all, or is it a generic link/reference? What’s the difference between a “quote” and a “link preview”?

By semantic, I mean “meaning”. What does it mean to “quote” something?

If “quote posts” never existed, how would you design an equivalent?

EDIT: got plenty responses! see downthread for conclusion

Anthony Sorace

@trwnh @darius I think the difference between a quote post and a simple link preview is that I expect the quote post to be more “live“. I think from a semantic perspective that means that whatever software is doing the reading understand that it is a post. I think (but I am not certain) that was missing right now, semantically, is about the post part, not the quoting per se.

@trwnh @darius In practical terms, I think the most important implication of that is that when I tap on it, my client should open it as a post, not a webpage. Also, embedded media should be live.

There are open UI questions about whether other things about the quoted post should be inherited by the parent, things like content warnings (probably) and @ mentions (probably not), but those all depend on semantically understanding that the thing is a post to start with.

@a @darius so a link where the href is a “post” and then you fetch the “live” data instead of embedding a frozen repr