Event JSON
{
"id": "f68cb896e7a98deefdb92c3d1c35cc7bbceffedeb1a92bbf8fcde7d7506ac3f4",
"pubkey": "a66ade00baf68ef943c94a412e2cb97d6c95919f469bf7842298f36d0b417e3b",
"created_at": 1724989302,
"kind": 1,
"tags": [
[
"p",
"680cc2d1b7bace5037256fc7efb5f6ec512654793ff406a7f77bc6444271915d"
],
[
"e",
"1484a61c7a2a09c33a6b37fe8a0d85140ff97206e794ee5c3db957e91fbf911d",
"",
"root",
"680cc2d1b7bace5037256fc7efb5f6ec512654793ff406a7f77bc6444271915d"
],
[
"proxy",
"https://piefed.social/comment/2632143",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://piefed.social/comment/2632143",
"pink.momostr"
],
[
"-"
]
],
"content": "This blog post is from May. I remember this issue kicking off on Mastodon a while ago - not sure if it came from the same person. Either way, the overwhelming recommendation was 'use caching', and sure enough, the update from the next day is https://kevquirk.com/blog/i-stopped-mastodon-ddosing-me-i-think\n\n\n",
"sig": "f2fed768f8029ecfff90526cbd8b42fa76b074e8639a7c3793ad9b551925c6399668645817a2c188e39fe2b91b684da893f89f36b7a37d8afb441ba118fd3436"
}