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.
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.
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.
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.
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.
Because it’s a bare link, some apps interpret the underscore as the end of the link.
Ah right I see. Surely that’s the app developer’s responsibility to fix?
“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.
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.
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.
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.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.
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.
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.
Thank you! Now it’s clickable for me.