[Issue] Another domain with issues when subscribing: @lemm.ee. Also redirects to a 50x error page and subscribing still works for the account despite the error.
[Issue] Subscribing to magazines from the @readit.buzz domain makes the page redirect to the 50x error page. Despite the error, subscribing still turns out successful.
I see. Is this issue being actively fixed right now? Don’t mean to be pushy. Just want to know how soon it would be fixed. I really want to use kbin lol. Other alternatives for my use case involve having parallel mastodon and lemmy clients (which would be really weird), or Friendica (which unfortunately does not seem to work that well with lemmy).
I doubt it. They've had more important stuff to work on and probably forgot about that issue in the meanwhile. That said, best would be to just comment on it asking what's up with it. That'll bump it up in visibility.
Maybe I spoke too soon…anyone have any idea why I have gotten 3 notifications for comments in this post, but when I view the post it shows no comments?
@ernest might it be an idea to set up a "kbin social status" web page or mastodon account - divorced from the kbin.social server infrastructure - which people could follow and be informed of any site issues which might not be publishable when the kbin.social site itself is down?
So, slight correction to my previous post (which I now deleted) thanks to @troplin.
It seems that phrasing content like <span> elements are allowed inside <pre> elements according to the spec, so Lemmy is actually doing the right thing there. It's on kbin to fix this, not Lemmy.
I commented on one of the closed issues about this on the kbin code repository, asking for the issue to be reopened. Hopefully it will so this gets fixed, I'm not sure though how visibility works if the issue is already closed. I'll make a new one if it's neither reopened nor replied to until next week, if no one else does first.
The issue here is that Lemmy is federating out it's content with the pre blocks containing rendered code fit for some sort of code display plugin/CSS - which KBin doesn't have.
It would ideally send out the blocks html encoded and would let downstream implementations like KBin or others figure out how to display it themselves. I don't know how we would fix this.
I think Lemmy is correct here and the Mozilla docs only refer to the text content, not elements. It also mentions that < and > still have to be escaped to be displayed.
kbinMeta
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.