As an example, after I signed up it showed me this screen, which supports four branches in the flow: 1) email validated, 2) resend link, 3) email is incorrect, 4) skip & continue in unvalidated state. That's a lot of work to support edge cases.

Then to figure out which areas were in danger. Every official resource I could find pointed to a map from California Dept. of Conservation, which was down because of the server overload.

Props to tsunami.gov for handling the spike in traffic. But I found its UX to be pretty confusing. I had to navigate through a table of alert messages, and find the option labeled "Obs/Forecasts" in a dropdown. It wasn't clear which row pertained to my area so I guessed.

Seemingly the only online tsunami zone map, which is pointed to by every official emergency resource, currently looks like this.

DevOps is important.

5/5 Animated 3D tunnel view of the "Firehose" (all the posts on Bluesky in realtime). This one is particularly visceral. by @theo.io. firehose3d.theo.io

4/5 Emoji use in posts with realtime updates. Filter for 15 different languages. by @alice.mosphere.at. emojistats.bsky.sh

3/5 Historical activity in likes, posts, and follows from May 1st 2023 up until 3 days ago when things got a little hectic. by @jaz.bsky.social. bsky.jazco.dev/stats

2/5 Compare the Bluesky userbase with the populations of countries. By the time we're at 20M we'll have exceeded that of Ecuador. by @watwa.re observablehq.com/d/58c2cd234c...

1/5 Simple user counter from @natalie.sh, based on a similar one by @theo.io (the two are off from each other by a few hundred—not sure which one is more accurate). Good place to be when the numbers turn over. bcounter.nat.vg

Bluesky is very likely to reach 20M users in the next 11-17 hours. Here are 5 community-built visualizations for Bluesky user data 🧵