Event JSON
{
"id": "5fc6e35393b30d15b2f7d1a3e7b63fd4032da984b872691a4f15bdf45f50320f",
"pubkey": "fdeb3967a12d0a5afede68d1624770d82a909b1ab420c673e14c980ea2c8db01",
"created_at": 1730188332,
"kind": 1,
"tags": [
[
"p",
"e169cd1332305e075ad728b4d0d82b69d2f671b036eb7b6c96e56df95e9021ce",
"wss://relay.mostr.pub"
],
[
"p",
"65cd8b3ef65f48f32b01896d26bc0147b906a61b16bccd4891f83121fba31ea2",
"wss://relay.mostr.pub"
],
[
"e",
"489417d3f9ef2e53d7b89ffc3eb9b8a42c83dad9c9a22bdd9c1cc3bd94dd4983",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mastodon.social/users/henrikjernevad/statuses/113389622570362663",
"activitypub"
]
],
"content": "nostr:npub1u95u6yejxp0qwkkh9z6dpkptd8f0vudsxm4hkmyku4kljh5sy88q0a0kv7 I agree. Most \"zero policies\" become increasingly difficult as scale goes up. (Maybe that is a good reason to keep scale down? 🙃) But even in inherited large code bases, a light \"zero policy\" can be a way to \"bite the bullet\" and start improving the system. Personally, I don't mind working with legacy code as long as I am allowed to meaningfully improve it.",
"sig": "8471d143bcca2cb5496fce33a829f0443c8b0118fe2486d6baa4ff0c7ca1ec74412723c1f8848a5da3c63ad89582225d1fbaf6e852ae04b36fee6ec4e405c1b7"
}