Discussion
most of Mastodon’s implementation of the Oembed API is actually really good. they’ve worked really hard to limit their dependency on javascript to render the embeds. that means fast loading toots.
but forcing a QT to be triggered by a boost kills OEmbed’s ease of use. we should be able to cut & paste a link and be done with it.
it also subverts one of the most important aspects of writing: freedom to attribute via a quote, citation or blockquote… 🧵
ONLY PUBLIC TOOTS SHOULD BE QUOTABLE
yes, even the “quiet” ones. that’s what an OH (overhead) statement is: something said quietly in public.
if we go back to the metadata image, there is no META for VISIBILITY. each toot should have in their metadata their visibility declared:
PUBLIC - full visibility
QUIET PUBLIC - stripped of attribution
PRIVATE - no visibility
that would set the IF and HOW a toot’s card is rendered… 🧵
most of Mastodon’s implementation of the Oembed API is actually really good. they’ve worked really hard to limit their dependency on javascript to render the embeds. that means fast loading toots.
but forcing a QT to be triggered by a boost kills OEmbed’s ease of use. we should be able to cut & paste a link and be done with it.
it also subverts one of the most important aspects of writing: freedom to attribute via a quote, citation or blockquote… 🧵
Mastodon’s implementation of consent for #quote #quotedToots needs further development.
METADA is created with XML because, as opposed to HTML, you can create your own meta tags. this should make it possible to set the quoteability based on its visibility. it would also correct for people’s wrong interpretation of public/private.
if you can be boosted, you can be quoted. this shouldn’t be controversial.
again: to be able to give attribution is a core principle of #freedom of the #press /🧵
@blogdiva Yo, like I fucking TOLD THEM, I've been telling them for some time after I added a custom CSS hack to display the full text of the post that was already there just hidden via CSS that what most people want with quote posts is to be able to see the entire post that's been quoted. That's it.
Just a preview pane.
That thing that Phanpy has been doing for a long ass time.
But they had to build this elaborate thing and while that's nice and all, does that mean Phanpy should stop showing the full preview when someone embeds a link, or....?
@blogdiva SO MUCH DEV TIME was spent on this.
@blogdiva You know that annoying thing where there's a link to a fedi post and it takes you to another server and you're not logged in there so you can't interact with that?
Phanpy solved that, too, over a year if not years ago.
That would have been a great UI feature to spend time on.
@blogdiva I think you can cut-and-paste the link and have it be treated as a quote post ...
EDIT: apparently not! looks like I was confused about that?
A space for Bonfire maintainers and contributors to communicate
