No worries! Happens to all of us

Adding because I'm interested and for anyone else who wants to try codeberg:

There was a slight typo in the url, but codeberg.org works!

Are you willing/able to share the code you used?

My dad-in-law is a retired programmer with an interest in genealogy, and I'd love to be able to nerd out about this with him.

Analog buttons are a big reason why I went with a 2013 rather than a newer car!

I'm not car shopping right now (my 2013 CRV is doing great), but I *also* want a car that's just a car. No data sharing, no autopilot. (Though I won't say no to heated seats!)

Another option: OpenRefine has some great fuzzy text-matching algorithms
openrefine.org

Many of my colleagues have limited Shiny experience, and I wanted a debugging option that was as simple and legible as possible.

I use this in a shiny app! 'debug' is a list containing items for whether to 'write_rds' files to a debug folder after major data cleaning steps and/or 'print' debug messages (to the console and/or a .txt file, using the logger pkg)

If it's a data frame in a function, it's called `dat`.

If it's a data frame I'm prototyping something with, it might also be called `dat`. Or `foo` or `bar`.

Yeah, this feels like a job for brand.yml and some nice code templates

I loved hearing your talk today. What a useful and thoughtful package. Thank you for sharing it with us!

Growing up, my grandma had an oblong kitchen table. Wasn't til today that I looked it up though!

Apparently "oblong" is just generic for "a stretched out square or circle"?

IDK

Does some of this functionality depend on Shiny version 1.11 to update if module files are changed?

Hey, I'm sorry. My bad for misunderstanding you.

Pak is so fast!

I agree that aesthetically it looks better and highlights that the foreground data is smaller, but I think for making sense of the graph, the only justifiable options are having the foreground bins the same width or half the width of the background