How? I read the comments and I can't replicate the issue you are experiencing. The original link is causing the problem for me (but I can still access the page).

[-] [email protected] 3 points 10 months ago

Fix what? Link works fine for me. Sometimes Nitter doesn't load though, hit refresh a few times and you'll get it.

[-] [email protected] 10 points 10 months ago

Because it's a bare link, some apps interpret the underscore as the end of the link.

[-] [email protected] 1 points 10 months ago

Ah right I see. Surely that's the app developer's responsibility to fix?

[-] [email protected] 4 points 10 months ago* (last edited 10 months ago)

"I see a problem I can easily fix but obviously it's someone else's problem."

Here's the full link.

https://nitter.net/__silent_/status/1698345924840296801

Edit: to lemmy users, this link looks no different. To third party app users and Kbin users, etc, the previous links all cut out after the first underscore.

[-] [email protected] 2 points 10 months ago

Thank you! Now it’s clickable for me.

[-] [email protected] 1 points 10 months ago

I mean sure, but that's a bit more involved than just pasting a link with no code and having the renderer make a link, which lemmy is supposed to do. The app is failing to meet the lemmy spec, the developer should fix that.

[-] [email protected] 3 points 10 months ago

So, it's actually more a Lemmy bug. Lemmy stores the comments just fine but the API displays it with markdown. The double underscore is screwing up other apps abilities to display it and there's really no way to avoid that. A third party app can't tell if it's supposed to be interpreted or not.

So on Lemmy, all the URLs look fine. On Kbin or any other apps, they'll all get cut off after the first underscore.

[-] [email protected] 0 points 10 months ago* (last edited 10 months ago)

and there’s really no way to avoid that.

Yes there is, the way lemmy avoids it. _ might be usable as a tag in mark down, but it shouldn't be used to break out of a URL.

~~This is definitely a kbin bug lol.~~ Edit: not kbin, but whichever app people are browsing with. Both lemmy and kbin websites work.

[-] [email protected] 0 points 10 months ago

Lemmy avoids it by having the source content and then translating output to markdown. Any third party reader needs to sanitize that output.

Lemmy basically does not output safe content for third parties. It's absolutely a Lemmy bug from any developer's perspective.

[-] [email protected] 0 points 10 months ago

I've just checked on kbin and the link works just fine. Kbin doesn't display the full link, but when you click it on the website it works.

Are you using an app to browse kbin? In that case it's your app that's not doing it correctly. Possibly kbin doesn't give it the infomration, or maybe it just reads the text of the link and misuses that.

Either way, the problem is nothing to do with lemmy. However lemmy apps have their own little bugs to work out (eg instance agnostic links from v0.18) so we're all in the same boat of fedeverse development.

[-] [email protected] 0 points 10 months ago* (last edited 10 months ago)

The link works for me. I was helping other folks who may have an issue with bare links as pointed out by the other commenter.

Either way, Lemmy is the reason non-lemmy readers can't actually properly parse the information. The information is not what's stored in the database. Only Lemmy can display it properly since it wraps it up in a bunch of markup that is then provided to third parties. As a developer, I don't know what reasoning you still think you have to believe it's not Lemmy. Everything you've said so far does nothing to backup that point.

Edit: also, I'm done here. I'm not interested in convincing a non-developer their favorite platform isn't perfect.

[-] [email protected] 1 points 10 months ago* (last edited 10 months ago)

Edit: to lemmy users, this link looks no different. To third party app users and Kbin users, etc, the previous links all cut out after the first underscore.

The link works for me.

So which is it? Did it work or not?

When I checked, it worked. Before the link was edited, when it was just a raw url with no markdown code. Lemmy dispayed the full link with the underscores. Kbin displayed a shortened version, but it linked to the same url.

You're being incredibly pretentious with this "I'm a developer" nonsense. A developer of what? Be specific. Which app did you actually see the problem in?

Either way, you've been the one trying to push the blame on lemmy and users, right from the start. I'm not really sure what you're playing at here, but it seems like you've realised your mistake and are now trying to save face.

The issue is with your app. Both lemmy and kbin desktop websites parsed the url correctly.

Here it is again for testing: https://nitter.net/__silent_/status/1698345924840296801

Edit: Works fine on lemmy and kbin websites, doesn't work in Jerboa. So it's yet another problem with Jerboa (or whichever app) text processing, nothing to do with lemmy and certainly not the user's fault.

“I see a problem I can easily fix but obviously it’s someone else’s problem.”

Incredibly pretentious. Sort yourself out mate.

[-] [email protected] -2 points 10 months ago

Before the link was edited, when it was just a raw url with no markdown code.

It's always with markdown. Lemmy is the only web app that can access it without markdown. I explained it like four different ways now. If you don't understand it by now, you never will.

It worked for me and it's why I provided a full link. Since it was created on Kbin, it was escaped by Lemmy as well. So lemmy will display the app just like Kbin would. But anyone who creates a link on lemmy, it will always look wrong in every other web app or third party app. It's simply not possible for a third party app to display a link properly that was created by a lemmy user. Same goes for code boxes. They can only be displayed properly by Lemmy and no one else. It's not possible for third party apps to display them properly.

Lemmy is the only one that can display links and code boxes created by Lemmy users. Links and code boxes created by every other platform displays properly everywhere.

You're literally hand waving it away because it still works even though it's impossible to parse by any other app. Just because it is only aesthetic doesn't mean it's a bug. The bug affects jerboa more than Kbin. I still helped those users instead of your pretentious ass by saying "oh well, not my problem."

When there's a problem that only exists with lemmy, it's lemmy.

Do you need me to explain it yet another way? Do you need an ELI5?

You're the pretentious one speaking from some authority without having any clue what the fuck you're talking about.

I'm done. You're blocked so I won't be angered by any stupid replies from you.

[-] [email protected] 1 points 10 months ago* (last edited 10 months ago)

Same goes for code boxes. They can only be displayed properly by Lemmy and no one else. It’s not possible for third party apps to display them properly.

Except Jerboa displays code tags just fine. There's also the view source function.

There are ways to solve the problem, they just haven't been implemented yet. That's up to app developers.

I’m done. You’re blocked so I won’t be angered by any stupid replies from you.

Shock horror. Something tells me they don't need me to get angered.

Edit: So, thinking on it some more for the benefit of anyone else, it would be perfectly possible to fix in Jerboa for lemmy. Jerboa just breaks out of the link but still shows the full url, only the rest of it is text and the bit in between two removed _ is italicised. Jerboa is failing to inhibit for the link and applying markdown to it.

Maybe on kbin apps it can't work, because kbin shortens the link in text and doesn't have a view source function. But kbin is not lemmy.