Taking a break from whitelisting/sandboxing and malicous users.

There are 1281 functions in the base package version 3.4.4.

Shiny app using safe(?) evalation of R code

As mentioned in Part 1, I’m looking into the idea of running R code which may originate from potentially malicious sources e.g. code from a web interface, or a database or even a tweet!

I’m looking into the idea of running R code which may originate from potentially malicious sources e.g. code from a web interface, or a database or even a tweet!

As described in a prior post I need to save some configuration objects from R into human-readable, human-editable format.

By default, blogdown in Rstats includes an RSS feed which is limited to just the first snippet from each article.

I made a simple package to encapsulate the dithering code from yesterday’s post.

I wanted to experiment with some dithering algorithms within R, but I also wanted complete control of the error diffusion.

I often use R list objects for storing configuration information within shiny apps. These are used to define multiple configuration sets and are usually saved to file. I then want to be able to edit the objects on the filesystem with a text editor.