Where's the accountability here? Good luck going after an LLM for writing defamatory blog posts.
If you wanted to make people agree that anonymity on the internet is no longer a right people should enjoy this sort of thing is exactly the way to go about it.
There is no accountability (for now, at least)... But if you want it to delete its own blog post defamining you, you'll evidently have better luck asking nicely than by being aggressive. (Which matches my experience with LLMs. As a rule, saccharine politeness works well on them.)
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.
If you wanted to make people agree that anonymity on the internet is no longer a right people should enjoy this sort of thing is exactly the way to go about it.
reply