jwildeboer@social.wildeboer.net I propose we nickname the new one the first 'murican pope.

britt@mstdn.games to be fair, the reason this happens is because Marketplace lets you press the button to send the quick response, but doesn't open the chat, so people just keep browsing.

It's a dumb UX and it only barely works at that.

fediforum@mastodon.social thanks, I was wondering

> The ALICE analysis shows that, during Run 2 of the LHC (2015–2018), about 86 billion gold nuclei were created during the four major experiments. In terms of mass, this corresponds to just 29 picograms (2.9 × 10-11 g). Since the luminosity in the LHC is continually increasing thanks to regular upgrades to the machines, Run 3 has produced almost double the amount of gold that Run 2 did, but the total still amounts to trillions of times less than would be required to make a piece of jewelry.

We're all gonna be RICH

cadey@pony.social

trwnh@mastodon.social before, I was not sending Accept at all, now I am sending application/jrd+json.

FWIW testing with cURL showed the same Bad Request with application/json.

thisismissem@hachyderm.io yes, but... that takes effforrrrrrrtttt

Anyway, ding ding ding, application/jrd+json was it

thisismissem@hachyderm.io yeah, I tried sending Accept too, which also fails. Will try the suggested type.

The library we use just blanket sends content-type because we're usually POSTing haha. Shouldn't hurt to include it, but who knows.

Does anybody know what exactly Pleroma needs for a valid Webfinger check? I'm attempting to figure out why @jmtd@pleroma.debian.social won't resolve in NodeBB, and it's because the webfinger call returns 400 Bad Request.

NodeBB is calling https://pleroma.debian.social/.well-known/webfinger?resource=acct%3Ajmtd%40pleroma.debian.social with User-Agent and Content-Type headers (curiously, it's not sending Accept, but it also fails if that header is set, so that's irrelevant.)

Navigating to that webfinger url in the browser returns XML, which is but I'm not even getting that when NodeBB makes the call.

deadsuperhero@forum.wedistribute.org you can use the latest master or develop branch commits if you want to try out the fix ahead of time.

Oh, @icaria36@the.socialmusic.network is running Discourse. Well, all bets are off then

@deadsuperhero@forum.wedistribute.org @icaria36@the.socialmusic.network are the two of you using v4.3.1? That's the latest version, although the very latest includes some important fixes that might actually be related to these issues you're seeing.

For now I also want to make sure neither of you are using the category sync feature.

@silverpill@mitra.social is that part of the nodeinfo spec?

I haven't looked into the differences between their implementation and how groups are implemented using 1b12, but what I have discovered is that the 1b12 community is much larger than I gave it credit for.

@projectmoon@forum.agnos.is said in Updates to the world page:
>
>
> Also, are there plans to merge the federation synchronization and new remote category following stuff together into one cohesive set of functionality?

Yes... the remote category functionality supercedes the category sync functionality in some ways, but there is still a use case for it.

Most likely I will need to develop proper support for cross-posting (at least locally), and that would work well with the remote category functionality, so that topics are cross-posted to the synchronized category, instead of moved.

That's correct, that category wasn't federating, but it is now

Were there other categories breaking?

@kirkmoodey@universeodon.com yes, Mastodon compatibility is lacklustre but that's partly because the architecture of Mastodon doesn't lend itself well to categorical organization. That's not a criticism, merely a difference that we have to consider.

Currently, when a user addresses multiple communities, then the existing software (NodeBB included) uses the first one. How the rest of the addressed communities are handled is what's of interest here.

@iso@lemy.lol what's a "lemmy-like" PM I think this explains why I can't log into the site.

@ludrol@szmer.info yes, you're right about that. The silver lining here is that we're at a point where the major players' implementations are local-only, so we don't have to work around with a pre-existing implementation and ensure compatibility.

The second point is that a "cross-post" could have multiple meanings, including manually creating a new post about a link already present in multiple communities. What I'm hoping to describe is a common way that items can be cross-posted natively between instances, while hopefully preserving their reply-trees.