@bh4-tech I realised that a part of the issue was due to the fact that I was using cloudflare proxy. Disabling that improved the situation. Now, my instance does not crash on viewing threads media. Also, for every 3-4 media , 1 media file loads properly(link is not displayed, actual media is displayed). Maybe, admins should have the ability to set a custom timeout for the link preview plugin so that the success rate for viewing remote media becomes 100% as compared to current 25-33 %. @julian
bh4-tech
joined 1 year ago
@julian Yeah that worked for mastodon, but not for threads. Guess that's some problem on thread's side and not nodebb.
However, the remote media preview problem still remains https://community.nodebb.org/post/103782 . Guess you will need to cache remote media like misskey.
@julian https://www.threads.net/@khabydistas on threads and https://mastodon.social/@dansup on mastodon
@julian Are categories supposed to follow regular users from this 
screen in admin panel. Asking this because I tried putting a mastodon user profile link in the textbox but upon clicking on 'Follow' nothing happened. For threads, the request is pending(with some error, I guess) as you can see from the picture.
@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/________
Here is the link https://ekk.app/topic/e670e98f-c13f-4ab5-b174-96974ebca495/jay_shah_%E0%A4%95__%E0%A4%95_%E0%A4%B0%E0%A4%A8_%E0%A4%AE____
and here is the original post link https://www.threads.net/@dhananjay.naidu02/post/DHAlBHgzryu
I tried running with ./nodebb dev and although no response was received from site (pic above) no error message was also logged in console
@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.
Yeah, not an ideal experience. I guess a placeholder as suggested above would be a better experience, especially for users not familiar with concept of fediverse.
@bh4-tech Update: I think that community.nodebb.org is now running with latest commits from the develop branch and so remote images and videos can be viewed once we click on the attachment link. But I think the UX can be somewhat improved.
Current experience- A remote post contains a media file. The file(image) is not displayed below the text and only its link is displayed. An unaware user might not notice that it's an image and not click on the link thinking it's an external link and, in that case, will only see the text and so the post will feel awkward to the user.(I know that once any one user clicks on a link, the media gets loaded inline automatically for all other users, but even that also seems a good amount of friction). Also, if the forum is installed as PWA, clicking the media link will open it in a custom tab.
Possible improvement- Instead of the link, show a simmerring image loading animation(the one we see on instagram or youtube when images/thumbnails are loading) with the text "Click to view" and upon clicking on the animation the media gets loaded.
@julian Restarting also did not change anything.
Also, noticed that if a post on mastodon, lemmy or threads has an image, it is shown beside the topic headline as a thumbnail but is not rendered below the actual text as an image. I guess that once this problem is fixed, videos(or video links) will also get rendered. The same behavior is observed on both community.nodebb.org as well as my nodebb instance. Attaching screenshots of both-
1)community.nodebb.org with a lemmy post 
2)my nodebb instance with a mastodon post
view more: next ›
@baris Not related to this, but I am also facing a problem due to csrf token. I earlier used cloudflare SSL on my nodebb instance but now have turned it off because it was giving issues with loading media for federated accounts. My account was auto logged off and now I cannot login. Everytime I try to login, I get the error "Login Unsuccessful We were unable to log you in, likely due to an expired session. Please try again" and the url bar shows
This happens both for admin as well as non-admin user. I have turned on-off-on as well as restarted both nodebb and nginx but the problem remains. Any suggested solution?