Don't expose primary keys to the public. Create separate external ids instead. I personally use BIGINT primary keys, with UUIDv4 external ids, but any random string will do.
Certainly seems the easiest solution. A lot of handwringing about poor database performance of UUID4 when you could use it exclusively for an external identifier all for the cost of an additional column.
Also, poor performance of UUIDv4 primary keys is most related to how write heavy your table is in the first place, and in particular how insertion heavy it is. In theory your users table shouldn't be very write-heavy, even if it may be insertion-heavy compared to other writes.
I'm also going down this rabbit hole, and it's about to get even crazier with multi-tenant SQLite[1] and Beamer[2] replication. It's not quite ready yet, but the foundation is there.
Elon is only permitted to work for 130 days because he's an SGE. The last day is May 30, which is 130 days after Jan 20.
A "special Government employee" (or "SGE") is an officer or employee in the Executive Branch of the Federal Government who is appointed to perform important, but limited, services to the Government, with or without compensation, for a period not to exceed 130 days during any period of 365 consecutive days.
This article is based on the text change on the gov.uk website from:
"The authorities in the US set and enforce entry rules."
to...
"You should comply with all entry, visa and other conditions of entry. The authorities in the US set and enforce entry rules strictly. You may be liable to arrest or detention if you break the rules."
