Event JSON
{
"id": "57826dbd3ca8ad7e423d3672c84ebedc0111589ff6654d87cece7f9570953c10",
"pubkey": "0e96c87e8dd4555400276a435f539e851fe33860b4e820aa0d4670009653962c",
"created_at": 1697888089,
"kind": 1,
"tags": [
[
"p",
"822a3c32c6b06303792fc98e35b5a527f0d6a938bad3b52924ad2f573d418bf4",
"wss://relay.mostr.pub"
],
[
"p",
"05bbadaea41d30c3cf3b7fb1027622eb00cca66635fc9047053df7f9a54cb0c7",
"wss://relay.mostr.pub"
],
[
"e",
"40cb6b0329430dfe2fc59e0d7f7ab8aa5266cc7fa9176fac1c2302a70d391a3d",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://soc.punktrash.club/objects/8a8b708f-e29f-4973-90ce-83d32cda7b09",
"activitypub"
]
],
"content": "nostr:npub1sg4rcvkxkp3sx7f0ex8rtdd9ylcdd2fchtfm22fy45h4w02p306qq7xslc I've tried to add a `needredraw: bool` to not redraw every similar frame, but this isn't enough. It continues to burn 12% of my cpu resources. I guess it is related to the de-sync between the square move, and the frame ticks that is triggered by the compositor, but then, how can we keep control over the life-cycle to reduce cost?\n\nThis is a genuine question that is related to this frame life-cycle design, and not to hari specifically",
"sig": "ee0eea6405c2bd0e22cb55b527c3dcce50da75677e1643a5c7ca15d53c9809fb608b3297ff5986952b386c925b5c057b781f090ea9ad89a0863c10688a3f77da"
}