vvulph on Nostr: Happy to hear sentiment turning against GraphQL. Of course GraphQL shouldn't be its ...
Happy to hear sentiment turning against GraphQL.
Of course GraphQL shouldn't be its own language (ideally it would have been JSON), but exposing GraphQL through a web api server endpoint to the public internet is as bad an idea as exposing an endpoint that accepts SQL.
https://changelog.com/jsparty/plusplus-308-pre-partyPublished at
2024-01-21 01:13:44 UTCEvent JSON
{
"id": "6025f1315cd90bdd5f20f97152d1dcdbc75f12e985e239eefa5585ca698168e6",
"pubkey": "6ec69e6f02eb4b31f9ab8f6468bc3b3b28cffd22d355606bfefaf7208ce5da40",
"created_at": 1705799624,
"kind": 1,
"tags": [],
"content": "Happy to hear sentiment turning against GraphQL.\n\nOf course GraphQL shouldn't be its own language (ideally it would have been JSON), but exposing GraphQL through a web api server endpoint to the public internet is as bad an idea as exposing an endpoint that accepts SQL.\n\nhttps://changelog.com/jsparty/plusplus-308-pre-party",
"sig": "25d640a23321d853b8455cd66b2671cb0c5850e96410b4454be48e634fb7254f3f93661fe57a50e02fe528fac8f73bb464d46fbbfa090311ab3ab8162bbd6b99"
}