-
Notifications
You must be signed in to change notification settings - Fork 122
Homepage: G+/Twitter #io15 posts #13
Comments
@crhym3 do we need backend work to pull-in and cache the latest 3-5 feeds from each account? |
Just a reminder that the intention is to pull from both Dev social channels |
Yeah, Jeff and I were both imagining a backend pulling for tweets and G+ There was only one concern: wouldn't tweets and G+ posts be identical or
|
Hey @monicabagagem, I think this question is for you :)
|
We usually post the same content on both channels - but written in Do we have a character limitation on how much content per post we can show If we think it will be too repetitive we can eventually consider pulling |
The endpoint is accessible at `/api/extended`. The backend returns a JSON file stub located in `app/temporary_api/ioext_feed.json` in `dev` mode, while fetching real entries from a spreadsheet feed using backend/service-account.pem private key in `stage` and `prod`. An encrypted version of the service account private key is in this PR. It's been encrypted with a 64-chars pass phrase using AES-256 algorithm. This PR actually contains more than is needed for just fetching a sheet list feed, but we'll definitely use it later, in #13 and phase 2. Closes #106
Talked to my team - we'll pull in Twitter posts only since they'll all have |
Since we're only Twitter data now, they do provide an embed stream for a given account: 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? |
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. |
@ebidel btw, another limitation of the embedded stream is you can't do filtering by a hashtag. |
Right right. Still need the backend stream. I was just documenting EVERYTHING :) |
Just fyi we don't want to have heavy Twitter branding on the site - not |
I think we're done with both the backend and frontend for now—at least for the initial revision. |
@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! |
For homepage, query
@googledevs
and+GoogleDevelopers
for latest few posts with hash tag#io15
. We should eventually setup a server-side cron for this.The links should be clickable in tweets and the username links to the tweet, just link twitter does.
We should hide the section until there are at least 3 tweets. That'll be easy with
<template repeat="">
and<template if="{{}}">
.The text was updated successfully, but these errors were encountered: