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?

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.

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.

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.

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.

I am not sure what is correct to put in kbin-core/issues without cluttering it up with somewhat speculative requests. I have no idea how to implement this or whether it is possible. So I will post here?

This is a response to issue
#635 - Editor support for autocompletion when a user types /m/, /c/, /u/, or @

@garrettw said:

After all of this I'm left with the distinct impression that a standardized link format is needed across the fediverse for any fediverse content.

I keep wishing for UUIDs or hashes or an internal link shortener or permalink something.

These are the same post on different instances:

• https://fedia.io/m/firefox/t/132144 <- this is the instance where the community lives
• https://lebowski.social/post/12337 <- this is the poster's home instance
• https://kbin.social/m/firefox@fedia.io/t/237162
• https://beehaw.org/post/6759290

It would be nice if it would have a unique ID like e3d14d6c-28d7-11ee-be56-0242ac120002 across the *verse. I can't be the first person to think of this right? Why is ity either not a good idea, or not a viable idea?

I imagine 2 variations. I am not attached to any of the particulars... Just spitballing. What do you think?

1. /local/uuid

/local/e3d14d6c-28d7-11ee-be56-0242ac120002 - this link would bring the user to the post on the instance where you are viewing it.

So if someone writes in a comment:

check out [this post](/local/e3d14d6c-28d7-11ee-be56-0242ac120002)!

and you are viewing it on beehaw, it renders like this:

<p>check out <a href="https://beehaw.org/post/6759290">this post</a>!</p>

if you are viewing it on kbin.social, it renders like this:

<p>check out <a href="https://kbin.social/m/firefox@fedia.io/t/237162">this post</a>!</p>

2. /orig/uuid

On the other hand we need a way to link to the particular item as it appears "originally". To do this, you could write:

check out [this post](/orig/e3d14d6c-28d7-11ee-be56-0242ac120002)!

And irrespective of where you are looking at it, it will render like this:

<p>check out <a href="https://fedia.io/m/firefox/t/132144">this post</a>!</p>

I am not 100% sure if the correct behaviour for this is to link to the community home instance or the poster's home instance? I went with community home but maybe there is argument for the other way, or for both.

Im sure theyre going to find the perfect mods

I would like to suggest that developers consider as much flexibility when trying to interact with links/handles from off-instance and off-kbin (e.g. lemmy) as possible. I would like for it to work on lemmy in a similar fashion.

I think that the various "incorrect" ways of doing things should work as redirects assuming this would not cause a technical problem. It could even explain the correct way of doing things if you'd like to discourage it.

Non exhaustive examples:

communities

as an example: https://lemmy.ca/c/wowthislemmyexists

search kbin.social for https://lemmy.ca/c/wowthislemmyexists - finds occasions where people have mentioned the URL in comment/post

Most lemmy instances suggest searching for a group in a way that doesn't work:

search kbin.social for
for [!wowthislemmyexists@lemmy.ca](/c/wowthislemmyexists@lemmy.ca) - finds occasions where people have mentioned the handle in comment/post

you need to replace ! with @ to find it:

search kbin.social for
for @wowthislemmyexists@lemmy.ca - works as expected

So the kbin.social URL is https://kbin.social/m/wowthislemmyexists@lemmy.ca

But what about variations a person could try based on principals of how things work e
lsewhere:

https://kbin.social/m/@wowthislemmyexists@lemmy.ca

[https://kbin.social/m/!wowthislemmyexists@lemmy.ca](https://kbin.social/m/[!wowthislemmyexists@lemmy.ca](/c/wowthislemmyexists@lemmy.ca))

even allowing use of the /c/ instead of the /m/?

profiles

profiles have similar inconsistencies.

I can view this off-instance profile on kbin.social: https://kbin.social/u/@btschumy@mas.to

but if I try to drop my own username into the same structure, it doesn't work: https://kbin.social/u/@density@kbin.social

The only way to see my profile is (I think) https://kbin.social/u/density

Hope this all is intelligible.

/r/Firefox and /r/FirefoxCSS have both moved to fedia.io kbin instance.

from kbin.social I can access Firefox. But I can't access FirefoxCSS. I waited about 90 mins since first trying. Should I just wait longer or is there some other issue?

@Firefox@fedia.io
fedia link: https://fedia.io/m/Firefox
from kbin.social: https://kbin.social/m/Firefox@fedia.io
search on kbin.social: https://kbin.social/search?q=Firefox%40fedia.io

@FirefoxCSS@fedia.io
fedia link: https://fedia.io/m/FirefoxCSS
kbin.social: https://kbin.social/m/FirefoxCSS@fedia.io "404 Not found"
search on kbin.social: https://kbin.social/search?q=FirefoxCSS%40fedia.io "Empty"

If you ever have the problem of forgetting you were writing something and closing a window, or accidentally navigating away from the page on which you are composing, this is the browser extension to save your ass: Form History Control.

• Documentation: Form History Control (II)

• Git repo: stephanmahieu/formhistorycontrol-2

• Firefox Addon

• Chrome Web Store

In kbin I especially have this problem as I get logged out constantly for some reason, for example while I am composing even a fairly short comment, and if I submit while logged out the text vanishes. But everything is stored in the extension. It is local to your machine where it will be secure.

I am using it for a year or two now and it has been flawless. It doesn't cause any slowdown in browser performance. It is unnoticeable until that moment you need it.