Hey @newpipe
hope you are well. Just wondering, of you habe a tip for me. I'm following a the Channel with some live stream content. On YT it's Lister under the Tab "live" and not in the main video list.
In #Newpipe it's not listed inmy subscription either. I need to specifically search for it, to find it.
Is there a way, to see is in my subscriptions and within the channels video list.
No. There’s an older development version of NewPipe from when they were experimenting with including the YT tabs (live, shorts etc) but that never got included in the final release for some reason. And meanwhile all the YT changes broke playback on these older versions.
I've been wondering about this for a while, but couldn't find anything about it. What exactly happens after the screen turns off? Does the kernel actually suspend and halt the CPU? If so, how are notifications received while sleeping? Is there a coprocessor involved?
I'm curious. It would be great if someone could point me towards some articles or videos about this.
Amateur here, can only convey what I remember from reading. In sleep mode the the cpu wakes up regularly to do things that are needed for background services and connectivity.
Now, “regularly” may still mean hundreds of times a second between milliseconds of sleep. These wake cycles are also synchronised with other parts of the system, especially networking.
Similarly, cpu will sleep even if the phone is awake but not very active, but will wake more frequently.
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.
Then that’s probably the answer you’re looking for. Who else is gonna give you a better answer?
I also think that makes quite sense. People with regular vision can just glance at a picture for half a second to get the idea of it, and move on. Having to spend a minute on every illustrative pic, no matter how unimportant, sounds more annoying than missing out on an extra layer of information. (Most of the time.)
I used to be a journalist and I’ve learned you can trim a helluva lot of information without really losing much. It’s a generally useful skill since time is limited for all of us.
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.)