@julian unfortunately, I think that’s true.

@dansup @reiver Ha! It wasn't me; it was the SWF.

@deadsuperhero @frequency thanks!

@SouthFresh @fedicon LOL. Yes

evan@cosocial.ca that’s cool, so hopefully I’ll have something to test against besides another NodeBB server

@julian@community.nodebb.org This is definitely something I’ve seen a lot of over the years. Take curation, for example. WordPress has a discovery portal for blogs and interesting content. So does Ghost. So does Medium. To some extent, so does Blogger. A lot of these platforms get caught up in self-discovery and promotion amongst their own kind, when they’d all clearly benefit from showcasing a wider part of the Web regardless of underlying platform. I really love the idea of Ghost’s “Reader View” which highlights articles from publications you’re subscribed to. It would be amazing to see this kind of utility and a social feed in all blogging platforms.

julian Those are not Lemmy communities but authors of a federated Wordpress blog: the author skariko is followed while the authors marcocalamari and fediverso remain in “pending”. On the other hand as far as PeerTube is concerned I just tried it and it did not give me any errors, in the next few days I will try to see if new posts also appear to me but it seems so: https://citiverse.it/category/framablog.audio@framatube.org Thank you

julian it’s possible? or retry follow requests?

Is there or should there be a distinction between the original and the mirrors? We have a conversation owner at the thread level (which is either the forum, subforum, forum category, or person who created the top level post, depending on the software). They determine the official moderated version of the thread since they can remove comments (although mirrors don't have to honor that). If we show that conversation on another server, technically that is a mirror of that thread, especially if you are throwing it in a category or displaying it under a hashtag. Should we be indicating that a particular thread was started on a particular forum (or category within a forum)? Should we be honoring the moderated version of the conversation from the original thread? The concept of mirroring threads across platforms is great for participation and censorship resistance, but it does make it unclear about who owns the thread from a moderation perspective.

julian@community.nodebb.org said in Backfilling Conversations: Two Major Approaches: > A number of implementors follow this approach to backfill, including NodeBB, Discourse, WordPress, Frequency, Mitra, and Streams. Additional implementors like Lemmy and Piefed have expressed interest. Is this implemented currently? One weakness I have noticed in NodeBB’s current federation is that posts which are in reply to a topic (e.g. a Lemmy comment) show up as individual threads until (or if) the root post of that topic shows up in the local NodeBB. It’s a bit confusing of a UX, I think. Because you think: (Before root post) Why is this a post that seems to be just a random comment? (After root post) Why did that other thread disappear and why am I seeing the same comment again?

@julian @mikedev Yes, if you receive an Announce(Create), and Create is not signed, then you need to retrieve this Create from its origin. When that origin server receives your signed GET request, it needs to verify that you belong to the group, but it might not have that information.

@mikedev @julianhen conversation containers are working correctly, you never need to backfill a conversation. It is all delivered to you.I think there is one case where backfill is necessary: public conversations that are not discovered through following (e.g. by retrieving an object by its ID).

Hello from Hubzilla!

@julian@community.nodebb.org Yeah, being able to treat Mastodon and Lemmy/mbin/piefed like a bulletin board continues to feel like magic.

That instance runs Lemmy 1.0 which is still in alpha state, and the frontend is not compatible yet. So only the api works there.

I’m assuming Unicode in handles is not allowed? At least by Mastodon. This user is not able to have their content federated because the username is all Hebrew (I think?) characters!