Homepage: G+/Twitter #io15 posts about ioweb2015 HOT 13 CLOSED

@crhym3 do we need backend work to pull-in and cache the latest 3-5 feeds from each account?

from ioweb2015.

Just a reminder that the intention is to pull from both Dev social channels
(G+ and Twitter) BUT filtered by the I/O hashtag: #io15. Otherwise, we
will be showing posts on the I/O Website that have nothing to do with I/O!

from ioweb2015.

Yeah, Jeff and I were both imagining a backend pulling for tweets and G+
and caching it for a little while.

There was only one concern: wouldn't tweets and G+ posts be identical or
are you guys going to post different things on different channels?
On 13 Jan 2015 18:50, "Monica Bagagem" [email protected] wrote:

Just a reminder that the intention is to pull from both Dev social
channels
(G+ and Twitter) BUT filtered by the I/O hashtag: #io15. Otherwise, we
will be showing posts on the I/O Website that have nothing to do with I/O!

Mónica Bagagem | Product Marketing - Developers |
[email protected]
[email protected]

Ping me on Hangouts http://hangouts.google.com\* | Find me on
*Google+
<
https://plus.google.com/u/0/117516490147085985454/posts?e=-RedirectToSandbox>

On Mon, Jan 12, 2015 at 4:16 PM, Eric Bidelman [email protected]
wrote:

@crhym3 https://github.com/crhym3 do we need backend work to pull-in
and cache the latest 3-5 feeds from each account?

—
Reply to this email directly or view it on GitHub
<
https://github.com/GoogleChrome/ioweb2015/issues/13#issuecomment-69673338>

.

—
Reply to this email directly or view it on GitHub
#13 (comment)
.

from ioweb2015.

Hey @monicabagagem, I think this question is for you :)

There was only one concern: wouldn't tweets and G+ posts be identical or
are you guys going to post different things on different channels?

from ioweb2015.

We usually post the same content on both channels - but written in
different ways given the character limitation on Twitter. There will also
be cases where we post only on 1 of the channels (e.g. during I/O days,
Twitter will probably have more activity than G+ since it usually has
higher engagement for real-time events).

Do we have a character limitation on how much content per post we can show
on the Website, or will we always be able to show the entire post? Also, if
the post has images, will we be able to pull those in?

If we think it will be too repetitive we can eventually consider pulling
only from Twitter. Let me check in with my team on this and I'll get back
to you.

from ioweb2015.

Talked to my team - we'll pull in Twitter posts only since they'll all have
the same size.
The top right of the announcement section should still link out to both G+
and Twitter.

from ioweb2015.

Since we're only Twitter data now, they do provide an embed stream for a given account:
http://jsbin.com/potehefoxo/1/edit?html,output

However, there's limited styling and only vertical orientation AFAICT. It's a pity we have to build so much when they provide this. We'll have to figure out quota bumps for their API. But that may not be an issues if the backend reads posts every so often and caches the for us.

@crhym3 This might be the next thing to tackle for backend work. WDYT?

from ioweb2015.

They do provide some styling, e.g. https://dev.twitter.com/web/overview/css but I guess yeah, it's limiting. Unless we hack and reverse-engineer their platform.twitter.com/widgets.js :)

Will work on this as the next thing. Shouldn't take long, actually, as I've already implemented caching and other things needed for this on the backend.

from ioweb2015.

@ebidel btw, another limitation of the embedded stream is you can't do filtering by a hashtag.
Anyway, working on adding this feature to the backend today.

from ioweb2015.

Right right. Still need the backend stream. I was just documenting EVERYTHING :)

from ioweb2015.

Just fyi we don't want to have heavy Twitter branding on the site - not
sure the embed would have more than we are planning?

from ioweb2015.

I think we're done with both the backend and frontend for now—at least for the initial revision.

from ioweb2015.

@jeffposnick - can you force the +googledevelopers and @GoogleDevs on the top right to open in new tabs instead of in the same tab? thank you!

from ioweb2015.