@chriscoyier Like 2 hours ago. SSH for testing a only-happens-in-production bug.

@Rmmmsy Uh… my site runs over HTTPS if that’s what you mean…

@sethrubenstein How would you ban it?

@chipcullen Well looky here… bradfrost.com/blog/post/sass-sel…

On top of Carter Mountain Orchard instagram.com/p/Bok0Cx2nS-V/

@elgreg My dentist runs Windows 7

@randallb I’m sure there are probably some radical redesigns floating around there at Facebook HQ. But look at this junk-filled text box…

@randallb 2005 Facebook was the best Facebook

@randallb What is the state of Facebook?

@sawarunan @round Microsoft BOB

en.wikipedia.org/wiki/Microsoft_…

@round That’s a lot of fudge to pick up

🆒

@lelandf Did you meet a girl at the bank and then go to Cleveland? youtube.com/watch?v=wBWNgg8CClc

But if you’re using an Amazon Aurora managed database its dead simple to spin up read replicas so your site doesn’t fall over because you have too many bloated SQL queries overwhelming your poor database. So that’s cool.

Cooool so long story short not only does your database need the proper character encoding but the thing talking to your database needs to ask for data using the same character set. I guess that is better than just outright failing…

Our site talking to the database: “Gimmie some of that sweet, sweet UTF8 characters…”
Database: “Ok here ya go, I left out those 4-byte characters for ya since you didn’t ask for them”
Website: **Emojis are displayed as ???**
The Rest of the Internet: “This site sucks”

Our database is set to UTF8mb4 which can handle storing 4-byte characters (aka emojis basically). But clients accessing the database can specify what character set they understand.

@daveburdick I explained it to my wife like dialects and emoji and… yea she fell asleep.

Today I learned databases and character encodings are hard.

Someone is locked out of Slack so someone else is relaying communications from them via a Google Doc.

Slack.docx