Event JSON
{
"id": "b963a1c9426d9010e8466ccbd3cce402ae0610eb96edffb9dea6b4a9c69d80cb",
"pubkey": "a297d2ef6a36a76aa5241cfc4c0ab5ab13e37ab15aaa46b48dabd8cc3ace895c",
"created_at": 1732140115,
"kind": 1,
"tags": [
[
"p",
"80f08b97c5262fc68877efbb0377d6666730a2e8b885d6ed94463934ba81f281",
"wss://relay.mostr.pub"
],
[
"p",
"878c47bd4979fad7d81d5032895a0cbd8c7b3ac35f6b75f6131bd7144293d9fa",
"wss://relay.mostr.pub"
],
[
"e",
"abb672e47ca91805cb32f93cfea7acb376e2450052b4416e4b6d385d00e212bc",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mastodon.social/users/pervognsen/statuses/113517534628241239",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqsrcgh979ychudzrha7asxa7kvennpghghzzadmv5gcunfw5p72qsx8cc5z Rust has a similar issue with proc macros (as opposed to pattern matching macros). A proc macro is essentially just a token stream transformer so it has to do its own parsing if it wants to process Rust syntax as opposed to some other made-up syntax. And since the compiler itself does not provide that (mainly to avoid exposing the internal compiler APIs) you have to use a third party package for that like syn.",
"sig": "b40798061b538e54ea9e8450f37c9613375b994564d5e21c8ad8ce0de353d1f3429006ddb817167644630dcf8d755c4b5bd06166673a3a0e92851cb338c7db5e"
}