Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ @lemmy.dbzer0.com ɐɥO @lemmy.ohaa.xyz 1y ago

Rockstar selling you cracked copies on Steam

Source: https://www.reddit.com/r/Piracy/comments/16afo4x/rockstar_selling_you_cracked_copies_on_steam/

You're viewing a single thread.

99 comments

Source's source: https://twitter.com/_silent/status/1698345924840296801
- The nitter link: https://nitter.net/_silent/status/1698345924840296801
  
  I'll just stick to 🏴‍☠️ old games with DRM, why should I give a company 🤑 for redistributing a cracker's hard work?
  
  You gotta do a workaround [url](url) when the URL breaks like that.
  
  Thank you! Imma fix it right now.
  
  Might wanna fix that
  
  Fix what? Link works fine for me. Sometimes Nitter doesn't load though, hit refresh a few times and you'll get it.
  
  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.
  
  Thank you! Now it’s clickable for me.
  
  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.
  
  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.
  
  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.
  
  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).

99 comments