Event JSON
{
"id": "ee97baf210d5cfbbc1c0d9eadf6bdec49f04d6ec453ebb294feef493ac15f532",
"pubkey": "d4e0623c6b6a5b0911b013e1e242fc477ec8d689f8e38c14e2742fe0120b4cf9",
"created_at": 1698824133,
"kind": 1,
"tags": [
[
"p",
"9529d1f7d069871da2bf6f827b72f781c15cf7f4488fc261432c8d8e4b35be3f",
"wss://relay.mostr.pub"
],
[
"p",
"cf0a0a4627541e36c5af1b9e226c9e599996b68c172bee0a942bcbc3a1dd7150",
"wss://relay.mostr.pub"
],
[
"e",
"44a2c9b5b7902ff1cd3a6a7da07481b8079b94b1e5737b1a40b958381657f4ba",
"wss://relay.mostr.pub",
"reply"
],
[
"t",
"capacities"
],
[
"proxy",
"https://pkm.social/users/spinningthoughts/statuses/111334138393996018",
"activitypub"
]
],
"content": "nostr:npub1j55ara7sdxr3mg4ld7p8kuhhs8q4eal5fz8uyc2r9jxcuje4hclsrftkvt TBH I think that in of itself can be \"blamed\" in part on a slew of minimum-functionality, user story-oriented design without fundamental decomposition. I wrote about this months ago as something I think #Capacities is defying. But consider for example how full of special features Notion is. New fields, data structures and documents just to support one more application- instead of having it all emerge from the same data structure and tooling, connecting differently.",
"sig": "5ebe3badef62d43d019a5ee50c1d27586570821d79b15d6a43ed9c413d0205e80ab438c1f678648c1170947d83845538c44d84a47a38d5cd5e9a4c228be0dfed"
}