zerakith

"Enjoys" is not how I would describe it.

I won't rehash the arguments around "AI" that others are best placed to make.

My main issue is AI as a term is basically a marketing one to convince people that these tools do something they don't and its causing real harm. Its redirecting resources and attention onto a very narrow subset of tools replacing other less intensive tools. There are significant impacts to these tools (during an existential crisis around our use and consumption of energy). There are some really good targeted uses of machine learning techniques but they are being drowned out by a hype train that is determined to make the general public think that we have or are near Data from Star Trek.

Addtionally, as others have said the current state of "AI" has a very anti FOSS ethos. With big firms using and misusing their monopolies to steal, borrow and coopt data that isn't theirs to build something that contains that's data but is their copyright. Some of this data is intensely personal and sensitive and the original intent behind the sharing is not for training a model which may in certain circumstances spit out that data verbatim.

Lastly, since you use the term Luddite. Its worth actually engaging with what that movement was about. Whilst its pitched now as generic anti-technology backlash in fact it was a movement of people who saw what the priorities and choices in the new technology meant for them: the people that didn't own the technology and would get worse living and work conditions as a result. As it turned out they were almost exactly correct in thier predictions. They are indeed worth thinking about as allegory for the moment we find ourselves in. How do ordinary people want this technology to change our lives? Who do we want to control it? Given its implications for our climate needs can we afford to use it now, if so for what purposes?

Personally, I can't wait for the hype train to pop (or maybe depart?) so we can get back to rational discussions about the best uses of machine learning (and computing in general) for the betterment of all rather than the enrichment of a few.

Not irrational to be concerned for a number of reasons. Even if local and secure AI image processing and LLMs add fairly significant processing costs to a simple task like this. It means higher requirements for the browser, higher energy use and therefore emissions (noting here that AI has blown Microsoft's climate mitigation plan our of the water even with some accounting tricks).

Additionally, you have to think about the long term changes to behaviours this will generate. A handy tool for when people forget to produce proper accessible documents suddenly becomes the default way of making accessible documents. Consider two situations: a culture that promotes and enforces content providers to consider different types of consumer and how they will experience the content; they know that unless they spend the 1% extra time making it accessibile for all it will exclude certain people. Now compare that to a situation where AI is pitched as an easy way not to think about the peoples experiences: the AI will sort it. Those two situations imply very different outcomes: in one there is care and thought about difference and diversity and in another there isn't. Disabled people are an after thought. Within those two different scenarios there's also massively different energy and emissions requirements because its making every user perform AI to get some alt text rather than generate it at source.

Finally, it worth explaining about Alt texts a bit and how people use them because its not just text descriptions of an image (which AI could indeed likely produce). Alt texts should be used to summarise the salient aspects of the image the author wants a reader to take away for it in a conscise way and sometimes that message might be slightly different for Alt Text users. AI can't do this because it should be about the message the content creator wants to send and ensuring it's accessible. As ever with these tech fixes for accessibility the lived experience of people with those needs isn't actually present. Its an assumed need rather than what they are asking for.

I was experiencing with both X11 and Wayland. I'll give 555 a test. Thanks!

Were you having any kernel panics before this beta?

I was having this issue https://forums.developer.nvidia.com/t/series-550-freezes-laptop/284772/163 I disabled the GPU for the time being and was hoping the new driver would fix.

Me too. Noticeable Delay around 6s.

I hope Nix sort it out too because technically I think its one of the better options for packaging.

It's not about "satisfying the minorities". It's about ensuring a basic base level of respect and behaviour for people from all backgrounds. The roles you are talking about were specifically to deal with the fact there was an active problem around that minority in that community that needed dealing with. So bringing in that lived experience is absolutely important. Someone can be adequate, sane, have "proper" mindset and judgement and be from a minority that is currently being targeted with lived experience of the problem. Dealing with issues around diversity and inclusion make life easier and better for everyone: it's well evidenced. I benefit daily from work that's been done to make my area easier for people with disabilities despite not having one. Those only came about by people with disabilities challenging and getting in the room where decisions are made.

It's really not that hard! If you don't feel minoritised in your daily life and therefore don't see the importance, fine, but all of us are only one incident or cultural shift to end up being the target so if you aren't motivated by the plight of people you are happy to "other" than do so because one day you might be the other.

You say remove discrimination and then use a discriminatory strawman. No one is suggesting a code contribution must be accepted based on a minority status. They are saying that to get a decent functioning community for everyone you need a diverse range of people in positions that set the behaviour of the community. You can't get the CoC and enforcement of it right unless those affected are in positions that influence it. Your enforced anonymity doesn't work because there are other ways of gendering and racialising people (e.g. based on who people talk). Additionally, what you are saying is that minoritised people have to hide who they are so they don't get discriminated against rather than just deal with those doing the discrimination. They are called communities because that's what's they are: people want to be part of something and that involves sharing a part of themselves too. Open source projects live or die on their communities because they mostly don't have the finances to just pay people to do the work. You need people to beleive in the project and not burn out etc.

You lose nothing by making sure people from all backgrounds have the same opportunity and enjoyment being part of it. If you aren't in a minority and don't care about those that are then just say so!

Others have replied pointing out this is a strawman and that merit doesn't make any sense as a metric if you have discrimination. In practice performance ('merit') is complex interaction between an individual's skills and talent and the environment and support they get to thrive. If you have an environment that structurally and openly discriminates against a certain subclass of people and then chose on "merit" you are just further entrenching that discrimination.

This is a project that seemed to be having specific problems on gender that was causing harm and leading to losing talent. In a voluntary role particularly this is a death spiral for the project as a whole. Without goodwill and passion open source projects of any meaningful size just wouldn't survive.

I'm glad you care enough about diversity and evidence to have worked out how to solve these problems without empowering and listening to those minorities. Please do share it.

This is a basic represention and inclusion issue. Unless you are actively seeking out voices of those minorities and addressing their concerns you will have a reinforcing loop where behaviour that puts people off engaging will continue and it will continue to limit people from those minorities being involved (and in the worst case causing active harm to some people who end getting involved). From what I understand the behaviour that has been demonstrated and from who those people leaving it is clear this is active issue within Nix. Having a diverse range of people and perspectives will actually make the outputs (software) and community generally better. It's about recognising the problems in the formal and informal structures you are creating and working to address them.

Additionally, but just to clarify nepotism would be giving positions based on relationships with people in power and not ensuring that your board contains a more representative set of backgrounds and perspectives.

I looked at the agreed changes for 41 but couldn't see any accessibility. Do you know what changes are coming?