@helix @fribbledom Of course not, but if you scale it to 1.5 (Iwould go with 1.75 probably) you still benefit from increased sharpness

@kunsi Telegram für alles, was irgendwann mal Probleme gemacht hat (aber auch banales Zeug wie updates verfügbar)

Justus boosted

git changing master to main by default 

The argument against the word "master" is based on the unproven assumption that the term is loaded with racist connotations, and the mandate for change is based on the fact that the possibility of the assumption's truth is nonzero and that the side-effects of the change are small.

If that were true, I would be on board with it. However, it's plainly clear that the impact of git upstream switching the default branch name to "main" is going to be huge. Many scripts with the "master" hard-coded are going to break, scripts written on the valid assumption that the name "master" was an intrinsic, unchanging property of git.

Every programmer who works with repositories before and after the change are going to constantly mis-remember which is which, and we'll have to guess at the default when working with new or unfamiliar repositories.

This event is going to establish a new epoch in git. We should take that seriously.

Which means we have to confront the fact that the assumption (that inherent racism is present in the word "master" and is causing harm to those who have suffered under racism) may not actually be true. The claims do not hold up well under scrutiny. And, as far as I can tell, the cause is championed disproportionately by white people.

The moralized nature of the question puts an external pressure on decision makers on the git project, which is normally not present for other patches. They have to consider, if they review these changes negatively, will it affect their personal reputation? Their careers? If there's even a slight chance of this, is it better not to argue the matter at all, and rubber-stamp the patches? I don't think this change is being developed under the right conditions.

On the left, we have a tendency to rubber-stamp social causes with a lesser degree of scrutiny. I think that this is a testament to how much we value empathy and solidarity, but I don't think it's a healthy way to approach our problems. Software breakage has a social cost, too.

@tjb @sir I find the UI to be more intuitive than those bloated ones. Every time I click a button, I realize "That was made by someone who thinks like me"

@sir so where is the project where I can contribute?

@sir Club scenes are worse. Not just flinshing but also missing it so much

Justus boosted

Still flinching when I watch a beforetimes video or movie and notice no masks in large crowds or public places

@SevenOfNein Finde gopass super, für den sync brauchst du nur n git-repo

@sir China educates people well and has zero liberties

Justus boosted

@kunsi @sqozz Konfigurierbar ohne Aufpreis. Das wär natürlich das absolute Optimum

@sqozz @kunsi Jein. Ich meine, wenn normale Heimrouter n NAT auf prefix::1 implementieren, ist das ja egal ob v4 oder v6. Und wer das nicht will, routet die Adressen direkt. Das ist imho nicht Schuld/Aufgabe der ISPs, die sollten brav n /64er vergeben und routen.

@sqozz @kunsi Äh, ja. Statische IPs sind ne Datenschutzkatastrophe und die Leute die das wollen sollten dann halt nen Geschäftsanschluss/Whatever kaufen

@bionade24 @fribbledom And if you don't live in Bavaria, you can easily DIY it. Normal yiest dow, shaped in Brezen-shape, add some kind of food-grade alkaline sodium solution (sodiumcarbonate is easily available), sprinkle on salt crystals, 10 mins in the oven, done.

@sir I would love to have one specialized to code hosting sites. Github, Gitlab, Gitea, Sourcehut, etc with specific filters like programming language etc

@ubernauten Wie schön zu sehen, dass ihr im Zweifelsfall auch für das einsteht, was ihr so propagiert. Einmal ganz viele Kudos!

Show more
Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!