Join us for today's live stream of #MAIHT3k in about 2.5 hours, at https://www.twitch.tv/dair_institute.

Calling Mystery AI Hype Theater 3000 fans --- want to join us for the livestream? Next chance is today!

@alex and @emilymbender will be joined by @hypervisible

Ever wondered how to tackle #multilinguality in #digitaleditions? In our @up_johd contribution (https://doi.org/10.5334/johd.174) we describe how we tackled #codeswitching, Early New High German #normalisation, #machinetranslation, and #HTR for #Bullinger's multilingual correspondence. The results are all on bullinger-digital.ch. And should be at the #openUpEditions conference @uzh_zde right now and have questions, feel free to ask. #digitalhumanities

An der Oldenburger Universitätsbibliothek gibt's zwei unbefristete E13 (100%, aber auch teilzeitgeeignet) zu besetzen:

- 1 Referent:in für Digital Humanities
und
Fachreferent:in für geistes-, kultur- und/oder sprachwissenschaftliche Fachgebiete (m/w/d) https://uol.de/stellen?stelle=70063

- 1 Direktionsreferent:in und Fachreferent:in (m/w/d) https://uol.de/stellen?stelle=70064

#dh #dighum #fachreferat #wissbib #bibliotheken #job #humanities #libraries #librarians

Ich suche einen Artikel oder ein Kapitel, dass die Probleme mit (digital humanities) Daten einmal benennt, also die Problematik von Atomatisierung (komplexer Kontextdaten) , Normierung (z. B. verschiedener Schreibweisen) , Auflösen von Co-Referenzen und Mehrdeutigkeiten, eindeutige Identifizierung von Entitäten, Konfrontation mit unvollständigen, unsicheren, Fehl- und Falschinformationen. Gerne auch englischsprachig #dh #DigitalHumanies #datamodeling

Die Rolle des Absatzes im Lesen und Schreiben wissenschaftlicher Texte wird hierzulande verkannt. Anders ist es in englischsprachigen Ländern: Keine Einführung in das wissenschaftliche Arbeiten kommt am topic sentence vorbei. Im Deutschen gibt es nicht einmal einen Begriff dafür.

Warum das Lesen und Schreiben in Absätzen auch an deutschen Universitäten als Schlüsselkompetenz anerkannt werden sollte, erklärt Kornelia Kończal bei ➡ Geschichtswissenschaftsdidaktik: https://gwd.hypotheses.org/1236

#gwd

#metadata und #hamburg #E11 / #A11 mit flachen Hierarchien und viel Blick über den Tellerrand und dann noch im #fediverse unterwegs ✊

Dann ist die #tuhamburg als Arbeitgeber eine sichere Wahl #bibliojobs
https://stellenportal.tuhh.de/dxo9e

There will be a 3-day scientific conference about the #Commodore64 / #C64 at the SRH (Heidelberg) this year - organized by Jens Schröter (Media Studies, University Bonn) and me. We've just started the plannings ...

Stay tuned for more information!

Can we just stop using Discord and go back to using forum sites?

I realize it's (comparatively) super easy to set up, but y'all realize it's just going to bite us all in the ass as soon as someone at Discord decides they need to turn up the profit ratio?

It's a ticking time bomb. The whole thing is going to follow the enshittification process, and anything of value on there is going to be lost/sold/destroyed.

From my perspective, professional forms should work without client JavaScript by default. They should validate on the backend providing good feedback on any problems with the input while persisting valid values until the form can be completed. Once those things work: go to town with the client code to make the experience even better.

If your framework doesn't support basic web form requirements it's not very helpful. In the case of React it's been frankly harmful to end users experiences.

Gerade in einer Rasierwerbung <hello, world/> gesehen. Schon gut gedacht, aber beim nächsten Spot besser wohlformen als <hello_world/>. 😎

I wrote about the genocide in Palestine, and how tech has been silent and complicit.

https://blog.paulbiggar.com/i-cant-sleep/

Something I’ve been thinking about a lot in the current battle over the future of (pseudo) AI is the cotton gin.

I live in a country where industrial progress is always considered a positive. It’s such a fundamental concept to the American exceptionalism claim that we are taught never to question it, let alone realize that it’s propaganda.

One such myth, taught early in grade school, is the story of Eli Whitney and the cotton gin. Here was a classic example of a labor-saving device that made millions of lives better. No more overworked people hand cleaning the cotton (slaves, though that was only mentioned much later, if at all). Better clothes and bedding for the world. Capitalism at its best.

But that’s only half the story of this great industrial time saver. Where did those cotton cleaners go? And what was the impact of speeding up the process?

Now that the cleaning bottleneck was gone, the focus was on picking cotton as fast as possible. Those cotton cleaners likely, and millions of other slaves definitely, were sent to the fields to pick cotton. There was an unprecedented explosion in the slave trade. Industrial time management and optimization methods were applied to human beings using elaborate rule-based systems written up in books. How hard to punish to get optimal productivity. How long their lifespans needed to be to get the lost production per dollar. Those techniques, practiced on the backs and lives of slaves, became the basis of how to run the industrial mills in the North. They are the ancestors of the techniques that your manager uses now to improve productivity.

Millions of people were sold into slavery and worked to death *because* of the cotton gin. The advance it provided did not, in fact save labor overall. Nor did it make life better overall. It made a very small set of people much much richer; especially the investors around the world who funded the banks who funded the slave purchases. It made a larger set of consumers more comfortable at the cost of the lives of those poorer. Over a hundred years later this model is still the basis for our society.

Modern “AI” is a cotton gin. It makes a lot of painstaking things much easier and available to everyone. Writing, reading, drawing, summarizing, reviewing medical cases, hiring, firing, tracking productivity, driving, identifying people in a lineup…they all can now be done automatically. Put aside whether it’s actually capable of doing any of those things *well*; the investors don’t care if their products are good, they only care if they can make more money off of them. So long as they work enough to sell, the errors, and the human cost of those errors, are irrelevant. And like the cotton gin, AI has other side effects. When those jobs are gone, are the new jobs better? Or are we all working that much harder, with even more negative consequences to our life if we fall off the treadmill? One more fear to keep us “productive”.

The Luddites learned this lesson the hard way, and history demonizes them for it; because history isn’t written by the losers.

They’ve wrapped “AI” with a shiny ribbon to make it fun and appealing to the masses. How could something so fun to play with be dangerous? But like the story we are told about the cotton gin, the true costs are hidden.

#ML #TESCREAL

MorganaXProc-III 1.3 is out. New features (e.g. support for p:ixml) and minor bug fixes.
#xproc
https://www.xml-project.com/

I just upgrade #Emacs to 30, since in this version #eglot can handle #jdtls (java lsp) code actions. Besides, I also find some newly added options looking attractive.

1. completion-preview-mode: inline compilation preview (preview the first completion candidate) just like corfu-candidate-overlay, but it seems more smooth and efficient and works with any completion methods.
2. flymake-show-diagnostics-at-end-of-line (see the picture)
3. :vc configuration option, which means you can directly use use-package to get packages from version control repos without using elpaca or straight, etc. ( Though I haven't use this option yet.)

Edit: you can also get the periodically released eglot from GNU ELPA.

#Emacs30