Apparently, Threads generating image urls with a short lived signature in the url. Since we directly fetch images on clients, there image requests fails with 403 response, with text response "URL signature expired"
And the result is, even avatars of the Thread accounts are not visible at all.
Here an example image url for the avatar of this account:
https://scontent-fra3-1.cdninstagram.com/v/t51.2885-19/358167676_653742456773330_2810549543525031296_n.jpg?stp=dst-jpg_s403x403_tt6&_nc_cat=101&ccb=1-7&_nc_sid=bf7eb4&_nc_ohc=tr9zLqqj9RYQ7kNvwHKN_dm&_nc_oc=AdmiOy3aPUShjCq1ke-2hrD5eFsPpA0K3Ae_D2VUdk1-QkC8MKUCtLDc4kwaChjGqmg&_nc_zt=24&_nc_ht=scontent-fra3-1.cdninstagram.com&edm=AIRTincEAAAA&oh=00_AfInmCG55DECiFqpaWhBFRbHBn5TqWdQPD477gGC4QF3yQ&oe=68438007
Mastodon doesn't have this issue because it fetches and stores all of those images on its own. Here is the same Threads account on Mastodon Social: https://mastodon.social/@calm@threads.net
Apparently, Threads generating image urls with a short lived signature in the url. Since we directly fetch images on clients, there image requests fails with 403 response, with text response "URL signature expired"
And the result is, even avatars of the Thread accounts are not visible at all.
Here an example image url for the avatar of this account:
Mastodon doesn't have this issue because it fetches and stores all of those images on its own. Here is the same Threads account on Mastodon Social: https://mastodon.social/@calm@threads.net