3 ms·
“As a result of this breach, all user permissions were reset, making all profiles visible to all users” This seems like the opposite of how a sensible permissi
by varenc 6y ago
“As a result of this breach, all user permissions were reset, making all profiles visible to all users”
This seems like the opposite of how a sensible permissioning data model should work.
- 0x00000000 6y ago“But A/B testing showed more ‘user engagement’ when you default to public”
- W-_-D 6y agoWho are you quoting there?
- woolinsilver 6y agowooosh
- isbvhodnvemrwvn 6y agoI think it's an older issue. Before it was sold, GEDmatch was ran by several part-time developers. It was running some old PHP 5 version the last time I checked. In general I advise to be very sceptical of amateur-ran genealogy sites - I know of at least 3 search engines with obvious SQL injection issues (which allow me to run better queries, but still). All of the major commercial sites had some sort of leaks as well (I'm not sure about FamilySearch).
- marsrover 6y agoI thought the exact same thing when I got the email. I would have much preferred a permission reset resulting in profiles being locked down tightly.