Day #19 No Leakage allowed

July 27, 2016 19:05 UTC Team LoadToCode [2016]Subscribe to this teams's activities

Today we played around with the Twitter Ruby Gem and tweeted our first tweet from the terminal (YEAH). We had a great coaching session covering following: the Network tab of the browser inspector; how loading assets such as JS files and images from a third party leaks information about the browser user to that third party; how the iframe approach leaks information about the browser user to third parties; the fact that Javascript can replace the HTML in a page with different HTML; a rough approach for using the Twitter gem to hand-construct the HTML for a Twitter feed.
To ensure to include Twitter content to the LEAP Webapp without leaking any information to Twitter our next step is to build our own HTML-Frame and pass the Twitter Text-Content with usage of the Twitter Ruby Gem, later it has to be discussed how we deal with pictures since using Pictures from Twitter is a possible leaking area.
We ended up the day having another coaching session covering blocks within ruby.

Comments

You must be logged in to add a comment.