[00:00:55] <MirahezeRelay>	 <notaracham, replying to bb010g> [1/2] Info on specifically impacted extensions/features is here:
[00:00:55] <MirahezeRelay>	 <notaracham, replying to bb010g> [2/2] https://discord.com/channels/407504499280707585/407504500136607745/1399059949262340207
[00:00:55] <MirahezeRelay>	 <bb010g, replying to pskyechology> yeah. for example, Discord. as opposed to an asynchronous communication method like email or tickets where real-time responses aren't expected by the parties involved
[00:01:28] <MirahezeRelay>	 <pskyechology> oh so a weird way to say you wanted to ask us lol
[00:01:29] <MirahezeRelay>	 <notaracham> Oh, I mean, yes, we do offer some support via #general and #support , though complicated tech stuff still requires tickets
[00:02:18] <MirahezeRelay>	 <notaracham> er, [[phorge]]
[00:02:18] <MirahezeRelay>	 <Wiki-Bot#2998> <https://meta.miraheze.org/wiki/Phorge>
[00:02:32] <MirahezeRelay>	 <bb010g, replying to notaracham> note, categories on [[mw:Extension:SocialProfile]] need to be updated
[00:02:32] <MirahezeRelay>	 <Wiki-Bot#2998> <https://www.mediawiki.org/wiki/Extension:SocialProfile>
[00:03:06] <MirahezeRelay>	 <pskyechology> we do still offer socialprofile, it's just missing that feature
[00:03:19] <MirahezeRelay>	 <bb010g> oh derp
[00:03:54] <MirahezeRelay>	 <bb010g, replying to pskyechology> yeah vs. asking in a ticket later after i had done more prep work
[00:04:25] <MirahezeRelay>	 <pskyechology> completely fair
[00:10:06] <MirahezeRelay>	 <pixldev, replying to pskyechology> Unfortunately
[00:29:54] <MirahezeRelay>	 <thewwrnerdguy, replying to pixldev> this typo is funny to me
[00:30:39] <MirahezeRelay>	 <pixldev> i mean
[00:30:41] <MirahezeRelay>	 <pixldev> true
[00:31:20] <MirahezeRelay>	 <pskyechology> we love our transcosmics
[00:46:30] <MirahezeRelay>	 <ieph> [1/3] Hi there.
[00:46:30] <MirahezeRelay>	 <ieph> [2/3] Um. Is there a problem displaying Wikimedia images on Miraheze, because I'm checking my articles only to find out that they have these displays telling me that it doesn't exist on my wiki.
[00:46:31] <MirahezeRelay>	 <ieph> [3/3] https://cdn.discordapp.com/attachments/407537962553966603/1469856885258715229/image.png?ex=69892e66&is=6987dce6&hm=304dff4a9aa3b5de7d2cd5695bd5b6d057780d2d9b12be0717f5bf8021175680&
[00:46:42] <MirahezeRelay>	 <ieph> [1/2] or they're just not showing at all.
[00:46:42] <MirahezeRelay>	 <ieph> [2/2] https://cdn.discordapp.com/attachments/407537962553966603/1469856935099760680/image.png?ex=69892e71&is=6987dcf1&hm=ac3325c5086b0ea28ad2a8dd8187538038d893fca3c9f981b656ec832db2ef46&
[00:47:02] <MirahezeRelay>	 <ucronista_> Tech is aware of the problem 🙁
[00:47:37] <MirahezeRelay>	 <ieph, replying to ucronista_> so I don't have to do anything, right?
[00:48:13] <MirahezeRelay>	 <ieph> just wait for the problem to pass?
[00:48:25] <MirahezeRelay>	 <ieph> What even is that problem anyway @ucronista_
[00:56:31] <MirahezeRelay>	 <ucronista_> I think they mentioned it, but I can't find the comment. This task is related to the problem.  There is a connection failure between Miraheze and Wikimedia. From what I understand, it seems to be on their end.  https://issue-tracker.miraheze.org/T14793
[00:57:30] <MirahezeRelay>	 <ucronista_> And it seems that they are conducting tests because I saw that they removed something related to QuickInstantCommons.
[00:58:14] <MirahezeRelay>	 <notaracham> Yep.  I'll leave it to tech to go into details, but it's suspected there's some fault in QuickInstantCommons that's been behind the redlinked images
[00:58:35] <MirahezeRelay>	 <notaracham> CA's been working behind the scenes to try to remove that dependency, but yeah, things are very redlinky right now
[00:59:01] <MirahezeRelay>	 <cosmicalpha> Yeah I apologize for that. We are still looking into this.
[02:04:51] <MirahezeRelay>	 <mr.shirokuma> I see.