Event JSON
{
"id": "facbb81621ef15924f56820e282ad240faeab5ba398d09b3bdb4c72a589a2fef",
"pubkey": "363e334fb9fe142676db5636439c23d55970b7857d1e043aff651bafa7200aeb",
"created_at": 1717837120,
"kind": 1,
"tags": [
[
"p",
"e062fbe72ae69ccb16a631db7dcba2221e17a897b835743d7f1c0ccd7a2ef223"
],
[
"e",
"6c749c99be9e315e92a6879fd3711c5316d5925a9b3a024834a78c01c7228931",
"",
"root"
],
[
"proxy",
"https://mastodon.social/@dotstdy/112580173542229383",
"web"
],
[
"p",
"363e334fb9fe142676db5636439c23d55970b7857d1e043aff651bafa7200aeb"
],
[
"e",
"75eceb72fa92ada167dc8130de92f4751dd97732c18ff7df23de910aab097bce",
"",
"reply"
],
[
"proxy",
"https://mastodon.social/users/dotstdy/statuses/112580173542229383",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://mastodon.social/users/dotstdy/statuses/112580173542229383",
"pink.momostr"
]
],
"content": "for concrete examples: all our hash maps (in internal builds) have a version number used to detect and assert on concurrent writes. when resizing our growing array, we fill the moved-from memory with a specific bit pattern, so it's really obvious in crash dumps when you've invalidated an iterator (but without the overhead of actually tracking iterator invalidation). stuff like that.",
"sig": "5a3384b0cba36db5a4df14cd1059de31a4e7e1eeef696a929f0f089e87942d39a35e2b2efc1bd4983fb8032952cc027c452066fe1179f2b6adc41fbc22131444"
}