Man I'm glad Twitter-like sites are federated with lemmy or we wouldn't get to see hashtag-laden tweets like this here
GOG
GOG.com is a DRM-free games and movies distribution service that is part of the CD Projekt Group. GOG.com is also a "sister" company to CD Projekt Red, developers of the Witcher series and Cyberpunk 2077.
Rules:
- No piracy discussion
- No harassment
- For post that is not in English, Please tag the language
the title formatting is fixed in v0.19.0 coming soon
What about the content of the posts? They're usually pretty empty. "just installed the new @KDE release! @linux @linuxdevs" and the like
@glimse Glad to be of service
@glimse (joking aside, I wasn't aware tags would come through this way, I'll be more considerate about this in the future).
(I'll fault lemmy for this though: it reinterprets the HTML as Markdown but then fails at rendering it in the title.)
Yeah rendering is fixed here https://github.com/LemmyNet/lemmy/issues/3828
The update should be releasing soon
It's not your fault - I disagree with the federation in general. Discussion boards (Reddit, Lemmy, etc) aren't the same thing as social media sites (Twitter, Mastodon, etc) and it doesn't make any sense to me to combine them
The vast majority of the posts I see aren't discussions - they're just communities getting tagged.
Works for me if I disable my ad blocker. You can also just use this link directly: https://www.gog.com/giveaway/claim
If you see an empty-looking JSON response, it's claimed. You can also refresh and it should tell you "Already claimed".
@rikudou interesting, I actually have uBlock Origin *disabled* on GOG, and even disabled Privacy Badger to see if this was the issue (and reloaded after it). Despite this I see lots of warnings in console about cookies not having the correct CORS setting, so it might just be an issue with the more recent versions of Firefox being more strict in this regard. That's a good workaround to know until GOG fixes their side, though, thanks.
Huh, weird, I just disabled my AdGuard and the link showed up. Well, glad I could help with the workaround!