Confirming at this time that at least the first URL shared does not get pulled in. Debugging.

ska which one doesn’t work?

Does it work here?

ska ok great news thank you!

ska I added some logic changes to better handle the locks… can you update to the latest version on the develop branch, and run NodeBB using ./nodebb dev?

ska Are you able to restart NodeBB without using the regular buttons from the ACP… just by stopping the service from the command line and restarting?

Then perhaps the locks will clear.

ska Unfortunately I can’t seem to reproduce the issue on my test instances (here and one other). The URL does seem to load fine.

Are you able to SSH into your forum server? Can you run curl -H "Accept: application/activity+json" https://www.lealternative.net/?p=63326 and tell me what shows up?

ska that is just a coincidence

baris added the additional logging at the same time

ska hmm that sounds like a regression, can you share the link to one of your posts here?

(Actually nevermind, I see it in OP.)

Can you try something for me… Can you restart NodeBB, and then search the direct post ID instead? (The one displayed in the log snippet you sent)

yasas turning on “I’m Under Attack” mode will likely block search engine crawlers as well.

It is meant to be used as a last resort.

eeeee /world hanging (but the rest of the site being accessible) sounds like an issue with the site, not with CF…

Other pages work ok?

eeeee we have “I’m under attack” enabled on CloudFlare.

It’s in response to AI crawlers, or potentially a DDoS. Not sure.

Either way it’s taking down this site when the traffic floods in.

thorrjo@lemmy.sdf.org I would say that I respect hongminhee@fedibird.com and a note was added to link back to the original.

I dislike AI generated content but am okay with it as long as it is labeled.

Hi deutrino@mstdn.io, please link out to the original, not this AI summarized copy.

https://community.nodebb.org/topic/18844/backfilling-conversations-two-major-approaches

This past June, I put together a write-up about two major approaches to backfilling conversations. The ability to properly backfill conversations means we will be able to make major inroads toward solving the feeling that the fediverse is quiet.

I, alongside several other members of the SWICG Forums and Threaded Discussions Task Force (ForumWG) have been working toward building implementor support for Conversational Contexts — the ability to explicitly classify a set of objects as belonging to a conversation, whether that be a topic, reply tree, or similar.

I am happy to report that we have made some wonderful inroads this past few months!

• jesseplusplus@mastodon.social has been working closely with the Mastodon team to allow software to backfill from Mastodon — this pull request has now been approved!
• I have been working with both nutomic@lemmy.ml and rimu@piefed.social to allow software to backfill from Lemmy and Piefed, respectively. (Lemmy PR, Piefed issue)

This marks a major milestone in the adoption of conversational contexts. With Mastodon on board backfill will be possible with the majority of the microblogiverse. With Lemmy and Piefed on board, backfill will be possible with the majority of the threadiverse.

Remember that pfefferle@mastodon.social was an early adopter of conversational contexts, and we have been able to backfill from WordPress blogs for quite awhile now (so that’s the blogiverse too)

I for one, am eagerly awaiting the next version of all of these softwares!!

D1re_W0lf those rules do not seem to help, I have enabled them as well.

yasas we have been seeing the same behaviour starting perhaps a week ago. The bursts seem to happen for maybe half a day and then disappear.

Since we wanted the site to start working quickly, we opted for an allow-list approach. We turned on “I’m under attack” mode, which has some unfortunate side effects (namely, causing federation to stop).

These are our rules:

(any(http.request.headers["accept"][*] eq "application/ld+json; profile=\"https://www.w3.org/ns/activitystreams\"")) or (any(http.request.headers["accept"][*] eq "application/activity+json")) or (http.request.method eq "POST" and starts_with(http.request.uri.path, "/inbox")) or (starts_with(http.request.uri.path, "/assets")) or (starts_with(http.request.uri.path, "/.well-known"))

This lets (respectively):

1. ActivityPub fetches
2. Same
3. ActivityPub publishes to the NodeBB inbox
4. Static assets
5. Certbot and webfinger (also for AP)

Jon-Pincus hey check out that topic loading from within this NodeBB

cc admin@discussions.thenexus.today