julian

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!

Everyone’s hilariously ragging on OP for setting up a federated instance with dubious uptime, and I’m sittin’ here thinking that it just reminds me of me when I was a young kid hacking around with software.

Back then I set up a mediawiki server with very dubious uptime. Was fun 😂

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.

Can you not call fetch() to do a HEAD call? Maybe I’m mistaken about it but it should be ok.

CORS is indeed a wrench that gets thrown in when you least expect it…

It took me a minute to find, but it is detailed in evan@cosocial.ca’s write up about HTTP Discovery of ActivityPub Objects.

This is probably exactly what you’re looking for.

https://swicg.github.io/activitypub-html-discovery/

I think your current approach has merit but is limited. If you know the instance software by URL and can resolve it using path matching without the use of a pre-flight request, that’s absolutely a better way forward. The downside is you have to know the URL patterns of every software. You’ll never “catch 'em all”!

However, if that method fails, doing a pre-flight check to grab Link also works and is a viable way forward.

You can test against NodeBB users or posts.

admiralpatrick@lemmy.world I think you would be better served by checking for the Link header. NodeBB and WordPress do it, if that gives you some idea of implementation?

Okay that’s fair.

I still think that shying away from the term would just be letting Meta win.

Might be we have to add qualifiers every time we say “threadiverse”…

• threadiverse (not that threads)
• threadiverse (lemmy/piefed/mbin)

Then again I suppose if you have to do that then that defeats the purpose of the term, doesn’t it.

Do you have occasion to talk about the threadiverse to people who do not use threadiverse software?

I usually find the conversation is much more elementary (i.e. “what are open networks”, “what is the fediverse”) and I’d never get into discussions about what the subset of the fediverse known as the threadiverse, is.

blaze@lemmy.zip there’s nothing specifically precluding Lemmy and Piefed from following users.

You can follow users on NodeBB, and in fact because I did worked on Mastodon microblog interop first, the software only gained the ability to follow a category relatively recently.

So dessalines@lemmy.ml has a point about it all being the fediverse, because some of what separates Lemmy/Piefed/mbin and Mastodon are artificial.

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.

Those are all very good questions, and exactly the sort of things that would be discussed at the ForumWG.

Backfill is just one of the things (the main thing, currently) we touch on, but one of the more important ones, because the potential to ensure you have the entire conversation is important from a data completeness standpoint.

The thing to remember is that there’s no one “owner” of a conversation. Right now it’s a pretty loose association… individual posts and notes can declare that they are part of a context, even if that isn’t the case. This beats the current system where there is no association at all.

The difference here is that as a consumer of backfill, I can actually go to the context and verify this. We can extend this later on with context ownership, and defer responsibilities like moderation, interaction policies, forking/merging, etc.

The long view of this is we intend to increasingly solidify the association between context and object over time.

Combining notification streams is precisely the mission statement of UnifiedPush.

The fact that you name dropped NodeBB (a good example), Flarum (which has no working federation), but did not mention Discourse (which has only partially working federation and limited threadiverse support) gives me the warm and fuzzies 🤣