I'm afraid I'm not in the group because I changed the email when I was registering. I used my yahoo account, which is first initial last name.

Hmmm.... I'm rethinking using a managed database. Provisioning a more powerful VM, installing a database, and setting up an automatic backup for the system looks more cost effective, provides more storage, and still provides a backup.

I've upgraded from rails 5 to rails 6 locally and so far so good. I was worried it would be a lot messier.

Cross-posted from the beta board:

Three comments make a post:

1. Phoenix is spelled wrong in the site footer.

2. The header in Spike's Bitches has the non-ASCII characters encoded wrong, which leads to:

3. The "Text Encoding" menu on Firefox doesn't work on the new site -- almost surely due to the <meta charset="utf-8"> tag at the top of the page. A lot of the header (and tagline!) stuff on the old board was originally stored in windows-1252 -- that will require careful attention when migrating to the new database.

Also, Gud, where would you like things we notice to be posted? Here, the new board, some other thread, an issue tracker of some sort? I'm ok with any of those.

(And since I haven't said so before now, thank you so much for taking this on!)

that will require careful attention when migrating to the new database.

In the perl script I gave Gud to do database migration, I took care of that. The current database is an ad-hoc mix of cp-1252 and utf-8. When you migrate, you have to check every text record: first, try to decode it as utf-8 and check for errors, and if it fails, then try to decode it as cp-1252.

That sounds like a very sensible approach.

(Peering over my teacup rim and smiling at the nice men talking in a foreign language, feeling unalarmed and in good hands, whether I know what they're saying or not.)

I might screenshot this page for my computer science class. "See? People really do have to know this encoding stuff!"

Thanks for all your hard work Gud et al!