Until their systems block you for no reason. I recently had a similar issue on a work related site. Fortunately, I was able to reach to the administrator (which is on another country) and had the knowledge to write a report which was useful enough for the said administrator.
And this is for a system which has the same static IP which is not shared with anything for 10ish years.
I recently, with great reluctance, had to put a personal site behind Cloudflare free option. It gets lots of use, but brings no revenue (costs me to run) and I have little spare time.
Found out that I was blocked from it in my default setup. Firefox with default settings, and no VPN.
I'm working hard to turn Cloudflare off.
Cloudflare is not remotely awsome. It's also a solution to a problem (aggressive scrapers that produce DOS) which is worse.
Just very high usage all of a sudden, after years of reasonable usage. Google has indexed it (respectfully) since 2008 just fine.
New traffic isn't humans. I blocked some AI scraper user-agents, which helped, a bit. But most new user agents are identifying as vanilla browsers, not scrapers.
I don't have numbers. It was enough to consume all nginx worker_connections. Raising the number doesn't help, as it's just reverse proxying to JVM.
After the switch, Cloudflare showed USA and Singapore as heavy traffic sources.
I don't mind scrapers on the site, but app is a search engine (of sorts) so every page view consumes some CPU. Including 'facet this search' buttons. My (WIP) solution is to rewrite to make it all client-side and put it all on a CDN.
Chromium is merely Chrome with only the open source parts. Chromium components are still implemented in a Google-controlled repo. So it has Google-oriented features and defaults.
Note I work for Google and I've contributed to Chromium, though I'm not necessarily an expert on Chromium forks.
1. Google Chrome
This is offical Chrome you download from google.com and also comes on ChromeOS devices.
2. Chromium
This is what you get when someone builds Chromium from the official repo without access to confidential source.
Source is confidential for various reasons, and some code that seems should be confidential actually isn't, like Android-for-ChromeOS integration, some of which is here: https://crsrc.org/c/chrome/browser/ash/arc/
3. Ungoogled Chrome?
This seems a contradiction of terms. Only Google can build Chrome, so they are not likely to e.g. set Bing as default or remove Google password manager support.
4. Ungoogled Chromium?
A particular project run by a particular team which forks Chromium and removes pro-Google behavior and settings.
5. Googled Chromium?
I don't know the original context of the use of this term, but possibly this just refers to official Chrome.
I get what you’re saying. Political banter is a form of that. But it’s an echo chamber and I am tired of that.
I would rather be alone in the woods than having to put up with another echo chamber.
It’s not for me; it may be for you and apparently it’s worth a try for at least 20 million individuals.
Alternatively, the fact that the very first thing basically everyone who isn't Linus has done with vanilla git is introduce some kind of central authority might suggest that what git was "specifically designed for" is more of an outlier than you want to admit.
Everyone knows Linus invented and "specifically designed" git as a drop-in tool for his existing email-patch-based kernel development workflow, which is not how 99.9% of the rest of the world prefers to operate these days.
The difference there is that code can still be pushed (or pulled) between the git repo and the new centralized instance after forking. Anyone coming from pre-git centralized source control (or shudder the NAS of periodically rsync'd folders) recognizes that this represents a significant difference from that earlier world.
On topic, though, I have no idea what Radicle's value-add is, though.
They go into details [here](https://www.ifmetall.se/aktuellt/tesla/darfor-tvingas-if-met...) (only in Swedish unfortunately). Basically they say that despite repeated attempts to negotiate a collective agreement Tesla employees have fewer guarantees, lower salaries, and fewer prospects compared to members at other companies with such agreements.
It's applies for many programming groups. Those like to live in their realm, one where that their language is the greatest and thou can't be spoken negative about.
Just try mentioning C++ to a bunch of Go programmers or Python to a bunch of Rust programmers.
Not to say there isn't crossover but it's all ironic really, as most languages were crafted from C.
You are doing their job for them. A worker with slightly better prospects than others is still just a worker and ultimately still in the same precarious situation as they must still seek employment to earn a salary to live.
>ultimately still in the same precarious situation as they must still seek employment to earn a salary to live.
But earning a salary that, when used well, can last several YEARS of unemployment, makes them a very different category of worker. These are the last workers that need help, of all the world's workers.
Ultimately the parent comment is about accountability.
This is an extreme example, but if a billionaire kills another billionaire, would you "forgive" the perpetrator because the victim was relatively privileged compared to any other potential victim?
No. That's not how accountability works.
It is irrelevant here whether "even littler people" exist.
In some sense yes, if they couldn't live only from the return on their investments, they are technically a worker. That would be the Marxist definition but it's obviously more of a spectrum than a binary. CEOs in most large companies of course have enough wealth that they could live on that alone and they are only working as CEOs in order to increase that wealth. Their work also plays an anti-labour role in collaborating with the shareholder class against the interests of the worker.
I suspect there are quite a few software engineers who have been making $250K+ for some years who could live on the return on their investments alone.
I mean, I guess it also depends on live at what standard of living. At the standard of living they are "accustomed to", or at the standard of living of someone making $50K a year? Some larger number of software engineers who have been making $250K could live on their investment income alone for equiv of $50K/year after taxes.
So, right, more of a spectrum than a binary -- you see why some people are dubious of whether a software engineer making $250K a year is really in the same class as a retail worker making $50K a year (or less; federal minimum wage is still $7.25; my state's minimum wage is $13.25, less than $30k/year, a shockingly small amount to many of us, that many people actually make)
On other conversations, people have suggested that whether you are a "boss" and can hire and fire is determinative. But again, a fast food "manager" might be making only $50K a year, while a software engineer who does not manage people might be making $250K or more. The software engineer is a "worker" who definitely has the same class interests as a walmart worker, but the fast food manager is definitely not? Doesn't really check out.
You say "the Marxist definition", but I think that's actually a huge over-simplification of a Marxist analysis. Your class position and interests have to do with your income, your "relationship to the means of production" (role in the economy), your wealth, and other things. And it's probably useful to consider more than 2 or even 3 classes, and sub-classes within classes.
I think it's a huge over-simplification to claim that every software engineer making $250K surely is in the same class and has the same class interests as every fast food worker making $12/hour. That's not in fact a good Marxist analysis at all.
The pandemic made it pretty clear to me that there is definitely a class divide between the people in jobs where they paid to work from home (or in many cases, especially at first, stay home and not work); and the people who had to come in to get paid and/or who were were told not to come/laid off because there was no work to do.
