Square Singer @ squaresinger @feddit.de

Posts

23

Comments

1,275

Joined

2 yr. ago

The poster before has a point. The translation in the video is pretty damning, but there is no real way to know if the translation is truthful if all you have is that video and not the ability to understand the original.

Did you read what the addon is about? It's not an adblocker but is to be used in conjunction with one. All it does is circumventing the adblockerblocker. It specifically recommends being used together with uBlock.

Btw, I use FF with uBlock. But I am not everyone, so when I stumbled across this, I thought it might be helpful for some people.

And I found it ironic, that Googles own extension store contains an extension that circumvents the YouTube adblockerblocker.

https://chrome.google.com/webstore/detail/youtube-anti-adblock-bypa/gbghmolkliahkeekflofoaiofibligjf could help as well.

Both versions exist: https://en.m.wikipedia.org/wiki/Doctor_(title)#Abbreviation

In German, we too have words that only survived in specific versions. What's really weird is that we have words like that, that died out, but a specific form survived, and then the word gets re-imported from another language with a slightly different meaning.

Take for example "Rasse" (race) and "Rassismus" (racism).

In German before WW1 the word "Rasse" was used to differentiate between the locals and the neighbouring "others". So the usage was like "the German race", "the French race", "the English race", "the Jewish race" and so on. After WW2 that word just about disappeared from the German language because it was used so heavily by the Nazis and also because it had no real meaning. They also used terms like "the Human race". So race could be anything from "speaks another language but looks exactly like me" to "species". It was almost exclusively (except for "the Human race") used to dehumanize the others.

But the term "Rassismus" survived and it's meaning is about the same as xenophobia in English. Thus, if a white person from France hates everyone from Belgium, that's racism.

In the USA on the other hand, the word "race" was used to differentiate between the white population (which came from all over Europe) and the "others", which in this case were Africans, Native Americans, Asians and South Americans. Like with the term "Rasse", "race" was also used to dehumanize the others. And accordingly, "racism" only applies when someone hates people of another race by the USA definition. But unlike in German, the USA was never ruled by Nazis, and thus the word "race" was never discontinued.

And now the English word "race" is getting re-imported to the German language, but with the US meaning, because there is no German meaning left.

So right now in the German language, "Rasse" means Black, White, Asian, ..., while "Rassismus" can totally be against someone who is of the same "Rasse" but speaks another language or is from another country.

Any block is a swastika block if you ignore the right set of roads.

But that's not the block's fault ;)

Which is kinda weird in it self, because when abbreviating you not only change the words but even the language.

Hardly anyone would ever write "exempli gratia" in a normal text, and "f.e." would also not be understandible for most people.

So in regular use, "e.g." is practically the abbreviation for "for example"

But if you enable "Avoid crossing perimeters" this problem will still not occur.

Since OP mentioned a switch from Marlin to Klipper, it could also be acceleration settings or something like it.

Might be. I'm neither Brit nor American, so I learned both.

Hopefully. Because right now this is not a simple bug but engrained in the core concept of how Lemmy works.

Sure the designers of this monstrosity thought, "There are only black people living there, so it's a win-win" -.-

Lemmy is setup quite ok to scale users and traffic, since the users are (theoretically) distributed over many instances. In reality it doesn't work out perfectly, since people generally are more likely to join the biggest instances, so there's quite an imbalance there.

But what's worse is content replication. As soon as an user requests to look at a community for the first time, the whole community will get completely replicated on that user's instance. So any decently sized instance will pretty much replicate almost all communities, at least all that have content.

There is no scaling or storage balancing mechanic here. Even if no user ever touches that replicated community again, it will continue to be replicated, will fetch all new posts/comments and store them in the instance.

There is also currently no workaround to this (like there is for users/traffic, which you can just tell to join a different instance).

So if Lemmy ever gets to the point where gigabytes of data gets posted every day (which is only about 1000 pictures a day) storage demand will get so high, that hosting an instance will be seriously costly, which will probably lead to instances without any kind of cash flow shutting down, which will in turn lead to more users and thus traffic on the remaining instances.

I guess, that's one of the biggest technical (and conceptual) roadblocks that need to be addressed if Lemmy ever grows that big.

Potential solutions:

• Coasting/Wiping before travel
• Linear Advance
• Tuning retraction
• Or completely side-step the issue by turning on "Avoid crossing perimeters"

The last one should really be default-activated. It avoids so much stringing and ugly outside surfaces.

Yeah, it's really hard to pinpoint such simple inventions.

Correct :)

Maintaining Open Source without being paid by a company to do so is terrible. I made a few Open Source projects and never will I do it again. I do contribute a fix or something every once in a while if the issue really annoys me in my usage, but I will never again take any active role in an open source project.

People take your work for free and then attack you for not doing everything they ask for, equally for free. It's just not sustainable.

The U2 metro line. No way in hell would I use the highway parallel to it in rush hour. There are many nicer parking spots than that highway.

Both Dr and Dr. are possible.

But shouldn't "w/o" then be written as "w/o/"?

And "N/A" omits more than one sylable in "applicable".

I guess it's a grown system.

Massive amounts of federation ;)

It's really hard to get thousands of software development companies, hundreds of thousands of hosters and billions of users to unitedly go for a new thing.