Improve per-square page

[fulldecent]

Example not personalized

https://tenthousandsu.com/square/#1

• Add call to action "if this is your Square..."

---

Example personalized

https://tenthousandsu.com/square/#123

• Add call to action "if this is your Square..."
• Note that we do not review third party links
• Button to copy link and button to open in new window

---

Example available for sale

https://tenthousandsu.com/square/#1103

• Remove emojified section
• Add link to mint

---

For all of them

• Support wasd and ,aoe (Dvorak) navigation. To jump to a different Square page. But not up/down/left/right (because that would mess up the scrolling you would expect).

[ritorhymes]

This sounds like a good direction. I can work on this.

[ritorhymes]

Support wasd and ,aoe (Dvorak) navigation. To jump to a different Square page. But not up/down/left/right (because that would mess up the scrolling you would expect).

What do you mean exactly? To clarify, do you mean that when the user is on /square/#1, pressing "s" (down) will load info for the Square underneath it on the Billboard at /square/#101, or if they press "d" (right), it takes them to /square/#2? Like that?

If so, that sounds like one viable way to navigate but only locally on desktop for a few adjacent Squares. It doesn't cover two important use cases:

1. Mobile users navigating the Squares. They don't have quick access to keys like this.
2. Desktop users navigating a long gap between Squares (like from 1 to 10000)

It isn't practical for the use case of traveling long Square intervals, like going from /square/#1 to /square/#10000. That would involve an unreasonable amount of button presses and page refreshing to get there.

How are mobile users supposed to navigate with this?

What I suggested in #62 of at least an input field to enter a Square # and a submit button to trigger it seems like a good minimal solution to have these expected use cases covered both for keyboard users and mobile.

Having both together would make more sense.