I've had two people message me in the past 2 days indicating that embedded Tweets are not rendering properly for them in the forum. Is anyone else having this problem? I am not able to replicate it with FireFox, Chrome or Edge. I don't have access to Safari for testing.
I've tried reloading the page, checking for extensions, checking my settings, deleting cookies and all the other recommended stuff but nothing is working.
If a thread has an embedded tweet it never loads and keeps me from seeing the rest of the thread and keeps me from posting in it.
It's basically making the Star Crossed forum inaccessible to me because most threads have embedded tweets.
Have the issue with Chrome running on an iOS device as well as on Safari and Chrome on MacOS. Seems to be something specific to the Apple OS(s), not the browser.
I think it's part of their privacy protections. I'll be able to dig into it soon. The MacBook Pro M2 I ordered should arrive tomorrow and I should be able to spend some time diagnosing it this weekend.
I use my laptop (not a Mac) to join in here. I always have to "refresh" the embedded Twitter links. Is there anything I can adjust in the settings to prevent this respectively see the preview immediately when I join the topic?
It's probably a general warning I could skip with the appropriate settings. But I hadn`t had this issue before you reshaped ADT (?) or someetime this year.
I wonder why this warning appears here even for those previews I have already clicked before.
That's a Twitter warning. It has nothing to do with Adult DVD Talk. It means the poster has it marked as adult content. On Twitter, there is an option not to display the warnings. However, you aren't seeing it through your Twitter account so the warning is always there.
It's not ADT. It's Twitter. I think over the course of the past year or year and a half they have been getting much better at automatically detecting adult content and flagging tweets/twitter accounts as 'sensitive content'. They don't want to accidentally trigger some snowflake.
I'm realizing now that Twitter has drastically changed the code that is rendered as part of a their Tweet Embed widget. I'm not sure when this changed. There's code in the ADT forum that used to programmatically click the "view" button on sensitive content. That auto-click code stopped working with the new Twitter code. I'll dig into this a bit and see if I can come up with a work-around.
The old Tweet rendering system plunked the HTML directly into the page which made it accessible to scripts in the forum. The new Tweet embed features insert an inline frame served by Twitter's servers. The content of that Iframe comes from a non-adultdvdtalk domain which makes it impossible for me to write code that manipulates the content in the inline frame. (It's a security feature built into browsers.)
I'll need to look into using Twitter's API directly for displaying Tweet content directly in the forum instead of using their embed widget.
I'm talking about the Tweets not rendering/Safari crashing problem.
I'm not able to do anything about the sensitive content thing without completely rewriting the Tweet embed system. And what I would end up writing would remove the personalization that's provided by Twitter's code. All Tweets would be rendered as though the viewer does not have a Twitter account.
To answer your question, everything now seems fine on my end with Tweets rendering.
However I am having an issue with one tweet not rendering in both the Leah Gotti and All Things Lesbian threads and those were the same posts by Ironknights so I'm thinking the issue my be on his end and not on the board's end.
Can't seem to use the tweet function without a "[Tweet is no longer available]" .
Last night, while operating without sleep, I tried to post a link but used the tweet function instead resulting in several 500 errors because I thought it was a caching issue.
Today I tried to embed a tweet, first one since a couple of weeks and I wondered about this massage. Does it has anything to do with Twitter's new policy or is it really a choice of the pornstar (it's Scarlit Scandal and I have embedded quite a lot of her tweets so far)
Sorry for asking, but I only use Twitter to check some news of my favorite pornstars.
Seems like the Twitter embed API is no longer functional. This could be temporary, or maybe Elon wants us to pay? If this continues I'll remove support for tweet embeds in the forum.
There's a 'new' Twitter API subscription plan available that's only $100/mo. Unfortunately that subscription only supports the new version 2 of Twitter's API. All of the existing Twitter integration uses the older v1.1 API. I'm working on updating the methods that ADT uses to talk to Twitter's API services.
I have updated the code that automatically Tweets out new reviews to use the new API function calls. But I have no idea why the forum code is randomly broken. The forum uses Twitter's free oEmbed API. Maybe the oEmbed developer docs haven't been updated yet. According to those docs there's no API account required and there are no rate limits. I'm guessing the random problems with Tweets in the forum is that Twitter is just a shit show lately.
I have updated one thing to maybe help accommodate the shit show: the forum will cache a valid Tweet for 30 days instead of the value Twitter returns for cache expiration. This way the forum won't re-check the existence of a previously-valid Tweet for at least 30 days.