I wanted to leave GitHub but I'm still stuck there. What it would take for me to finally leave is some kind of federation of the social features, so I can port my stars over, see what others are working on, etc.
I’ve never stumbled upon a project by browsing GitHub casually. It’s always through finding the product first and trying to find the source code. If the source code is on some other website, I’ll probably figure it out, but it’s be a new muscle. Same with making an issue or a PR. The barrier is higher but not so high that I wouldn’t complain about a bug.
If anything, I find the social tools on GitHub like PR reviews, issue management, and notifications to be terrible for their job. Perfectly fine for a 1 person project and absolutely awful for a team.
I casually browse GitHub sometimes in the same way I do HN. I follow friends and colleagues and through the feed see what they're building and starring. I use global search to find tools and libraries that do what I want.
Sometimes, I come across a repo I like that's on say GitLab, but not GitHub. I quickly forget about such projects because they live in my bookmarks instead of my stars list.
>I find the social tools on GitHub like PR reviews, issue management, and notifications
I don't consider these social features, at least not in the way I'm talking about.
Same.
The “discoverability” of github is two things:
1) Recognition of the name; so if I cannot find the source code and I believe something to be open source I will google the product name with “github”.
2) I can reasonably expect everyone to have an account, so getting issues and PRs is less effort than with other forges.
But I’ve practically never discovered some new FOSS from githubs social features, and I actually look at my friends activity feeds.
And every time I think about it for more than a second, I get mad that OpenID got eaten by OAuth.
I’m sure it was imperfect, but in theory it was easy to host and easy to implement. :(
Revocation was hard, but it's not like existing systems are solving that in practice either, and you can get a long way by just keeping short leases (which is fine because nothing needs to communicate with any third party).
If passkeys weren't so blatantly DRM-friendly I might like those, but they seem intentionally human-hostile for no good reason at all.
Personally, I do a Kagi search, or I make an LLM do it for me.
I highly prefer word-of-mouth recommendations like Reddit, HackerNews, or Lobsters. It's quite easy to browse threads where people mention hating some package and switching to something else. It's also a lot easier to see gamified posts (astroturfing), whereas it's really hard to judge projects on GitHub. So many forks are distractions, and stars mean so little. As such, I highly value a personal blog post.
Similarly, I look at what the projects I find link to. They'll often be "inspired by" another project, or a rewrite in a different language. It's a great way to see how different creators consider trade-offs between different projects.
I only browse someone's GitHub when I see an insightful blog post, and I want to learn more about the author and what they work on. Usually I close that tab within 10 seconds cause I can't be bothered to figure out which of their 100 repos is interesting.
My best analogy is that GitHub is the TripAdvisor/Yelp/Google Reviews of finding a good restaurant. Those platforms have been gamified aggressively. The signal is low, and you can't flatten judgement of a restaurant into a 1-5 star scale. Your best bet is to find opinions tied to real people that aren't tied to points.
Edit: here's one: https://forgefed.org/
For any given project, are there any forks / is this one a fork, and which ones are more recently/actively maintained, and what are the changes?
That network display where you can not only see all the forks in a timeline, but click on the individual commits is super handy.
Idk how you'd assemble that out of a federated system. It's probably possible but seems like it would require a lot of update traffic going in all directions between all nodes.
I have found running GitHub mirrors for my own projects hosted on a private Forgejo instance works well enough, but the fracturing of GitHub will inevitably cause more difficulty in discovering others’ work. I suppose that opens opportunities up for either federation, or at least aggregation (Sourceforge has been doing that already, although I find its interface a little clunky).
It used to be "I want to talk to these people. Oh, they're on IRC" and then it was "I'm on IRC. who can I talk to here?" and while that might not be so bad for IRC, it's catastrophic when it's proprietary platforms with lock-in.
The main issue though, is that I won't star a repo on an alternate forge. That is the main reason many projects will only consider Github - if they have no revenue they must have traction, and GitHub stars are a good substitute for meaningful measures of that.
Your stars list is browser bookmarks. You can see what others are doing even if you don't have accounts on their sites.
Not practically. That works up to a number like three. Are you really going to manually poll every account you care about?