Discourse's Trust Levels are an interesting idea, but not one that is novel. It was lifted almost entirely from Stack Overflow. At the time, Discourse and Stack Overflow had a common founder, Jeff Atwood.

There's a reason Stack Overflow is rapidly fading into obscurity... its moderation team (built off of trust levels) destroyed the very foundation of what made Stack Overflow good.

I am also not saying that what we have now (first-mover moderation or top-down moderation granting) is better... merely that should you look into this, tread lightly.

Hey, yeah, please tell the Linux Nerds people to turn on federation!

Tell them Julian from NodeBB will help them get started 🤓

Your blogging options with federation are: WordPress, Ghost, and WriteFreely

I suppose, although in that scenario theoretically one could add as:sensitive to mark the status as CW'd? I don't think CW logic is even run for non-Notes at the moment, though I could be mistaken.

Not necessarily, no. Content warnings were implemented in Mastodon specifically as summary plus sensitive=true. Perhaps not originally, but that is enforced now (all CW'd posts from Mastodon are marked sensitive). Might be Mastodon will CW notes that don't have sensitive, out of caution, but this doesn't apply to non-Notes.

So a summary included in a non-Note is not CW'd by Mastodon currently.

Thanks. Yes, this is just how Mastodon renders content from Lemmy and Piefed at the moment.

Mastodon sees something that is not a Note, and says "I will treat it using a fallback mechanism. If it has a title, it is added to the top, I will add the URL back to the site at the bottom. If it has a summary, I will use that as the content"

Note that it does not use content, that's why there's no actual content. This is why the link preview also links back to Lemmy, not to the article itself.

nutomic@lemmy.ml and rimu@piefed.social can add this to their software, respectively, by populating summary. It can just be a copy of content, or it can be a summarization... or it could be the link to the article... anything goes really.

otter@lemmy.ca perhaps the quote posts are not related but some other changes bundled in that version release are?

Can you share the instance that user was on? It's worth checking out how their instance sees your post.

Mastodon did improve some non-Note handling characteristics, so it could be related!

I mean, yes, but there's also an implicit social contract with fediverse software that you probably shouldn't scrape without federating back...?

It's a good approach, it's exactly how NodeBB operates as well.

We have a FOSS software and we sell managed services for those who don't have the technical know-how.

Win-win.

Eh we all have our opinions although I feel Threadiverse rolls off the tongue better than forumiverse (or foriverse which I also dislike.)

Also the term predates Threads by a full year, but I refuse to let the term die because of that association.

> is that an issue for the Threadiverse? I thought all replies are collected by the host instance of the community.

You're not wrong about that. Threadiverse software (Lemmy, Piefed, and NodeBB too) use something called 1b12 to synchronize content between instances.

If you follow a community, you set up the synchronization from your server to that community from that point forwards.

This is similar, but not quite backfill, which is what happens if you follow a community mid-way and don't have any of that stuff from before.

Also you can't 1b12 synchronize with Mastodon, so that unfortunately is a dead-end, but you would hopefully be able to backfill from Mastodon.

Thanks for the link back, I appreciate it!

One neat side effect of this is that if the microblogiverse backfills from the threadiverse, and vice versa, then you have in effect built a bridge connecting the two disparate 'verses.

We're not there yet — this step only exposes conversational contexts so that consumers (like NodeBB) can backfill from them. Neither Lemmy nor Piefed have signalled intent to consume contexts yet, but as it is a relatively new extension, there is no telling what may happen in a week, a month, a year... :)

Also rimu@piefed.social is pretty darn responsive and if you as (very) nicely that would go a long way.