… all in one place …
I’ll edit the subject line.
Problems with inverted versions of a logo
https://twitter.com/opensrcdesign/status/868205626308087808 (2017-05-26) cropped representation of what I originally thought was a square logo. In retrospect it might have been cropped from the square part of a rectangular logo. At the time of writing, it’s inverted.
https://twitter.com/simonv3/status/855409535070195714 (2017-04-21) previously presented a black rectangle, now there’s a cropped representation of an inverted logo.
https://twitter.com/opensrcdesign/status/870281492433326080 (2017-06-01) cropped representation of a different inverted logo. I guess, the same inverted logo that appears almost white-on-white at Twitter: black rectangle, or cropping of different types of inverted logo, in some tweets that refer to pages in the discourse.opensourcedesign.net domain above.
Yesterday (2017-06-01) the result of http://iframely.com/debug?uri=https%3A%2F%2Fdiscourse.opensourcedesign.net%2Ft%2F-%2F130 was:
418 server error
Not long afterwards, I began getting
– for that particular debug URL and more generally, for http://iframely.com/debug. I wonder whether access is denied because we have overused the debugging service for URLs in a particular domain, or because I have overused the service from a particular IP address. For a few hours, http://iframely.com/ was unaffected but now (04:56 UK time) there’s 504, gateway time-out.
The behaviours with @staff -defined images at
discourse.opensourcedesign.net should be as good as with the set of admin/staff-defined images at, for example, Mozilla Discourse.
– in that example, a list of tweets, it’s probably normal for one to appear without an image because an adjacent tweet refers to the same topic. The tweet that is listed without an image does present its image when viewed as https://twitter.com/firefox/status/837044463864279048
https://twitter.com/search?f=tweets&q=discourse.mozilla-community.org offers a broader overview where most examples are OK, exceptions include:
– both of which present a generic page icon. @discourse that’s just FYI; I don’t suppose that the forthcoming deep fixes are intended to address such cases. (I treat the generic page icon as normal, not peculiar.)