Event JSON
{
"id": "056184906f1fae10ad9c0b0ba452a2964d31e8d936e00dd31bedc42801b22ff3",
"pubkey": "5f2dac217c35680cbce574baa0ae609373a356ef1de1ab2ed0a920abb9db3fff",
"created_at": 1732285804,
"kind": 1,
"tags": [
[
"t",
"valkey"
],
[
"proxy",
"https://fosstodon.org/@linux_mclinuxface/113527082493565410",
"web"
],
[
"proxy",
"https://fosstodon.org/users/linux_mclinuxface/statuses/113527082493565410",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://fosstodon.org/users/linux_mclinuxface/statuses/113527082493565410",
"pink.momostr"
],
[
"-"
]
],
"content": "There was an interesting request posed in the #Valkey discussions:\n\nA request for a 32-bit container. Earlier this year I advocated for dropping 32-bit support because it decisively seems like something of the past. I would be surprised if _anyone_ was running Valkey on 32-bit machines.\n\nHowever, 32-bit addressing _does_ save memory, a non-trivial amount. OTOH, it caps you to 4gb. And then there is maintaining 32-bit code, which is something.\n\nWhat do you think? \n\nhttps://github.com/orgs/valkey-io/discussions/1304#discussioncomment-11341542",
"sig": "6e76b3d12b0b4a6ded376bfe8081475a0b11e3584d2145316ca7979b18719b365c9f3a6cc4c3ac1346e6a1a94ff8a2fbf3f0115142f3e1d26a6c876febf219d9"
}