Event JSON
{
"id": "38b790d40d2d4365c9ea7d29316f130dcd3f844a9be67c9fbbe6275657208842",
"pubkey": "f40fb34cbe1940c4dd8413efbeb5b7f298baf5bec177e6b856bafde015df544b",
"created_at": 1726505052,
"kind": 1,
"tags": [
[
"proxy",
"https://social.tchncs.de/@teleclimber/113148235095968593",
"web"
],
[
"t",
"websockets"
],
[
"proxy",
"https://social.tchncs.de/users/teleclimber/statuses/113148235095968593",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://social.tchncs.de/users/teleclimber/statuses/113148235095968593",
"pink.momostr"
],
[
"-"
]
],
"content": "Server-Sent Events are under-appreciated. I get that people are scared of them because each ties up one of six connections (browser-wide) to the domain. But that's only under http 1.1. Under http/2 you get 100 usually. So no biggie?\n\nThe advantages are: amazingly simple API. You can have something useful, with automatic reconnects, in a few lines of JS. #WebSockets almost always involve loading a 3rd party library to take care of all the tricky bits.\n\nhttps://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events",
"sig": "09601182eda5db153dad62ce61f3b92f728e9b03eaadecbfbb027cf02347e090e45a4855a71589c4dd9645ab438a0598b1e97e21c538e373ddd1f229866e36d1"
}