this post was submitted on 27 Mar 2025
4 points (100.0% liked)

Mbin Meta

0 readers
1 users here now

An "official" way of giving suggestions, feedback or questions about mbin.

Related

This is a replacement of !Mdev@kbin.run since kbin.run is no more

Rules

founded 7 months ago
MODERATORS
BentiGorlich@gehirneimer.de
4
Community links lead to /m/ when federated with Lemmy (kbin.earth)
submitted 2 weeks ago by aasatru@kbin.earth to c/mbinmeta@gehirneimer.de
9 comments fedilink hide all child comments
 

This is probably old news, but I didn't realize before now - if I link to !mbinmeta@gehirneimer.de, Lemmy users will see it as a link to lemmy.example/m/mbinmeta@gehirneimer.de.

Is this something that could potentially be resolved at some point? I get that it's a bit of a legacy problem from the questionable decision not to follow Lemmy URL structures.

I guess it could always be fixed on the Lemmy side, but is a fix on the Mbin side of things possible? Since community links from Lemmy work well on Mbin, can't Mbin links just be federated in the exact same way?

Edit: I observed this in this thread: https://kbin.earth/m/seattle@lemmy.world/t/1109670 https://discuss.tchncs.de/post/33165045

Apparently it federates well in this thread. Might be related to where the community is hosted?

It could also be that it happens when linking communities that the Lemmy instance hosting the community has not yet federated with.

you are viewing a single comment's thread
view the rest of the comments
[–] squirrel@discuss.tchncs.de 1 points 2 weeks ago (1 children)

I'm seeing https://discuss.tchncs.de/c/mbinmeta@gehirneimer.de from Lemmy and it links the community correctly.

[–] aasatru@kbin.earth 1 points 2 weeks ago (1 children)

Thank you! I have specified more, as apparently the problem is less general than I thought. Which makes sense, I was wondering how it had not been picked up earlier.

I found the problem in this post: https://discuss.tchncs.de/post/33165045

[–] squirrel@discuss.tchncs.de 2 points 2 weeks ago (1 children)

There is some very broken markdown in that post:

Cross-posted from [!washington](/m/Washington@50501.chat) ([`[!washington@50501.chat](/c/washington@50501.chat)`](/c/washington@50501.chat))

Would be interesting which client produced this code. The link format is completely broken.

[–] aasatru@kbin.earth 1 points 2 weeks ago (1 children)

The weird [!washington@50501.chat](/c/washington@50501.chat) link was my attempt to offer a transparent alternative for Lemmy users. The rest is presumably done on the mbin side.

Here's my input:

Cross-posted from [!washington@50501.chat](/c/washington@50501.chat) ([`[!washington@50501.chat](/c/washington@50501.chat)`](/c/washington@50501.chat)), for those who might be interested but who don't follow that community (yet). :)
[–] squirrel@discuss.tchncs.de 3 points 2 weeks ago (1 children)

I've discovered if you don't use markdown at all and just write [!washington@50501.chat](/c/washington@50501.chat) it works best in most clients.

Does this work across platforms?
!washington@50501.chat

[–] aasatru@kbin.earth 2 points 2 weeks ago

Your link works great here, on Mbin.

On the first version of my post I only wrote [!washington@50501.chat](/c/washington@50501.chat) - as you'll see, there's no markdown in the first link coming from my side. The problem here seems to be that Mbin for some reason translates [!washington@50501.chat](/c/washington@50501.chat) into [!washington](/m/Washington@50501.chat) automatically.

I'm not sure exactly why, as it does not seem to be the normal behaviour.