Ah yes, the oscillating state of the display of avatars in embedded timelines


So … once upon a time, a former version of the Timeline API allow for the display of avatars to be set to false. See here:

And here:

Apparently the setting went back and forth over a period of a year or two, starting in 2011, with the last update to the issue occurring over one year ago in December 2013. It’s 2015 now.

I looked through the HTML produced by the script, and the avatars seem to be set to two classes, avatar and u-photo. The below is simply the first instance of what I believe to be the relevant code—there may be another instance later on.

<img class="u-photo avatar" alt="" src="path/to/img" data-src-2x="path/to/img" data-scribe="element:avatar">

In an external stylesheet, I have declared the following:

.u-photo, .avatar {
	display: none !important;

I’m guessing, that since the CSS can’t actually alter the styling of the elements produced by the script, the above CSS has no effect (I tested it—it doesn’t)

There were some CSS hacks presented in one of the above threads, but since the API structure/semantics must have changed, the hacks no longer work.

Therefore, can you please re-re-enable the attribute that controlled the display of avatar?

Or would setting the desired attribute’s value to false (presumably setting the CSS to display: none;) break the layout generated by the script?

@episod had chimed in in both of the previous threads, but he may or may not still have control over this feature.

EDIT: Here are some guidelines/“rules” for the display of avatars on the Twitter platform.

If there is an exception made for phones or data plans with low bandwidth, is it really too much of a stretch to make an exception for the “typical” application of the API (i.e. a website being displayed on a desktop OS)?


All Tweets include author attribution including the profile image.

closed #3