themaninblack@lemmy.world to memes@lemmy.world · 4 hours agoCVS stylelemmy.worldimagemessage-square27fedilinkarrow-up1205arrow-down12
arrow-up1203arrow-down1imageCVS stylelemmy.worldthemaninblack@lemmy.world to memes@lemmy.world · 4 hours agomessage-square27fedilink
minus-squareWarl0k3@lemmy.worldlinkfedilinkarrow-up3·edit-23 hours agoCannot imagine how this could be legit - you’d run into a hard limit unless you explicitly designed that field to be unbounded.
minus-squareFartMaster69@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up1·1 hour agoIt’s not hard to find badly designed webpages.
minus-squareMotoAsh@piefed.sociallinkfedilinkEnglisharrow-up3·edit-22 hours agoMeh, not that hard to default things to “string”, or similar. For example, the “text” type in PostgreSQL explicitly says “unlimited”, though it seems it’s up to 1Gb. See https://www.postgresql.org/docs/current/datatype-character.html Similarly, it’s not like text fields on web pages automagically apply limits. It’s not unimaginable that some dumbass could vibe-code themselves up an easily exploited form.
Cannot imagine how this could be legit - you’d run into a hard limit unless you explicitly designed that field to be unbounded.
It’s not hard to find badly designed webpages.
Meh, not that hard to default things to “string”, or similar. For example, the “text” type in PostgreSQL explicitly says “unlimited”, though it seems it’s up to 1Gb. See https://www.postgresql.org/docs/current/datatype-character.html
Similarly, it’s not like text fields on web pages automagically apply limits.
It’s not unimaginable that some dumbass could vibe-code themselves up an easily exploited form.