[deleted]
Nginx has moved to GitHub
41–50 of 170 posts
Re: Nginx has moved to GitHub
#42What's the state of nginx nowadays? Last I heard the original core team had fractured and formed two different forks while F5 continued to develop OG nginx, so there's three nginxes being developed in parallel now. Have the forks gained any traction?
You know, for most projects, I'd think that'd be pretty...bad. Given that nginx only recently got dynamic module support, I'm curious how many people are out there having grown to build it from source, letting them switch upstreams a bit more easily. perhaps. maybe.
Re: Nginx has moved to GitHub
#43Earlier quoted context omitted.
There are some alternatives like https://grep.app or https://sourcegraph.com/search if you want fast live search, but at the end of the day these are services offered by companies, and rather expensive ones especially for free anonymous users, so you should probably at least accept that service providers can and do change things like this. You can also run something like your own copy of Zoekt and then ingest reposit…
Github managed to provided search to free anonymous users since its inception in 2007, to mid-2023 when they introduced this new code search. I would submit that this change is entirely business-related: it's a power-play to make people create accounts and stay logged in so they can track you better. It is not that they cannot afford it, it is that they are enshittifying the service to further their interests. If the…
Personally, I don't think this is a valid case of enshittifying. Products that you pay for that loses features or break or become more painful to use are enshittifying.
A free feature that stays free but requires you to make a free account (no credit card needed), I can see at least one very valid reason: if the feature heavier than a simple page (which is the case here), then it's an open door for DDOS attacks. Being able to track and ban/block the users that appear to participate in such an attack is totally valid.
The alternative is having to do captchas and the like to use those features anonymously, which is a pain both for user and for the devs/UI, and does feel more like the overall enshittification you are mentionning (even if it's a valid reason)
Re: Nginx has moved to GitHub
#44Recently, I was browsing an open source project I use a lot. "Sign in to search code on GitHub" was kinda discouraging to see. Sure, I can clone it and run grep/ripgrep - but sometimes I like the ability to search the code on the browser. Is it only GitHub where this is a restriction or GitLab is similar?
You can change github.com to github1s.com to get VSCode in browser with fairly capable search without logging in. E.g. https://github1s.com/nginx/nginx
Alternatively the official site is vscode.dev.
Re: Nginx has moved to GitHub
#45What's the state of nginx nowadays? Last I heard the original core team had fractured and formed two different forks while F5 continued to develop OG nginx, so there's three nginxes being developed in parallel now. Have the forks gained any traction?
TEngine might be the most well-known fork
That ones new to me, I was aware of Angie and Freenginx which are both led by former nginx developers who left F5 after the acquisition. TEngine looks to be a much older fork but I can't find much recent discussion about it, though that may be because it's an Alibaba/Taobao project with a primarily Chinese userbase judging by the GitHub issues.
Re: Nginx has moved to GitHub
#46Recently, I was browsing an open source project I use a lot. "Sign in to search code on GitHub" was kinda discouraging to see. Sure, I can clone it and run grep/ripgrep - but sometimes I like the ability to search the code on the browser. Is it only GitHub where this is a restriction or GitLab is similar?
I believe it was added when they made their search more advanced and presumably more resource intensive.
And yet, nothing stops them from continuing to offer their existing search to anonymous users. The search they have offered since inception.
They chose to take the existing search away from anonymous users to drive signups and logins. "Sign up and log in to get improved search" is not as compelling as "sign up and log in to get any search at all"
Re: Nginx has moved to GitHub
#47Recently, I was browsing an open source project I use a lot. "Sign in to search code on GitHub" was kinda discouraging to see. Sure, I can clone it and run grep/ripgrep - but sometimes I like the ability to search the code on the browser. Is it only GitHub where this is a restriction or GitLab is similar?
You can change github.com to github1s.com to get VSCode in browser with fairly capable search without logging in. E.g. https://github1s.com/nginx/nginx
I believe the search there uses Sourcegraph, so you can also search directly at https://sourcegraph.com/search. E.g. https://sourcegraph.com/search?q=repo:github.com/nginx/nginx...
Re: Nginx has moved to GitHub
#48I wonder how the interim process is handled? They're accepting mailing list updates until the end of the year. Does someone take the mailing list updates and manually PR them into Github? I've never actually used a mailing list so I'm curious how it works.
With a mailing list you download a patch and apply it with "git am", then push it to the repository -- as you are presumably the maintainer who has permission to do that, and assuming the patch is good. You basically just do code review through email and reading the patches with some git functions. It completely sucks in my opinion, but some people like it, or it's how they do things in those parts, etc. When in Rome...
Having done a similar rodeo in the past -- migrating a project to an actual code review tool that enforces some more rigid structure, over plain patch files -- the interim process will probably be something like:
- Previously, some key people were allowed to commit to trunk directly.
- They would read emails/patches, do code review, apply, and push them to trunk.
- For now, you can keep emailing people your patches like you did before. Nothing will change.
- But at a certain point, you'll have to use this new Other Method.
- So, you should probably get familiar with Other Method early, by using it in the meantime, so you can be ready.
- At some point, no more patch files will be accepted and you will have to use Other Method.
- In the meantime, the maintainers will do double-duty and handle both venues.
Most projects are small enough where the double-duty isn't so bad. Most people will switch quick enough and you probably aren't dealing with 1,000 patches. It sucks but the payoff is considered worth it.
Eventually once this is completed you can do things like stop pushing directly to trunk and handling all patches to main through the Other Method. But you don't have to do that. It does sound like they'll stop accepting email patches, though.
Re: Nginx has moved to GitHub
#49Earlier quoted context omitted.
The problem is that GH makes it the login process as painful as possible. Login tokens expire frequently, necessitating new logins. Logins require 2fa every time, which makes them extremely flow-breaking. Post-login you're not returned to the file you were on, so now you need to navigate back to search. Logins are per domain and per device, so I end up dealing with this 4x per day if I'm using GitHub heavily. It's un…
To me, ordinary login is one of the things they've genuinely improved over time I feel? I absolutely never deal with logins more than once a day per machine? With stuff like Passkey support now, I basically click two buttons in 1Pass and I'm logged in instantly on ~everywhere. I also feel like I never have my tokens expire. I'm probably not doing the same stuff as you. It's sudo/elevated mode that really gets you I t…
GH Enterprise and public GH don't share tokens, so 1 login/day automatically becomes 2. Then, logins aren't shared across devices and 2 additional devices (phone and personal computer) makes 4 logins/day.
Not sure why GitHub expires tokens so quickly, but I can replicate it across every device I own and multiple accounts. Maybe they just don't like me?
Re: Nginx has moved to GitHub
#50Recently, I was browsing an open source project I use a lot. "Sign in to search code on GitHub" was kinda discouraging to see. Sure, I can clone it and run grep/ripgrep - but sometimes I like the ability to search the code on the browser. Is it only GitHub where this is a restriction or GitLab is similar?
This thread from 9 months ago has a bunch of discussion on this. https://news.ycombinator.com/item?id=38432261