@thisismissem@hachyderm.io said in Quoted posts:

does it make sense on a forum to prohibit quoting of you?

I will say that back in the day nobody ever thought about this particular use case. Also me earlier:

Another upside is that a copy-paste of a post preserves that post to history. That can be useful if the quoted user tries to edit their post later, etc.

Even writing that now I was struck by how problematic that can be. It just simply wasn't something you thought about back then, but the right to be forgotten needs to be addressed too.

I'm not weighing in on that issue specifically, but just remarking on how our approaches to public discussions have changed over the years.

cc @renchap@oisaur.com

@julian Here is one post with screenshots: https://indiehackers.social/@leroy/111746082634398937

I ended up not continuing with this idea. I still really like the simplicity of it BUT it suffers from the fact that people might have auto-deletion of their posts, which can cause gaps in data quite quickly. Which goes against my love of forums (a trove of data for future ‘generations*’).

*generation in this use means a person looking for same knowledge, but it’s new to them

@renchap @julian @leroy

I feel like a first step we may be able to do is support <blockquote> and encourage clients to support that markup (currently @ivory doesn't support that html tag in content)

@thisismissem@hachyderm.io Yes, I've noticed that Megalodon also doesn't support blockquotes, but the web client definitely does (I just checked hachyderm), which is a great start.

@julian so perhaps more an advocacy thing than a feature change?

Little heads-up: So far, Hubzilla renders everything the way I guess it's intended. Nothing out of the ordinary.

@julian @trwnh @thisismissem

>How that is represented via ActivityPub is probably detailed in some FEP

FEP-e232? I think you can add content or summary property to FEP-e232 link to represent HTML content of a quote

@thisismissem @julian @leroy @renchap I take the same view as @leroy as well -- you can render replies as a rich preview above every post that happens to be a reply. Discord does this, for example. In fact, if Mastodon did this, then they would only need a way to tell when to insert such "quote replies" into timelines and when not to. It could be as simple as a boolean toot:quoteReply = true. With management of the `replies` collection via FEP-7458 (and some proof/stamp mechanism like FEP-0391).

@silverpill @thisismissem @julian I think you could define a Quote type that is a subclass of Link and use microsyntax to find-and-replace the blockquote with a rich entity with `content` or maybe even `preview`. But this generally makes sense only when you want that rich entity, and not just a "simple" blockquote.

Discourse for example uses [quote] tags kinda like bbcode, and they add metadata something like [quote author:someone,thread:2319,post:69] where the metadata is used in the preview.

@trwnh@mastodon.social part of the reason we don't do this special syntax is because we (probably) made the conscious decision to keep the composer as simple as possible so that end users wouldn't have to relearn a bespoke syntax.

... but I'm not really sure anymore. My rationale could just be post facto lol

@julian yeah, if you have a rich composer it's less bad. i don't think i've ever manually authored a quote tag in Discourse, for example. every single time i quote someone it's via the floating button that appears when you select something, or via the dropdown menu option

For reference, Hubzilla renders both the same way.

If you "share" someone's post (what Mastodon users call a "quote post") is basically just:

@channel@example.com 
[quote]Whatever they said.[/quote]

which gets translated to:

@channel@example.com
<blockquote>Whatever they said.</blockquote>

If someone quotes someone's post in a forum, it is the same exact thing.

And users can also add their own blockquotes to posts by using the BBCode [quote] tags too.

It's all blockquotes.

Note: This posts uses <code> blocks. This may not render properly on all platforms.