4 ms·
> Why spend any resources on users who aren't adding value? What makes you think that logged out users aren't adding any value? The behaviour of github here i
by eru 3y ago
> Why spend any resources on users who aren't adding value?
What makes you think that logged out users aren't adding any value?
The behaviour of github here is consistent with them assuming that logged out users provide a small but non-zero amount of value for them.
The link you provided seems to suggest that the code search is supposed to be faster for users, but I can't see anything in it that suggests that it's less taxing on the backend?
- throwaway7679 3y agoI may not have made it clear enough, but my first line was meant to be absurd and obviously wrong. I think a service should focus on how it provides value to users, not the other way around. People use it because of what it provides to them, not because they desire to support the company's bottom line. GitHub built a remarkably valuable product, which attracted 100M users and $1B in revenue. It has tons of public features that never required login. They could have put search, or any number of other things, behind a login at any point in the last 15 year. But they didn't, because that's not actually a good thing to do. Doing that can only ever make the feature less usable. What drives them to do it now is unclear. Perhaps just wanting to juice their login numbers or whatever. But, performing little bait-and-switches on random features isn't going to make people use them more or spend more money. It's going to make them seek hedges against the destruction of the features they enjoy. As for my link, the search result speed for users is directly related to cost per query, unless you believe that all of this is fake and the new search system is secretly just a bunch of expensive new hardware.
- spoiler 3y ago> What makes you think that logged out users aren't adding any value? I'm curious because I'm not sure of the answer myself: what value do you think anonymous users provide to them? I suspect gating it behind a login is a simple way to rate limit, and prevent abuse with a cheap and effective way to mitigate false positives. As someone who's had to make similar decisions in the past (albeit smaller scale), I can sympathise with them turning off a computationally expensive feature that's not at the core of their product, but just an add-on.
- aleksiy123 3y agoAnonymous users are potential future customers. Too much friction and they will leave and never convert. Also network effects of those users since GitHub is not just a git repo host but a social media and community for code. I think product needs to strike the right balance of free and paid features to maximize their profits.
- spoiler 3y agoRight, I kinda see that point, but I'm also not sure how I feel about the code search issue. On one hand, I agree that it makes the user experience nicer and can aid conversion, but on the other it's easy to abuse the feature (in a few ways off the top my head). Some of the things you highlighted (ie the social network effects) are best experienced when logged in, and other than "just" browsing, there's not much in interaction for logged out users already (can't host code, open issues, comment, star, etc). I think allowing people to browse code and its history, alongside other parts of the platform for logged out users already feels pretty open to me