Twitter Module Stuck in "Loading" State

[Area51Brett]

As we all have seen the Twitter module on the bottom of the page is broken and stuck saying "Loading". It looks to be an issue with the Twitter API, we should either fix it or remove it from the site because currently it looks unprofessional.

[notslang]

See issue here: core2062/website#1
Closing because this is a duplicate and this project is going to be deprecated by core2062/website soon. Not even sure if it's worth releasing a new version of this to patch it.

[nightpool]

Reopened. core2062/website is no longer on our short term radar, and this needs to be fixed.

[agilgenbach]

Workaround discussed at:

seaofclouds/tweet#264

[agilgenbach]

Clicked closed by accident.

[nightpool]

Workaround not necessary. Haley said she'd be working on this tonight at
the meeting.

Unlike tweet.js, we're supported fine by Twitter's official API.

On Tue, Feb 11, 2014 at 2:51 PM, agilgenbach [email protected]:

Clicked closed by accident.

Reply to this email directly or view it on GitHubhttps://github.com//issues/26#issuecomment-34804676
.

[notslang]

except the official twitter widget doesn't fit as well into our site, and doesn't seem to offer styling.

[Featherdragon15]

The official widget does in fact offer some customization (like simple
things such as border color and link color) but honestly the dark theme
fits with our existing website just fine.

On Tue, Feb 11, 2014 at 3:17 PM, Sean Lang [email protected] wrote:

except the official twitter widget doesn't fit as well into our site, and
doesn't seem to offer styling.

Reply to this email directly or view it on GitHubhttps://github.com//issues/26#issuecomment-34808034
.

Haley Bates

#################################################################################################################################################################################################################################

[notslang]

This dark theme?

...That matches our theme even less than the default widget. It doesn't match the background color of the other content-boxes, uses rounded borders (unlike everything else on the page), doesn't use flat-buttons, has seemingly random margins (we use a standard measure of 10px nearly everywhere), and the font-sizes / fonts are different (twitter uses Helvetica Neue and we use Calibri).

But perhaps the worst part is that it introduces a scroll-bar just for the widget. I mean, how selfish is that?! Jeez, Twitter - you're just a widget, not the center-piece of the page! You don't deserve to have your own scrollable content-section; at most you get a "filler" space at the bottom of the page where you can be casually looked upon.

[Featherdragon15]

Yes, okay, thank you Sean, but honestly a working widget that doesn't fit
exactly with the theme is better than one that perpetually loads and never
displays tweets.

On Tue, Feb 11, 2014 at 8:07 PM, Sean Lang [email protected] wrote:

This dark theme?
[image: image]https://f.cloud.github.com/assets/1049204/2144447/51782afc-9387-11e3-8c0f-c6f35f52fe3e.png

...That matches our theme even less than the default widget. It doesn't
match the background color of the other content-boxes, uses rounded borders
(unlike everything else on the page), doesn't use flat-buttons, has
seemingly random margins (we use a standard measure of 10px nearly
everywhere), and the font-sizes / fonts are different (twitter uses
Helvetica Neue and we use Calibri).

But perhaps the worst part is that it introduces a scroll-bar just for the
widget. I mean, how selfish is that?! Jeez, Twitter - you're just a widget,
not the center-piece of the page! You don't deserve to have your own
scrollable content-section; at most you get a "filler" space at the
bottom of the page where you can be casually looked upon.

Reply to this email directly or view it on GitHubhttps://github.com//issues/26#issuecomment-34831709
.

Haley Bates

#################################################################################################################################################################################################################################

[notslang]

Or we could just remove the widget entirely... after all, we only tweet like 2 times a month.