Do you have some data on that ? Because the majority of people inside far-left organizations are just not, and I don't base that on superficial myths but on actually talking with people
I'm sorry but this is just too naive. There is no honesty in most people working for a wage that is barely enough to survive, while capital owners don't actually do anything and still receive an inconsiderate amount of money. There is no trading here, just a good old theft of all the produced value with just enough redistribution to buy back the stolen value. No billionaire ever became billionaire by trading anything only by stealing other's work.
That's assuming that the population has any power, which in pretty much all countries in the world is not true. "Democracy" isn't just a value to behold, if the population has no power, it has no power and a country can't be called as such out of nowhere. Now, the people might have no actual power, but it's in their hands to get it.
> Western-style billionaires do the former, as their wealth is created by providing services to people
I'm sorry but this is just not based on reality. Wealth has always been formed by taking away from those who produce value. No one asked for 1000 new phone models every year, no one asked for 1000 new car models every year, no one asked for a million new kind of clothes every year. Services aren't provided, they are forced on people who just are not allowed to function without them and must work with and in those services, while billionaires don't produce anything, don't do anything yet get all the money.
If it's a common enough occurrence to have _all_ your nodes down at the same time maybe you should reevaluate your deployment choices. The whole point of multi-nodes clustering is that _some_ of the nodes will always be up and running otherwise what you're doing is useless.
Also, garage gives you the possibility to automatically snapshot the metadata, advices on how to do the snapshotting at the filesystem level and to restore that.
> Ahead of the International Women's Day, a UNESCO study revealed worrying tendencies in Large Language models (LLM) to produce gender bias, as well as homophobia and racial stereotyping. Women were described as working in domestic roles far more often than men ¬– four times as often by one model – and were frequently associated with words like “home”, “family” and “children”, while male names were linked to “business”, “executive”, “salary”, and “career”.
> Our analysis proves that bias in LLMs is not an unintended flaw but a systematic result of their rational processing, which tends to preserve and amplify existing societal biases encoded in training data. Drawing on existentialist theory, we argue that LLM-generated bias reflects entrenched societal structures and highlights the limitations of purely technical debiasing methods.
> We find that the portrayals generated
by GPT-3.5 and GPT-4 contain higher rates
of racial stereotypes than human-written por-
trayals using the same prompts. The words
distinguishing personas of marked (non-white,
non-male) groups reflect patterns of othering
and exoticizing these demographics. An inter-
sectional lens further reveals tropes that domi-
nate portrayals of marginalized groups, such as
tropicalism and the hypersexualization of mi-
noritized women. These representational harms
have concerning implications for downstream
applications like story generation.
The internet and the web were, and still are, made by and for white rich men. It's not about who can be a prick, everyone can. It's about what the ecosystem pushes towards, and it's not the safety and general good life of women, black people, handicapped people, etc...
That's why you need to go to other regions, not remain in the same area. Putting all your eggs in one basket (single area) _is_ stupid. Having a single shutdown command for the whole cluster _is_ stupid. Still accepting writes when the system is in a degraded state _is_ stupid. Don't make it sound worse than it actually is just to prove your point.
I disagree that it's bad, it's a choice. You can't protect against everything. The team made calculations and decided that the cost to protect against this very low probability is not worth it. If all the nodes lose power you may have a bigger problem than that
I don't understand this article and It's like the author doesn't really know what they're talking about. They don't want eventual consistency, they want read-your-writes, a consistency level that's stronger than EC yet still not strong.
Read-your-writes is indeed useful because it makes code easier to write: every process can behave as if it was the only one in the world, devs can write synchronous code, that's great ! But you don't need strong consistency.
I hope developers learn a little bit more about the domain before going to strong consistency.
> When you run a business, you can’t realistically perform background checks on every partner or contributor
You can, and that depends on whether you want to or not. No one forces you to run a business. You're not absolved of the chore of having a look at your supply chain just because you're disinterested in it
AP, even in its purest simplest form, already allows to "revive" and "remix" data: you have the JSON of the data, you can do whatever you want with it. You can build a product injecting JSON of this data, just like in AT, but those product don't really exist so even if I can say "yes you can fork them" it's all talk.
There's no talk about migration in the core spec, but how is it in ATproto in practice ? Does everyone carry their entire repository, live from their own PDS, ready to be remigrated somewhere else ? It does feel like in AT-in-practice people just have a PDS and that's it ? (I've never used it, I might be totally wrong)
Really, if you want a simplistic view of AP, it's easy: it's an INBOX where you receive content, and an OUTBOX where you send content, and the content is activitystreams-formatted JSON. Anything else just makes it easier to work with.
That's a purely personal point of view but I don't think the AP people claim that "people want the wrong things", but rather that "the things you want have a cost and we're not hiding it".
The fact that likes count and half the replies are missing is not specific to AP but to implementations not willing to actually follow the AP community: in fact the SocialHub (https://socialhub.activitypub.rocks/) community is the place where all coordinated development happens, and solutions to those issues have already been designed and implemented in multiple softwares, with the notable exception of Mastodon. Maybe that's the issue: people keep looking at Mastodon to understand AP, but Mastodon is one of the worst examples of AP, even when talking only about the technical domain. It doesn't implement the C2S API, it doesn't have portability, likes counts and missing replies as you said, ...