There's a clearer definition that you might be more familiar with in section 2.3 of a familiar paper: tidy-data.pdf share.google/GlF5MJ73iS1a...
1. Each variable forms a column.
2. Each observation forms a row.
3. Each type of observational unit forms a table.

bsky.app/profile/jont...

It's specifically `.bsky` (with a period) so it won't show up in my Environment panel in RStudio (nor session variables in Positron, evidently, yay!) and generally stays out of the way.

I'm figuring out the most straightforward way to add "Google '{dataset description} controversy'" to my dataset todos in a way that I won't forget. I'm also going to try to make better use of the dormant `#club-tt_testers` on DSLC.io to review datasets ahead of time, now that I have a runway.

FYI, we've removed this dataset, after being advised of www.studocu.com/en-us/docume... (summarized here: researchblog.duke.edu/2016/10/24/d...). Sorry for accidentally embroiling you in controversy!

Because I didn't know better. Thanks you for this post! I've removed that dataset, and am working on improvements to my dataset submission review process to avoid repeating this mistake. If you identify an issue in the future, we'd love an issue or PR (github.com/rfordatascie...).

Yup! Ok, this works!

Can the uri in the {bskyr} result be used as the url for `reply`?

I don't think I needed an extra auth stepping, confirming

While digging in there to copy/paste the code I found a thing I started but forgot about 😁
bsky.app/profile/jont...

This is in a branch named "encounters" of a package I'm working on.

That's inside this:
```
if (interactive() && getOption("load_specials", FALSE)) {
## Fancy stuff
}
```

And at the top I have `options(load_specials = TRUE)`, so I can comment that out to turn off all my fancy stuff when I'm testing something.

This is how I learned that Rstudio shows the current branch in the title bar. Doh!

I have this in my .Rprofile to show branch & time in console on RStudio & Positron:
```r
prompt::set_prompt(
function(...) {
paste0("[", prompt::git_branch(), " ", format(Sys.time(), "%T"), "] > ")
}
)
```

That caveat is what has killed all of my time-tracking plans. How has it gone for you?

#TidyTuesday dataset curation PRs are #RStats only right now, but I'd welcome a PR to make it work for #PyData and/or #JuliaLang! You'd need to help me adapt the automations to your preferred programming language, but I'd love to work with you on that!