4 ms·
Hm, I thought it was going to be talking about leaking information from your app, not browser cache. Putting the database row ID in urls, which is the Rails de
by swalberg 11y ago
Hm, I thought it was going to be talking about leaking information from your app, not browser cache.
Putting the database row ID in urls, which is the Rails default, basically lets a competitor plot your growth with a simple script.
- elithrar 11y ago> Putting the database row ID in urls, which is the Rails default, basically lets a competitor plot your growth with a simple script. Which is only a 'problem' (we'll assume there's 1:1 between DB rows and growth) with incrementing column IDs. UUIDv4's or some other random ID (24-bit base64, composite IDs with a shard prefix, etc) don't have this problem.
- rhizome 11y agoor slugs.