| Website | https://eliocamp.github.io |
| Pronouns | they/elle |
| GitHub | https://github.com/eliocamp/ |
| Location | Australia 🇦🇺 (previously Agentina 🇦🇷) |
▶️ Videos from the rainbowR conference are now on YouTube 🎉
Catch-up with talks on wide-ranging subjects in R, Shiny, and working with LGBTQ+data, from our fabulous speakers including @hadleywickham, @jasminedaly, @hfrick, @oberman and @ursula.
https://www.youtube.com/playlist?list=PLaSZCD8_cwh0MOQf1m8DrLheH1Tu0g2o_
Based on the results and discussion, I'm turning cache on by default. The deciding feature was that the data itself doesn't really change; save an exceptional update to the data, a single request returns the same data every time, so it's not like there's a big rist of getting stale data.
I developed an #RStats package to get data from a remote service. Functions allow caching results, so that they will just return the saved files if the request is the same. I tend to be conservative and set the cache option to FALSE by default, but now I'm wondering if it would be more user friendly (and friendlier to the remote API) to set the default to TRUE.
What say the R community?
What is most terrifying about this is that people are seeing ads. Use an ad blocker, folks.
On closed platforms like android, you can use as guard DNS to block most ads.
https://hachyderm.io/@thomasfuchs/116262153401762539
https://adguard-dns.io/en/welcome.html
RE: https://infosec.exchange/@BleepingComputer/116260341395396371
"Satya Nadella says as much as 30% of Microsoft code is written by AI"
Google has news on what you will need to do for still being able to sideload apps:
* enable developer options
* confirm that you are not tricked
* restart phone and re-authenticate
* wait one day
* confirm with biometrics that you know what you are doing
* decide if you only want unrestricted installs for 1 week or forever
* confirm that you accept the risks
* enjoy the few apps that still have developers motivated to develop for a user-base willing to put up with this
Google: pay and register as a developer with us, or your users must wait a day after deciding to install your app.
No surprise that the alternative to handing over ID, money, and contractual agreement to Google is a hostile experience for users.
https://android-developers.googleblog.com/2026/03/android-developer-verification.html?m=1
RE: https://lipn.info/@clairemathieu/116254500918858625
"Whoever submits hallucinated references pretends to have a scientific foundation that doesn’t exist. This misleads reviewers and readers and undermines trust in science. This is an individual decision for which individuals are responsible. Structure may explain some things, but it doesn’t absolve. Individual responsibility remains."
I have my first research assistant and got an email from HR with a bunch of admin stuff I need to do.
I will never complain about software documentation ever again; this stuff is a nightmare. Acronyms are used all over with no explanation, instructions to go to some web service or other without a link to it, training materials so complicated that there are training materials FOR THE TRAINING MATERIALS. This is completely unintelligible.
rainbowR
Torsten Grote
Neil Brown
Nicolas Fressengeas