You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 15, 2020. It is now read-only.
I didn't create any accounts (I see people in issues that did this), I just created resume.json file in my Gist and it works. Whenever I load https://registry.jsonresume.org/mygistfile?theme=cora it shows me my CV. Do I need any account at all?
I have privacy concerns about this approach, now registry accepts only public gists as a source for resume and this is not good. Everybody can search gist and find my resume together with contact details.
I tried to create secret gist but registry does not see it. Can we somehow solve this problem?
The text was updated successfully, but these errors were encountered:
dude are you kidding me ? you literally open your CV for public (companies to hire you) your data is already out there all can see it so there is no privacy
Open CV is not the same as open contact details of this CV, I definitely do not want every *ucking recruiter call me by phone and know my email, I want to be picky and choose to whom give the details and to whom not. And in current implementation every layman can search the directory and find my gist with my contacts.
If you don;t understand such simple thing then you are a rookie on a labor market.
I didn't create any accounts (I see people in issues that did this), I just created resume.json file in my Gist and it works. Whenever I load https://registry.jsonresume.org/mygistfile?theme=cora it shows me my CV. Do I need any account at all?
I have privacy concerns about this approach, now registry accepts only public gists as a source for resume and this is not good. Everybody can search gist and find my resume together with contact details.
I tried to create secret gist but registry does not see it. Can we somehow solve this problem?
The text was updated successfully, but these errors were encountered: