As part of #PalaeographySchool23, we'll be using the MUFI Unicode specifications for transcription. I've created a spreadsheet of the codes, divided by category, which will be added to by the students. If others will find this useful, I can make it publicly available at the end.
The file does not yet have a complete selection of codes/signs (e.g. I still need to add all the p and q variants), but this may be useful to some of you. If you send me additional codes, I can update and put this up again in October.
Please note you need to install a font like Junicode in order to be able to see all the signs!
[Question] Harbor registry with Ingress on a k3d cluster
Hi, Has anyone tried to enable #ingress + #certmanager on a #k3d cluster while installing #harbor registry via #helm ? Any inputs on how to achieve this on macos? TIA
Still calibrating the Lynx
Dinner was carrot mint salad, shoshito peppers, and #kenjilopezalt BBQ chicken. Note to self - turn the heat down on the gas grill... @food@cooking
Bisher waren alle Rennen Zeitrennen. Ich mache sie auch nur einmal, um mehr über Geschichte von Maurice zu hören.
Zum Glück muss man sie dafür auch nicht erfolgreich abschließen.
In brief: I'm still not sure how much #AltText is optimal. And I tend to run into situations in which alt-text that describes everything in a picture will grow longer than any of you could possibly imagine in their wildest dreams.
Here's my situation:
I don't have a problem with writing a lot. Unlike most of you, I'm not on a phone. I'm on a desktop computer, and if I'm not, I'm on a laptop. I've always got a full-blown hardware keyboard, and I can touch-type with ten fingers. And I like to rant.
I'm on #Hubzilla. This means virtually no limit in post length and especially virtually no limit in alt-text length. The only limiting factor would be how much alt-text the instances where my posts are viewed can display. #Mastodon has a hard cap at 1,500 characters, for example.
I'm not the one to skimp on #accessibility rules unless they're technologically impossible for me to follow. I'd rather do too much than too little. This includes full transcriptions of all texts in a picture unless privacy issues speak against it, or unless I've got no way to source the original of a text anymore, and said text in the picture is ineligible even for me. Yes, I transcribe text that's one pixel high if I can get the original.
When I post pictures, I don't always post them Instagram/Pixelfed-style, i.e. posts that are about this particular picture. Instead, I often use pictures to illustrate the post. Hubzilla gives me all necessary means to write full-blown blog posts with all bells and whistles as regular posts. Describing a picture in the visible part of a post when the post isn't about the picture is horribly bad style. Doing so when there are multiple pictures in one post, regardless of whether Mastodon puts them in the right places (which it doesn't), is even worse.
I usually post pictures taken in #VirtualWorlds. In comparison with pictures taken in real-life, they have a much higher tendency to contain things that need to be described, often to both sighted and blind or visually-impaired users, because they simply don't know them, be it objects, be it locations. It's one thing if a picture was taken on Times Square, and it's something else if a picture was taken in a place of which maybe not even five people in the whole Fediverse even know that it exists. Thus, more text is needed.
Now there are two schools of thoughts when it comes to alt-text.
One: clear and concise alt-text. Only describe what's necessary in the context in which the picture is posted. Screen readers can't handle long alt-texts well. You can't navigate alt-text with most screen readers, i.e. you can't stop it somewhere, rewind it to a certain point and listen to parts of it once more. All you can do is let the screen reader rattle down the whole alt-text in one chunk. If you need to hear it again, you have to hear all of it again.
The obvious downside of this is that most of the content of the image is lost to everyone who isn't sighted, and some is lost to those who can't identify it even by looking at it in that particular picture.
Two: full description of absolutely everything in the picture plus explanation if necessary. Denying non-sighted people the chance to experience everything that's in a picture, and be it through words, can be considered ableist. Also, tiny details that are barely visible in the picture could be described so that sighted people can identify them.
And besides, there's the idea that alt-text can help everyone understand what that is that they see (or don't see) in that picture if they're unfamiliar with them.
As I've said, extensive image descriptions in the visible part of a post may be okay when the post is about the picture, but not when the picture illustrates the post and even less when there's more than one picture illustrating the post.
Yes, this is a thing. Just read what @Stormgren wrote earlier this month.
Alt-text doesn't just mean accessibility in terms of low -vision or no-vision end users.
Done right also means accessibility for people who might not know much about your image's subject matter either.
This is especially true for technical topic photos. By accurately describing what's in the picture, you give context to non-technical viewers, or newbies, as to exactly what they're looking at, and even describe how it works or why it matters.
#AltText is not just an alternate description to a visual medium, it's an enhancement for everyone if you do it right.
(So I can't find any prior post of mine on this, so if I've actually made this point before, well, you got to hear a version of it again.)
And I'm actually waiting for Mastodon users to refuse to boost posts that contain pictures with insufficient alt-text. Many refuse to boost posts that contain pictures without alt-text already now.
The obvious downside of it is: "DESCRIBE ALL THE THINGS" + lots and lots and lots of stuff in the picture + just about everything needs to be explained because nobody is familiar with any of it = alt-text the size of a rather long blog post.
I've tried that with this picture (no embedding although I could because reasons). I've written a detailed alt-text. I've spent more than three hours in-world in a preserved, static copy of this place, researching and transcribing text where probably none of you would even know that there's text otherwise. The picture alone wasn't enough of a source for an alt-text that I would have deemed sufficient.
Only description plus some transcriptions: 7,636 characters. Description plus everything transcribed, save for the big black panel in the middle background behind the tree which I couldn't transcribe because it no longer exists in-world, plus translations of everything that isn't English plus everything unfamiliar explained: 10,985 characters. If that panel had still existed in-world, and I could have transcribed it, I might have passed the 12,000-character mark. With an image description.
As I've said, Hubzilla doesn't have a hard cap for alt-text length. In theory, it could handle and probably display alt-texts much longer than this. I don't know how it'd display an alt-text of that size in practice, whether it'd be scrollable, whether it'd have a time-out before anyone could read it fully etc. Mastodon, in the meantime, has the hard cap I've mentioned above which probably also cuts alt-texts coming in from outside. That's where most of my audience is. And screen reader users might have no other choice than to sit through their screen readers rambling down alt-text for more than five minutes in one go, especially if they could get a hold of the original alt-text instead of one cropped at the 1,500-character mark.
Now, even though I'll probably kick off two separate threads, I'd like to read your thoughts about how detailed alt-text should be.
Alt-text doesn't just mean accessibility in terms of low -vision or no-vision end users.
Done right also means accessibility for people who might not know much about your image's subject matter either.
This is especially true for technical topic photos. By accurately describing what's in the picture, you give context to non-technical viewers, or newbies, as to exactly what they're looking at, and even describe how it works or why it matters.
#AltText is not just an alternate description to a visual medium, it's an enhancement for everyone if you do it right.
(So I can't find any prior post of mine on this, so if I've actually made this point before, well, you got to hear a version of it again.)
This means she asks for a) a full description and b) a full set of explanations where necessary, especially of technical content.
Besides, there might still be legally blind people who nonetheless want to know everything about everything that's in a picture, too.
I admit I skimmed it at first, because even for sighted people text might be too long. As I mentioned, trimming is a useful thing (and I don’t mean it snarky, even if it may seem that way).
However, I had given it a 2nd look and added an edit. Maybe the edit didn’t federate to Mastodon tho, so here it is:
Also, for uses other than vision impairment, I think text should be elsewhere than alt-text. Like just description text or image metadata. Alt-text is for when you can’t see the picture.
(Like on ye olde internet which you might have browsed with images disabled to speed up loading.)
What's a good, cheap, no external power GPU to buy for VMs? Want to chuck a few in my Dell R730 server to make my desktop VMs more usable. Right now have an old K620 for a Windows VM, seems like 1030s are a good bet since I have a bunch of low profile slots I otherwise have no use for.
@TrenchcoatFullofBats I think this is the winning answer. Looks like it's about a 1060 6GB, which should be enough horsepower for several desktop VMs, and keeps open my full profile slots should I ever want to install something even more powerful in the future. vGPU support is also nice so I don't have to juggle which VM gets which GPU.
Das erste Stück wird sich um die #Zeidlerei im #Spreewald des 18. Jahrhunderts, das andere um den Versuch der (Wieder?) Einführung der Zeidlerei im #ThüringerWald des 16. Jahrhunderts drehen.
Sobald die Periodika gedruckt sind, werde ich natürlich informieren. 📯
Die Druckfahne für die Spreewälder Zeidlerei konnte ich bereits korrigiert zurücksenden. Ich freue mich sehr. Und auch der erste Aufsatzteil zur Thüringer Zeidlerei hat bereits zum Herausgeber gefunden. #Thüringen#Brandenburg
Endlich ist das erste Büchlein da. Auf den Seiten 35 bis 38 des aktuellen #Lübben|er #Heimatkalender|s stelle ich eine kleine Geschichte rund um einen widerrechtlich gefällten Bienenbaum vor und was uns diese über die #Zeidlerei im #Spreewald der Frühen Neuzeut verrät.
Hi, we're a tech startup run by libertarian Silicon Valley tech bros.
We're not a newspaper, we're a content portal.
We're not a taxi service, we're a ride sharing app.
We're not a pay TV service, we're a streaming platform.
We're not a department store, we're an e-commerce marketplace.
We're not a financial services firm, we're crypto.
We're not a space agency, we're a group of visionaries who are totally going to Mars next year.
We're not a copywriting and graphic design agency, we're a large language model generative AI platform.
Oh sure, we compete against those established businesses. We basically provide the same goods and services.
But we're totally not those things. At least from a legal and PR standpoint.
And that means all the laws and regulations that have built up over the decades around those industries don't apply to us.
Things like consumer protections, privacy protections, minimum wage laws, local content requirements, safety regulations, environmental protections... They totally don't apply to us.
Even copyright laws — as long as we're talking about everyone else's intellectual property.
We're going to move fast and break things — and then externalise the costs of the things we break.
We've also raised several billion in VC funding, and we'll sell our products below cost — even give them away for free for a time — until we run our competition out of the market.
Once we have a near monopoly, we'll enshitify the hell out of our service and jack up prices.
You won't believe what you agreed to in our terms of service agreement.
We may also be secretly hoarding your personal information. We know who you are, we know where you work, we know where you live. But you can trust us.
By the time the regulators and the general public catch on to what we're doing, we will have well and truly moved on to our next grift.
By the way, don't forget to check out our latest innovation. It's the Uber of toothpaste!
@ajsadauskas@technology And don’t forget their enablers - the investors who pour in billions of dollars of other people’s money, the marketeers who hype these “disruptive” technologies and the copycats who naively follow them. “Disrupter” used to be a bad word - how that became a badge of honor is another of Silicon Valley’s mysteries. #disruptors#SiliconValley
Annie, are you okay? So, Annie, are you okay? Are you okay, Annie? Annie, are you okay? So, Annie, are you okay? Are you okay, Annie? Annie, are you okay? So, Annie, are you okay? Are you okay, Annie? Annie, are you okay? So, Annie, are you okay? Are you okay, Annie?
@linux_gaming Have a question. Is possible to connect and a bluetooth TV with Linux Mint? bluetoothctl can not be connect to this device and I try difirent ways as possible. I need to extend my screen without HDMI.
I have never heard of streaming a screen over bluetooth and I highly doubt that the bandwidth would be enough for even a few frames per second. Are you sure that your TVs bluetooth is for streaming a screen and not for audio only?