February 13, 20251 yr comment_1787108 Can we just turn off embedding from x? It's simply not working worth a shit. A link that I can right-click and open in a new tab is sufficient. I don't blame @Griever btw. He's cool. Report
February 14, 20251 yr comment_1787128 I appreciate the shout-out, @CincyInDC. I do apologize for all of the blank posts. What I don't understand is, I follow the instructions on the other thread about embedding the tweets, the tweet is successfully embedded, interactive, etc. A couple days go by and the tweet is just...gone. Blank space as you illustrated in your screenshot above. Go has said it is on Twitter's (or X's) side so not sure what to do. So as of 2/14, the tweet below is fully embedded and visible: This is a tweet from the official, verified Bengals account regarding Al Golden. I can understand if they deleted the tweet later on, or edited the tweet later on that the embedded version here may disappear, but from what I've seen it doesn't have to do with that... Report
February 14, 20251 yr comment_1787129 So I guess long story short, if anyone ventures into this thread let me know if just taking screenshots of tweets is the best alternative due to the instability Report
February 16, 2025Feb 16 comment_1787234 word on the street is the embeds work if you replace x.com with twitter.com in the embed link. not sure if it would work but i could add x.com to the bad word filter and replace it with twitter.com i dunno... Report
February 28, 2025Feb 28 comment_1788066 On 2/15/2025 at 11:25 PM, GoBengals said: word on the street is the embeds work if you replace x.com with twitter.com in the embed link. not sure if it would work but i could add x.com to the bad word filter and replace it with twitter.com i dunno... Thanks for this, Go. I have been editing to twitter.com and they are embedding as expected, hopefully they stay visible (unlike x.com's) Report
April 15, 2025Apr 15 comment_1792192 Testing something: (x.com address embedded) (twitter.com address embedded) Report
Archived
This topic is now archived and is closed to further replies.