Event JSON
{
"id": "ee36b9c95fbc196927d6021994248f08c5732a1009bcbddbabf8bcfd2e3045b2",
"pubkey": "5bdfe5c3188a24f76efd37648930d8ada3e458961d03b2e0d62596d4f76e4778",
"created_at": 1697959967,
"kind": 1,
"tags": [
[
"p",
"5150cec16f3fe453e8895cfc0a03f391c890712633f718c0bca1a1096cf8d547",
"wss://relay.mostr.pub"
],
[
"p",
"979383f8767c5d795fcad86f82dc7b38b384c1a473710c433014dc2c0fb0e359",
"wss://relay.mostr.pub"
],
[
"e",
"1c61ad7863f424143855e49d73296e1bc1b8469f2ab4922aa5b6082d3ed3ed91",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://fosstodon.org/users/dpom/statuses/111277504417706600",
"activitypub"
]
],
"content": "nostr:npub129gvast08lj986yftn7q5qlnj8yfqufxx0m33s9u5xssjm8c64rsve4kwg Demanding anything of OSS maintainers never ends well. I was picturing large projects, where a total rewrite would be unreasonable in the short term, but contributors are looking for ways to support modular/incremental adoption of Rust and its toolchain alongside existing code. If the project has a scope where a complete rewrite in Rust could be a short-term goal, then why even bother the maintainer with that? Just go do it.",
"sig": "d873e527cd109b1c9670c99dabe399c5c7bcbf3570a983ca156abc7b702f478419bb38eff5df9215a84ba9cabc0b0f121a27f0eee1c4f35f93e4b0f472ddf404"
}
