Event JSON
{
"id": "04f9539de91be38f45cc24446eb9dd8f603e5f6d3952ef8138ee5557b34ca4f3",
"pubkey": "effca4793b2710c9d391f2af243fc7228b446437e13c605b2ee931d03319336f",
"created_at": 1716047871,
"kind": 1,
"tags": [
[
"p",
"effca4793b2710c9d391f2af243fc7228b446437e13c605b2ee931d03319336f"
],
[
"proxy",
"https://front-end.social/@leaverou/112462913305989643",
"web"
],
[
"e",
"8a63d77ba3a79f8b58a9f3696d1b6bfb96428c9b9815c0f5b473b6c88be4ae45",
"",
"root"
],
[
"proxy",
"https://front-end.social/users/leaverou/statuses/112462913305989643",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://front-end.social/users/leaverou/statuses/112462913305989643",
"pink.momostr"
]
],
"content": "[2/2]\n\nCase that prompted this post, Custom SVG elements. 7y of pressure, a cornucopia of use cases, yet “no implementer interest”: https://github.com/WICG/webcomponents/issues/634\n\nCan someone shed some light on why browsers are so desperate to kill SVG?\n\nBecause at this point, I refuse to believe this is just a rational business decision based on hard facts. The hard facts are shouting “Fix your damn implementations!” and browsers are going \"la-la-la\" 🙉🙉🙉",
"sig": "90d970248b9cb9a690f5d28388efddb4ae7e8c9799feed8b2ce11da8e6c5f2204cfeb9e62ed8bda6f37ed3bd344262c9b785a9580feaf9eca89b5b96c6682ec1"
}