Chris Abbey on Nostr: ok, now that #php 8.3 has turned up the volume on unserialize() complaining about ...
ok, now that #php 8.3 has turned up the volume on unserialize() complaining about trailing data, does anyone have a built in method to decode the default session serialization? (the way most folks do it today is based on a comment in the docs from 12 years ago that will now spew E_WARNING like crazy.) I still see no official API for decoding it other than the one that shoves it into the super global (Which has other undesirable side effects.)
Published at
2024-09-19 22:08:55Event JSON
{
"id": "8ee65bd2c0a955b48bf6037d2b92e425eae769f687f29a294dfdade509f361eb",
"pubkey": "276b5f35f8893108e4febe4b60c85a0c002fde52c45d583c4b975c78a4632101",
"created_at": 1726783735,
"kind": 1,
"tags": [
[
"t",
"php"
],
[
"proxy",
"https://phpc.social/users/cabbey/statuses/113166498888636733",
"activitypub"
]
],
"content": "ok, now that #php 8.3 has turned up the volume on unserialize() complaining about trailing data, does anyone have a built in method to decode the default session serialization? (the way most folks do it today is based on a comment in the docs from 12 years ago that will now spew E_WARNING like crazy.) I still see no official API for decoding it other than the one that shoves it into the super global (Which has other undesirable side effects.)",
"sig": "ca1493552036f63007703ebfc8f344a2186582da9e49957ffde46b82e86a2e8ec46f2a47789d3803f2c364073881ce23cd975f3dc233b3e664b2e9c08017158f"
}