691
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 Sep 2023
691 points (97.8% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54609 readers
626 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
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.
Incredibly pretentious. Sort yourself out mate.
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.
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.
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 identify 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.