Event JSON
{
"id": "e826f04fbba001862d98428e3a7712c14776ef0affa9ba4f811a6f8fb83ea134",
"pubkey": "448e8660bb0a8eb8beabe668e7d8426941186d5f515803a249b83814ce50108f",
"created_at": 1721128125,
"kind": 1,
"tags": [
[
"proxy",
"https://social.joshthomas.dev/@josh/112795852844296662",
"web"
],
[
"p",
"9c031ba3d4464f56ce895aff6098269c9ed4ff45f2a256ac82aca11db5ca97fe"
],
[
"e",
"32d4ac32239ed25c391bc3076ccdcc8af74fcc60a7cb31aa30c17aced99339ed",
"",
"root"
],
[
"p",
"3ad70a151e864338862ea02a8773e0ad7fc51eeb6136e5539f4898e644e2595e"
],
[
"e",
"ff44cc8d6f996d8325a052545d50a11c7acc0a78ed6f96464c5ce26c992e2e80",
"",
"reply"
],
[
"proxy",
"https://social.joshthomas.dev/users/josh/statuses/112795852844296662",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://social.joshthomas.dev/users/josh/statuses/112795852844296662",
"pink.momostr"
],
[
"-"
]
],
"content": "For a very small subset of users too. I’m curious though, what would the alternative be, one that reduces downtime as much as possible? Two migrations, one to create the new table and copy the data from the old table and one to drop the old table?",
"sig": "627e299c7faa39b9943a179f710aade1aff073ce761d10822e8ca584ab1a2bd5f535d94d97887fa4180312bbec5e50d40bac40a945902b6b992dd614859d96e4"
}