š
Original date posted:2014-06-14
š Original message:Was joking, but isn't the translation process back-ended with runtime tests to ensure that any stray chars etc cause the application to fail?
> On 14/06/2014, at 1:49 pm, "Matt Whitlock" <bip at mattwhitlock.name> wrote:
>
>> On Saturday, 14 June 2014, at 1:42 pm, Un Ix wrote:
>> How about a prize for anyone who can spot any "malicious" strings within next hour?
>
> I think it's more an issue of accidental breakage than any maliciousness. One character in the wrong place in a language bundle somewhere can make the difference between success and runtime failure, and it may not be immediately apparent when running in unaffected locales. This kind of problem isn't likely to result in data loss (or money loss, where money is data, is in Bitcoin), but it could be enough to necessitate scrapping the whole release, which would look bad and prompt users to question the dev team's quality control process.
Un Ix [ARCHIVE] /
npub1mxā¦45sm0
2023-06-07 15:22:39
in reply to nevent1qā¦c0sl
Author Public Key
npub1mxy8zdeg4txh8se7ugkrfhyfwxevsggcrce4ydmnkz6pn25jzwrqu45sm0Published at
2023-06-07 15:22:39Event JSON
{
"id": "6b387d46f2115d8af5f93f11e339287837de11834505c8dfc74c653ad91f535d",
"pubkey": "d988713728aacd73c33ee22c34dc8971b2c821181e33523773b0b419aa921386",
"created_at": 1686151359,
"kind": 1,
"tags": [
[
"e",
"a7227de8a6e97c1dbd351d4724658eec4042be0f772d051e197a562ef93f0d92",
"",
"root"
],
[
"e",
"c1a92fefe5e0e1d86373e9e30ae3b0647593f597cc7ec1072ff630cb1d44e5c5",
"",
"reply"
],
[
"p",
"f00d0858b09287e941ccbc491567cc70bdbc62d714628b167c1b76e7fef04d91"
]
],
"content": "š
Original date posted:2014-06-14\nš Original message:Was joking, but isn't the translation process back-ended with runtime tests to ensure that any stray chars etc cause the application to fail?\n\n\u003e On 14/06/2014, at 1:49 pm, \"Matt Whitlock\" \u003cbip at mattwhitlock.name\u003e wrote:\n\u003e \n\u003e\u003e On Saturday, 14 June 2014, at 1:42 pm, Un Ix wrote:\n\u003e\u003e How about a prize for anyone who can spot any \"malicious\" strings within next hour?\n\u003e \n\u003e I think it's more an issue of accidental breakage than any maliciousness. One character in the wrong place in a language bundle somewhere can make the difference between success and runtime failure, and it may not be immediately apparent when running in unaffected locales. This kind of problem isn't likely to result in data loss (or money loss, where money is data, is in Bitcoin), but it could be enough to necessitate scrapping the whole release, which would look bad and prompt users to question the dev team's quality control process.",
"sig": "405ad219949264001dfd3cc44154f608e2860501f095b943d782e616e81d7a4f5da33593e6093a86e210fa0822ef0dff5e921ebb06934d574bf36f97e4c383e0"
}