343 karma · joined March 11, 2015
As someone deeply interested/involved in the area, I have a few leading questions and a shameless plug:
- From the description of your pivot, it seems that you plan for this to become a job board/professional profile/LinkedIn/Behance of AR. Did I understand that correctly? What do you consider to be the main source of revenue in that case?
- Do you feel that the simplification of your stack from JS to PHP helped you be more agile for 2.0? This is a tangential question but the answer is likely an interesting one given the choices and current web dev trends.
- Can you share some of your most successful SEO/Traffic tricks with the HN community? What worked the best? We love to hear a great creative/innovative bootstrap story.
- Do you miss working in AR dev itself given your background in the space or do you feel the most value comes from empowering other creators in the AR community?
- Shameless plug: https://pinealeye.co/adkitxr/ We are working on 3D native ads for AR/MR/XR. Check us out, let me know what you think, and let me know if there is a potential/interest for a partnership. I see a big synergy between building a community of creators who want to get their creations known, and our technology.
[0] https://techventures.columbia.edu/news-and-events/latest-new...
Put in layman terms - your best possible entropy is a case where every allowed character appears with roughly the same chance (i.e. there is no super common or super rare characters). The most extreme low entropy case is where only one character appears all the time so the password is completely predictable if you know how long it is.
I would recommend you run two tests. One with the same video over and over video and one with 5 or so videos filmed under similar conditions to measure how much of the randomness actually comes from different videos vs. your algorithm. For your videos genererate 100k+ passwords and count the number of times each character appears to get the probability of each character. Then use what you learned about Shannon Entropy (using the probability of each letter) to determine how much entropy your passwords have.
This is an interesting idea but have you conducted any entropy tests by generating a class of passwords from a family of videos and seeing how different they really are (e.g. character freq)? Without any hard numbers I can pretty confidently assume that the colors (8 bit unsigned perhaps mean R, G, and B pixel values) in a video are not uniformly/randomly distributed in the color space and subsequent frames of the video are also highly correlated. Not to mention you specifically throw away any non ascii character so a large portion of the UTF-16 space is not even allowed). Unless by chance, those you throw away happen to also be the super common int values, I feel that it's likely the entropy of these passwords is going to be surprisingly low.
What do you think? The entropy test would make a great blog post.
I have two comments though from a practical perspective:
1. If this one job (with a very specific team and requirements) is being advertised and your site gets popular enough, thats 100s of applications for one hiring manager to go thru in one day rather than a trickle over a few weeks. On one hand that might be appealing but from a practical perspective, that means most resumes won't get a fair shake or it will take forever to get back to everyone (if it all). This feels like a strictly worse user experience for both sides in terms of backlog, time to feedback, and fairness of evaluation. Not to mention the backlog of jobs itself waiting to be featured means most jobs will get 0 applications from you while they wait in line and that does nothing to fill the role.
2. If the job has some nuanced attribute to it like a foreign language requirement (current post requires Japanese) or an untenable relocation requirement, the subset of jobs that are even a possibility to a typical visitor is highly reduced. If that's 1 in 10 jobs that work from a skills and logistics perspective for a given applicant, that's on average only 1 option every 2 weeks which could really slow down a sensible job search process. From a product perspective, this will lead to high bounce for first time visitors - Perhaps you could mitigate this by showing the last 5 days of jobs if someone wanted to see them and that might motivate them to sign up for the daily recurring email if they see more potential for value. But that still doesn't solve the impractical nature of only seeing 1 tenable option every couple of weeks for someone genuinely trying to find a job quickly.
I understand the concept is one a day and this can be expanded by creating some more relevant tracks but it feels you may just end up converging on a standard job board :)
In my opinion, the biggest problems in job search are relevancy for applicants (as you say, you just need one hyper tailored job) and triage for hiring managers (what's the best way to screen a huge set of people on items that are (1) easy to gather (not a ton of open ended questions) and (2) hyper relevant to your specific position. Would love to hear your thoughts.
For sake of easy math, pick C, your threshold, to be fixed at 0, which is halfway between -inf and inf.
Now there are 4 scenarios. The numbers player 1 chooses, A and B, can be both above or both below C with probability 1/4 each. In both those cases, you have a 50/50 chance of being correct on which number is larger depending on which number you chose to see.
Then, with the other 1/2 of the times, one number will be above and the other will always be below C. In those cases, the selected strategy will have you always choose the correct highest number.
All together you are right 1/2 + 2 * 1/4 * 1/2 = 3/4 = 75% of the time. Simple probability but totally counterintuitive from the onset.
Now what if C!=0 or numbers are not being selected uniformly by your opponent? You can replace the 1/2's with (p) and (1-p) in the right spots without making any distributional assumptions and it seems (without doing the math out fully) that things cancel nicely and show that you always have a strictly greater than 1/2 chance of guessing right no matter what. Exercise left for the reader :P
Merkle trees are also used in Bitcoin and similar protocols to find if a transaction is present in a block. This may be a another useful link to help understand the concepts: https://hackernoon.com/merkle-trees-181cb4bc30b4
IMHO, the most important thing missing right now to promote more decentralzied mail is a cometivtive open source mail (web) app, with a simple UI and a vibrant plugin system for every use case.