Event JSON
{
"id": "a79db4140a7250b4b91dec132cb3c68c5d0978264ab8495106d29c33d554842f",
"pubkey": "ec6f81a56c07c99e5d9aadba4a0a88c1e52fdfa6de79e67239ec3bfd18cdd3a9",
"created_at": 1707311137,
"kind": 1,
"tags": [
[
"p",
"8f39365fcd938b90d2b383adc37e792673ecdf01c7b348af47b0c961b728d4aa",
"wss://relay.mostr.pub"
],
[
"e",
"cd85cd23abfe49ea6fa869463403c4a94f7b043b2f82301f12577ae1670078b3",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mastodon.social/users/aallan/statuses/111890342693136420",
"activitypub"
]
],
"content": "nostr:npub13uunvh7djw9ep54nswkuxlneyee7ehcpc7e53t68krykrdeg6j4qrdpvgs Because the author of picamera stopped supporting it? Wasn't our decision. The original picamera library wasn't written, or supported, by Raspberry Pi. The new picamera2 library was written in-house, and is extensively documented, https://datasheets.raspberrypi.com/camera/picamera2-manual.pdf. It might not do what you want (yet), but it's being actively maintained and worked on.",
"sig": "7935eed4f97ff6f97ebd72a12e53a21e6107bc171d09f87ab586351aa5de3e22a49a6cd9efc58e608384aa902dd66083d1a4c4f8fe0582b4009986bbe94043dd"
}
