density

in summer 2023, when I moved here from reddit, the lemmy instance beehaw.org was extremely divisive. they wanted to create a website according to certain rules rather than a free for all. some people were saying it would be the end of the threadiverse before it even began.

since that time, there have been various other intrinsic and extrinsic threats. I do not see much panicking about beehaw. did the threadiverse survive beehaw? or is this only a shell of what we might have had otherwise?

When I join threadiverse (summer 2023), soon everyone was talking about Threads and how it was about to destroy the whole thing.

Then nothing came of it and the whole convo kinda vanished.

Why didn't threads destroy threadiverse already?

When I Find-in-page for a term using ctrl+f or "find as you type" with "Highlight all" turned on, all results will appear highlighted. But then much of the time several seconds (variable) later it goes away, as though I had hit esc. If I hit ctrl+g for "find again" it starts again at the top. So current place in page is lost.

This happens even if I take my hands away from keyboard/mouse. It is not some kind of input I am doing.

Does this sound framiliar to anyone? Is there a way to make the "find" results stay found?

Or is there an add-on which reliably implements Find?

I have problem on multiple devices, for a long time, and with linux, windows and mac.

hello friends of rblind. I am a sighted person who follows the kbin-core repo. I saw an issue #1143 opened recently regarding the use of alt in markdown. I am having a hard time discerning whether it is a productive request or not.

I understand that rblind is not a free-of-charge accessibility consultation company. But I thought I would point out this issue in case anyone had an interest in contributing to the discussion.

If I am posting in error, please either remove it or notify me so I can remove or edit the post.

Here is the text of the issue:

See this post

Current widespread wisdom is that you should specify alt text with the format ![alt text](url) but this ISN'T behaving as alt text. It's behaving as a label. It needs to be set to the alt text attribute on the image.

True alt text doesn't need to be rendered out. It's a nice feature that apps like pixelfed give you a button to see the alt text, because it can give extra context, but this is a secondary feature. This would be great to add as well, but it's out of scope here.

Labels are meant for things like crediting the photographer. See any well written news articles for examples of this. This one has an image of some sharks as a header. You'll see underneath that it has an explanation and credits NIWA for the image.

There IS a way to specify labels in markdown, and leave the alt text in tact. The correct format is ![alt text](link "label goes here") but this isn't currently recognised by kbin and the label gets completely stripped out. (link)

You can verify this by using something like this plugin.

Notice how all the post images are marked as "Missing alt attribute"

Notice how things like the magazine icon don't render out their alt text "ArtemisAppPlayground Icon"

Further, see codberg's handling of images:

alt text

![alt text](https://upload.wikimedia.org/wikipedia/commons/thumb/6/66/SMPTE_Color_Bars.svg/320px-SMPTE_Color_Bars.svg.png "Label text here")

results in the following html:
<img src="https://upload.wikimedia.org/wikipedia/commons/thumb/6/66/SMPTE_Color_Bars.svg/320px-SMPTE_Color_Bars.svg.png" alt="alt text" title="Label text here">

(codeberg displays labels as tooltips)

I honestly think it's fine to keep using the first [part] as labels, mostly because this syntax is already widely in use, but I think the second (link "this bit") should be set to the image's alt text attribute.

I just learned:

https://github.com/ogham/exa the ls replacement has been replaced by https://github.com/eza-community/eza

the exa repo says:

exa is unmaintained, use the fork eza instead.
(This repository isn’t archived because the only person with the rights to do so is unreachable).

For the curious, looks like the story, contributor deliberations and conversations are here: [Question] Is this project still being actively maintained? · Issue #1139 · ogham/exa

hope everyone involved is OK & on to other projects

both projects are MIT licensed and written in rust.

I can't believe how fast this addon was developed into something that is super useful.

A month ago I made a list of all the available addons to address this need. There were I think 4-5 of them and I actually didn't end up using any of them because they were too simple and didn't add much for my usecase.

In the intervening days (days!) this project has really fleshed out. I am impressed that you've managed to make an interface that makes sense. I wasn't sure if that would be possible because it is kind of an inherently complex situation.

And on top of that, it works. There are issues with federation which are network wide and not much you can do about that. But as much as the threadiverse is willing to cooperate, this addon smooths the experience.

Thanks, I really appreciate this.

Im sure theyre going to find the perfect mods