@jupiter_rowland@hub.netzgemeinde.eu if you're seeing Hubzilla backfill "bit by bit" it is likely doing inReplyTo traversal, which is what NodeBB does if it cannot find a resolvable context.
@QuadRadical Your server seems to be using a customised version of the nightly version of Mastodon, so it's possible some things are broken due either to customisation or due to being experimental.
@trwnh@mastodon.social there is, and it'd work in this case. The issue is that as the condition is evaluated, if it doesn't resolve to boolean true, then the case won't execute.
In the example above it resolves (in JavaScript, anyway) to "bar"
@deadsuperhero@social.wedistribute.org @atomicpoet@atomicpoet.org we use the same synchronization mechanism that PieFed and Lemmy use, FEP 1b12.
Let me know if the follow doesn't take for whatever reason.
@Ihazchaos There is a guide to different timelines here:https://fedi.tips/what-are-the-local-federated-home-timelines-how-do-i-stop-them-scrolling-too-quicklyYou don't specifically post to them, your posts will automatically appear (or not) depending on which visibility settings you use for your post:https://fedi.tips/who-can-see-my-posts-in-mastodon-how-do-i-send-dms-in-mastodon
@stevePlease note that the data.coop setup is publicly available at https://git.data.coop. It is based on ansible scripts, and should in principle allow to replicate the services with minimal effort.It is a stated purpose in the bylaws to cooperate with similar organizations and help them start up.@mjj @Ruth_Mottram
@KaraLG84 @anti42 At first I thought it was the link format and did a post about this a while ago, but apparently it's also affected by which hosting company your server uses.As far as I know there seems to be some inconsistency over how YouTube/Google treats communication with different hosting companies?
@AndyK1970 I tried looking on the source and it seemed to go straight from the Mastodon link to <body>?Sorry to hear it isn't working, weird to hear it works for some people though
@Kichae the github issue is here:
https://github.com/NodeBB/NodeBB/issues/13172
I think I found the source of the problem and fixed it. Try updating to the latest master or develop commit and see if it still happens.
