161–170 of 170 posts
Centralise all the things. There is too much stuff of GitHub. From a resiliency point of view and from a monopoly point of view this is bad.
Earlier quoted context omitted.
You must surely know that people use Microsoft GitHub for far more than source control, right?, with issue tracking, email notification, CI, and GitHub Actions. I recently tried to get a small FOSS project to switch to Codeburg. The answer was "no" because the free CI for them let them catch some MacOS on Apple Silicon bugs (the devs don't have that hardware locally), and because they are already used to GitHub, maki…
So what's the problem? GitHub gives you a bunch of free stuff that would be pretty annoying/expensive to self host. Seems like a good deal. If they remove some of that stuff, that would be worth complaining about. Until then, seems smart to take advantage of what GitHub is offering. Their CI isn't even super proprietary, you can basically just write bash scripts.
By then it’s too late, because there’s no alternative.
Earlier quoted context omitted.
The state of nginx is fine, similar to pfsense. Both made a "Plus" enterprise support offering, open source clones were forked, the originals remain dominant for enterprise and free users anyways. Not to detract from the great projects that are being worked on, like freenginx and opnsense.
> the originals remain dominant for enterprise and free users anyways. I'm a former pfSense user that reluctantly moved to OPNsense a handful of years ago after a lot of bad press around Netgate started circulating widely causing me to believe that support for the community offering might wane over time. I was under the impression that many people had moved off of pfSense for home use. I'm surprised by your assertion…
Well, it works.
But try to add some custom parameters to a daemon, which aren't listed on the page. Or try to run more routers than one. Or diag network states even on 4k monitor.
There are a thousands cuts using OPNsense in anything more than a home router. Despite ten years of trying this year I ripped it off where it was installed and replaced back with pfSense.
Earlier quoted context omitted.
> The alternative is having to do captchas and the like to use those features anonymously This is not the case. You may have noticed that Google Search, Bing, etc. don't require login or captcha to do a search. Billions of people use this search daily. And yet, they will throw a captcha at you, or even just say "you're a bot, stop bothering us" whether you're logged in or not , if their signals have detected what the…
For the last seven months, Google has pushed every non-login search from my house network through a captcha; the image captcha is typically five to infinite repetitions. Audio captcha works after a single run-through, except that it is frequently "unavailable" now. I don't know why. Google won't tell me. They just started doing the same for YouTube: "Please login because we have detected malicious behavior from your…
My solution was to use a filtering DNS that always returns no AAAA records for domains ending in google.com. This works great and essentially solves the problems. I have to do the same for various netflix domains as well.
I'm dreading having to switch over to native IPv6 -- I don't even know how many /64s will be allocated to me (and how stable they will be).
Earlier quoted context omitted.
Can you please cite some recent examples of this clownlike behavior?
They harassed the OPNsense team, registering a domain to besmirch them and then pretended to have nothing to do with it until ICANN got involved Oh, and they knowingly shipped a broken and insecure Wireguard to their customers, and tried to use their FreeBSD commit status to force it upstream
Earlier quoted context omitted.
Can you please cite some recent examples of this clownlike behavior?
Try compiling pfSense. No, here's an even simpler task: try compiling packages for pfSense. The clowns from Netgate made it unbelievably difficult, for no good reason other than being antagonist to the open source community.
Earlier quoted context omitted.
For the last seven months, Google has pushed every non-login search from my house network through a captcha; the image captcha is typically five to infinite repetitions. Audio captcha works after a single run-through, except that it is frequently "unavailable" now. I don't know why. Google won't tell me. They just started doing the same for YouTube: "Please login because we have detected malicious behavior from your…
In my case, they block me on IPv6 since I use a Hurricane Electric IPv6 tunnel. It certainly used to be the case that my IPv6 connectivity was better and more performant down the tunnel than using my ISPs native IPv6. I have no idea what the situation is today. My solution was to use a filtering DNS that always returns no AAAA records for domains ending in google.com. This works great and essentially solves the probl…
Earlier quoted context omitted.
The OP is literally standing outside the restaurant looking through the window and complaining about not being allowed to eat for free. > GitHub is still getting lots of data from people without accounts This doesn't matter. If you want code search, you must log into a free account. Why is this controversial? Github isn't a charity - they don't exist to benefit freeloaders that won't even create a free account. Life…
Your version of the analogy makes no sense, because the people with accounts are also eating for free. If data is payment, then both groups are paying. If data isn't payment, then what is? Please elaborate on what distinguishes the groups, and how people with free github accounts fit into the analogy.
The parent complaining about creating a free account can just keep complaining, or create one, I don’t care. But this nonsense about cost for search is not the issue.
Earlier quoted context omitted.
In my case, they block me on IPv6 since I use a Hurricane Electric IPv6 tunnel. It certainly used to be the case that my IPv6 connectivity was better and more performant down the tunnel than using my ISPs native IPv6. I have no idea what the situation is today. My solution was to use a filtering DNS that always returns no AAAA records for domains ending in google.com. This works great and essentially solves the probl…
This could very well be the answer. I'll go check.