<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rvest on rostrum.blog</title>
    <link>https://www.rostrum.blog/tags/rvest/</link>
    <description>Recent content in Rvest on rostrum.blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Sat, 10 Jul 2021 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.rostrum.blog/tags/rvest/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Decay is inevitable, accept {linkrot}?</title>
      <link>https://www.rostrum.blog/2021/07/10/linkrot/</link>
      <pubDate>Sat, 10 Jul 2021 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2021/07/10/linkrot/</guid>
      <description>tl;dr I wrote a little function to check web pages for link rot and put it in the tiny R package {linkrot} in case you want to use or improve it.
 Page not found You’ve clicked a link before and been taken somewhere you weren’t expecting. Sometimes it’s because you’ve been rickrolled,1 sure, but content on the internet is constantly being moved or removed and links break all the time.</description>
    </item>
    
    <item>
      <title>{altcheckr}: check image alt text from R</title>
      <link>https://www.rostrum.blog/2019/12/08/altcheckr/</link>
      <pubDate>Sun, 08 Dec 2019 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2019/12/08/altcheckr/</guid>
      <description>tl;dr I’ve made a small R package called {altcheckr} that checks the accessibility of images on web pages. It has functions that (1) scrape attributes from HTML  elements on a web page and (2) apply simple rules to indicate the suitability of the alt text provided. To use:
remotes::install_github(&amp;quot;matt-dray/altcheckr&amp;quot;) images &amp;lt;- alt_get(&amp;quot;https://www.bbc.co.uk/news&amp;quot;) alt_check(images) I’m not an expert and the package has not been user tested.
 Accessibility A web site is accessible if everyone can engage with its content.</description>
    </item>
    
    <item>
      <title>A year of rostrum.blog</title>
      <link>https://www.rostrum.blog/2019/04/14/one-year/</link>
      <pubDate>Sun, 14 Apr 2019 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2019/04/14/one-year/</guid>
      <description>Happy first birthday 🎉 One year, visualised There’s been 27 posts on rostrum.blog in its first year, so about one every two weeks.
This interactive graphic shows the publishing frequency, where each dot is a post and the x-axis is time. Turn your mobile to landscape mode to see it in full.
 {&#34;x&#34;:{&#34;data&#34;:[{&#34;x&#34;:[17635,17648,17663,17670,17676,17687,17708,17712,17724,17729,17738,17786,17798,17817,17839,17856,17860,17864,17889,17900,17914,17928,17941,17954,17959,17973,17993],&#34;y&#34;:[1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1],&#34;text&#34;:[&#34;publish_date: 2018-04-14
title: R Trek: exploring stardates&#34;,&#34;publish_date: 2018-04-27
title: TWO DOGS IN TOILET ELDERLY LADY INVOLVED&#34;</description>
    </item>
    
    <item>
      <title>Web scraping the {polite} way</title>
      <link>https://www.rostrum.blog/2019/03/04/polite-webscrape/</link>
      <pubDate>Mon, 04 Mar 2019 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2019/03/04/polite-webscrape/</guid>
      <description>Reaping with rvest Ah, salutations, and welcome to this blog post about polite web scraping. Please do come in. I’ll take your coat. How are you? Would you like a cup of tea? Oh, I insist!
Speaking of tea, perhaps you’d care to join me in genial conversation about it. Where to begin? Let’s draw inspiration from popular posts on the Tea subreddit of Reddit. I’ll fetch the post titles using the {rvest} package from Hadley Wickham and get the correct CSS selector using SelectorGadget by Andrew Cantino and Kyle Maxwell.</description>
    </item>
    
    <item>
      <title>Graphing the Relayverse of podcasts</title>
      <link>https://www.rostrum.blog/2019/02/14/relayverse/</link>
      <pubDate>Thu, 14 Feb 2019 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2019/02/14/relayverse/</guid>
      <description>The Relay FM podcast network, visualised. View it here.  tl;dr I made an interactive graph network of the podcast host relationships on Relay FM using R. You can interact with it in a separate window and find out below how it was made.
I refreshed the data and style of the visualisation on 02 Jan 2020.
 Podcast networks Podcasting is becoming big business. Music-streaming giant Spotify just acquired the podcast network Gimlet for a reported $200 million.</description>
    </item>
    
    <item>
      <title>Travel the NBA with {rvest}, {leaflet} and {osrm}</title>
      <link>https://www.rostrum.blog/2018/12/24/nba-travel/</link>
      <pubDate>Mon, 24 Dec 2018 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2018/12/24/nba-travel/</guid>
      <description>Classic Jazz: Stockton to Malone for the dunk (via Giphy)   Note
The original version of this post (December 2018) used the {gmapsdistance} package. I updated it extensively in 2020 to use the {osrm} package, which doesn’t require an API key nor billing details.
 tl;dr The {osrm} R package can retrieve from the OSRM API the travel duration between points.</description>
    </item>
    
    <item>
      <title>R Trek: exploring stardates</title>
      <link>https://www.rostrum.blog/2018/04/14/r-trek-exploring-stardates/</link>
      <pubDate>Sat, 14 Apr 2018 00:00:00 +0000</pubDate>
      
      <guid>https://www.rostrum.blog/2018/04/14/r-trek-exploring-stardates/</guid>
      <description>Captain’s log  Star date 71750.51. Our mission is to use R statistical software to extract star dates mentioned in the captain’s log from the scripts of Star Trek: The Next Generation and observe their progression over the course of the show’s seven seasons. There appears to be some mismatch in the frequency of digits after the decimal point – could this indicate poor ability to choose random numbers?</description>
    </item>
    
  </channel>
</rss>