missing privacy level in api getPrivacyLevels

+4 votes
128 views
The API function getPrivacyLevels does not return all combinations of privacy names and level numbers. For instance, my profile has privacy level 35. The getPrivacyLevels action does not return a name corresponding to this number.
in WikiTree Tech by Doug Henderson G2G6 (8.8k points)

2 Answers

0 votes
So what's the deal?  I'd think there would be protection on access to privacy levels.  For instance if you can "getPrivacy Levels" how do you protect "setPrivacyLevels" (or whatever the program you're using calls it.)

I.e. do you have rights to muck with this api?  I realize this is collaborative outfit,  but there have to be limits when it comes to privacy.
by Dave Dardinger G2G6 Pilot (410k points)

The getPrivacyLevels provides information that is independent of all individuals. It provides a mapping from the numeric privacy level numbers stored in the database to the privacy level names displayed on WikiTree pages. The privacy level names are describe on the Privacy page. Internal to the database, privacy levels are represented by numbers that correspond to these names. This issue reports that I found a number in the data I retrieved that does not have a corresponding name in the the data returned by the getPrivacyLevels action, but which does appear on the Privacy help page.

In general, the API does not allow you to change the live data shown on WikiTree pages, in fact, according to the documentation, the API reads from an almost-live copy of the live data. When you use the API, you can see anything the public can see when they visit WikiTree. When you login to the API with your WikiTree credentials, you can also see anything that you can see when you are logged on to WikiTree.

So, to address your concerns, the API enforces the same privacy restrictions that WikiTree enforces on web pages. A non-logged-in guest will see no private information, and the logged-in user will see only the pages that he is allowed to see on the WikiTree pages.

Well that's good to know.  I'd assumed things had been arranged to prevent loss of security.  But I hadn't known whether that security had anything with what you were working on.  It seems your problem arrises elsewhere.  Good luck figuring it out.
0 votes
This should now be fixed.

Thanks for reporting it, Doug.
by Chris Whitten G2G Astronaut (1.3m points)

Related questions

+4 votes
2 answers
+6 votes
3 answers
110 views asked Sep 28 in WikiTree Tech by Przemek Więch G2G4 (4.8k points)
+5 votes
3 answers
125 views asked Feb 1 in WikiTree Tech by Fairch Fairchild G2G2 (2.5k points)
+4 votes
1 answer
+6 votes
1 answer
+23 votes
2 answers
+3 votes
0 answers
81 views asked Aug 1, 2021 in WikiTree Tech by Kay Knight G2G6 Pilot (477k points)
+7 votes
1 answer
230 views asked Apr 10, 2020 in WikiTree Tech by Brian Casey G2G Crew (340 points)
+19 votes
1 answer
463 views asked Jul 19, 2019 in WikiTree Tech by Jamie Nelson G2G6 Pilot (475k points)
+4 votes
1 answer
223 views asked Mar 25, 2019 in WikiTree Tech by ing C.J.S. Vonk G2G Crew (440 points)

WikiTree  ~  About  ~  Help Help  ~  Search Person Search  ~  Surname:

disclaimer - terms - copyright

...