@julian This post as it appears on kbin.earth thinks it's from 11 months in the future, with a timestamp of 2026-02-27. It looks fine elsewhere though (e.g. on Lemmy). NodeBB has sent out some incorrect activities for this post, so I'm guessing that Lemmy fixed itself after processing a later Update, but MBIN didn't get it or didn't process it (I'm not that familiar with it, but it looks like no-one there is subscribed to either the category or you, so I don't even know how they created it in the first place)

@freamon thanks, will have to mock up an update and send it their way specifically I guess.

Lmao same, been like this on and off for a few days.

Same with me, but I'm on a MBin instance too

@julian My nodebb instance is able to federate with threads and so I get posts from there also. Media from threads come in extra long url, with a very long hash(I guess) after the actual resource, so this problem gets even more prominent there. Would be nice if this is solved soon.
Here, you can see the video url after the text of the post.

@bh4-tech does the video or whatever load properly after you refresh?

For mastodon based servers, media loads properly after refresh. For threads, my nodebb instance dosen't respond(Bad gateway cloudflare 502 cloudflare error) after refresh, so the only way I can access the media is clicking on the long link.
Both are non user-friendly UX, specially for those who are not accustomed to activitypub

I tried running with ./nodebb dev and although no response was received from site (pic above) no error message was also logged in console

@bh4-tech NodeBB crashes when you navigate to a post from Threads containing a link?

Can you share the link here? Will it crash? Let's see

Here is the link
https://ekk.app/topic/e670e98f-c13f-4ab5-b174-96974ebca495/jay_shah_क__क_रन_म____

and here is the original post link
https://www.threads.net/@dhananjay.naidu02/post/DHAlBHgzryu

@bh4-tech Now threads seems to have reduced the time for URL signature expiry and media files expire by 24 hrs @julian For this, the only workaround I think is that my nodebb instance will need to save(cache) the remote media as soon as it is received
Posting the link of a recent post below whose media has around 10 hrs more before it expires
https://ekk.app/topic/40fda023-3d00-42e1-ad8c-ca3973760012/________

An annoying bug thats in v4.10, which has been on / off in some of the previous versions...
When you post need to do page refresh for post to show.
This is true on mobile for new posts and edits

@eeeee if you wait, does it show up eventually?

@baris fixed a bug related to this as well, but this was before v4.1.0