Nic @nicolagi@mastodon.sdf.org

Got this from my GF, it made my day

SDF aNONradio is celebrating 25 years on September 7th. Here is a little blurb from the Honolulu Weekly October 8th, 1997 asking the question: "The Internet has been touted as the public square of the Global Village. but does it have a decent radio station?"

How many of these are still around today? Come and party with us September 7th, 2021!

https://aNONradio.net

#bbs #community #radio #birthday #celebration #party #dj #music #stream

http://9p.sdf.org is a growing community! We are open - Join us today!

#plan9 #9front #experimental #unix #hacking #learning #community #new #introduction

@djsundog @phooky modern DRAM is so challenging to initialize that the cpu runs in Cache-As-RAM (CAR) mode until it the x86 firmware blob has finished link training.

Webkit's source code:

if(amazon || google){

}

Haha, HAHHhahaha

https://github.com/WebKit/WebKit/blob/31b77296cf6d85c40313812d9f65a003cf41f440/Source/WebCore/page/Quirks.cpp#L410

Here's my mind-blowing video for today:

https://www.youtube.com/watch?v=zQo_S3yNa2w

@chaosmonk thanks 😊 I love how 9front forces me into a more slow computer life. I keep the frenzy state of modern computing on my work machine and my pocket device and so far so good!

In Plan 9, the same idea is used to support both containers and VPNs, and it knows of neither

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.

#Newsgroups in 2020 with #tin and #Thunderbird
http://ffuentes.sdf.org/communication/2020/10/20/newsgroups-tin.html