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?

On desktop kbin is 5x better than vanilla lemmy.

But on mobile I have several FLOSS lemmy clients. They all have their pros n cons. Their development is spread out with different projects. Work and the responsibility are distributed from the main lemmy maintainers.

The kbin webapp is pretty good, but not as good as a native client. There is of course only one.

My feeling is that designing for clients (having an API) imposes some kind of discipline on projects. Like you can't just do whatever willy nilly.

My other feeling is that kbin is setting up to be like iCloud whereas lemmy is more akin to sftp.

Thoughts?

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.

One of the extremely useful things about reddit was that content was somewhat organized by URL. Each post was created in a subreddit. So you could do websearch like keyword site:reddit.com/r/subreddit

This is more difficult/impossible on the threadiverse.

I am not sure to what extent it is configurable on either platform, but quickly looking I see URLs like this:

• lemmy: https://lemmyinstance.tld/post/0000000; no community/magazine context is present

• kbin: https://kbininstance.tld/m/magazinename/t/00000/the-title-of-the-post-is-optionally-included

I like the kbin way of doing this because it provides the possibility of searching as with reddit.

Are there any potential solutions to this problem? I haven't even mentioned various other hurdles inherent to the distributed nature of the fediverse content. So feel free to enumerate those.

I'm sure I'm not the only one to want this feature. What is the status of it?

Somebody who was previously active on the kbin codeberg repo has left that to make a fork of kbin called mbin.

repo: https://github.com/MbinOrg/mbin

In the readme it says:

Important: Mbin is focused on what the community wants, pull requests can be merged by any repo member. Discussions take place on Matrix then consensus has to be reached by the community. If approved by the community, no additional reviews are required on the PR. It's built entirely on trust.

As a person who hangs around in repos but isn't a developer that sounds totally insane. Couldn't someone easily slip malicious, or just bad, code in? Like you could just describe one cool feature but make a PR of something totally different. Obviously that could happen to any project at any time but my understanding of "code review" is to at least have some due diligence.

I don't think I would want to use any kind of software with a dev structure like this. Is it a normal way of doing stuff?

Is there something I'm missing that explains how this is not wildly irresponsible?

As for "consensus" every generation must read the classic The Tyranny of Stuctureless. Written about the feminist movement but its wisdom applies to all movements with libertarian (in the positive sense) tendencies. Those who do not are condemned to a life of drama, not liberation.

test

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).

I didn't read it all, but for the curious, looks like the story is here: [Question] Is this project still being actively maintained? · Issue #1139 · ogham/exa

hope everyone involved is OK, on to other projects

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).

I didn't read it all, but for the curious, looks like the story is here: [Question] Is this project still being actively maintained? · Issue #1139 · ogham/exa

hope everyone involved is OK, on to other projects

Secure a place in history. Create the source material for hundreds of journalists, bloggers and shitposters writing about the downfall of reddit and the rise of the threadiverse. (also missing!)

At some point, there will be some sort of drama involving kbin. It could be constructive drama or not; who knows.

When it happens, whatever it is, lots of people will direct themselves to wikipedia to learn about what this website is. We all know wikipedia can be very influential. Even in the absence of drama.