[07:49:43] <MirahezeRelay>	 <honoka55> i figured out what causes the problem mentioned in this task. i just wonder if it's possible to fix this given our mw-config architecture? https://issue-tracker.miraheze.org/T14461#323891
[08:12:35] <MirahezeRelay>	 <posix_memalign, replying to honoka55> [1/3] Likely requires a ManageWiki patch as said in my comment.
[08:12:35] <MirahezeRelay>	 <posix_memalign, replying to honoka55> [2/3] Maybe we can give you beta access so that you can test your changes because ManageWiki is really hard to set up locally. To give someone beta access is a lot of work on both your side and ours, though, so I'm not sure if this is a desirable route. I think with the amount of work you are doing it'll definitely make things easier if you can test changes on 
[08:12:35] <MirahezeRelay>	 <posix_memalign, replying to honoka55> [3/3] beta for future PRs.
[08:14:54] <MirahezeRelay>	 <honoka55> oh does that need an nda?
[08:17:56] <MirahezeRelay>	 <posix_memalign, replying to honoka55> Yeah that's the main thing. NDA + data privacy training because beta also contains PII from users, and it is not perfectly separated from production.
[08:18:38] <MirahezeRelay>	 <honoka55> i guess so. yes it is a lot of work i think i may just make a pr on github for test
[12:04:36] <MirahezeRelay>	 <bluemoon0332> well I already hate MobileFrontend and it's been just an hour
[12:06:37] <MirahezeRelay>	 <bluemoon0332> I don't use that, so I didn't what these "amc" strings in the config of Minerva stood for, turns out it has some kind of "advanced" mode that's supposed to basically show more buttons, so know I wonder how I want to do [[phorge:T15782]] :ThinkingHardMH:
[12:06:38] <MirahezeRelay>	 <Wiki-Bot#2998> <https://issue-tracker.miraheze.org/T15782>
[12:07:12] <MirahezeRelay>	 <bluemoon0332> this is why I don't do UI work at work for the most part, I love my backend, keep the frontend as far away from me as possible
[12:07:44] <MirahezeRelay>	 <swuzzo, replying to bluemoon0332> why
[12:08:26] <MirahezeRelay>	 <bluemoon0332> I hate UI work mostly because you have to account for all these different devices, input methods, screen sizes, you are basically making multiple interfaces in one
[12:08:55] <MirahezeRelay>	 <swuzzo> input methods?
[12:09:06] <MirahezeRelay>	 <bluemoon0332> while the backend doesn't have this problem, all the servers are running the same software, with the same build options, speak the same language so to speak
[12:09:10] <MirahezeRelay>	 <jenny_on_wiki> I find web ui just about possible enough but I'm never making a custom gui
[12:09:37] <MirahezeRelay>	 <bluemoon0332, replying to swuzzo> how you interact with a website, for example that can be a mouse, a keyboard, a touch screen, long etc
[12:09:46] <MirahezeRelay>	 <swuzzo, replying to jenny_on_wiki> What's a custom gui
[12:09:48] <MirahezeRelay>	 <swuzzo, replying to bluemoon0332> Ohhh
[12:09:55] <MirahezeRelay>	 <jenny_on_wiki> a gui that's custom
[12:10:04] <MirahezeRelay>	 <swuzzo> Is Discord a custom gui
[12:10:07] <MirahezeRelay>	 <swuzzo, replying to swuzzo> ?
[12:16:21] <MirahezeRelay>	 <bluemoon0332> well seems we handle this in ManageWikiSettings with good old list-multi-bool, so at least I know what to do now
[12:40:13] <MirahezeRelay>	 <sakurababochka, replying to swuzzo> A GUI is a Graphical User Interface. So anything you can see and interact with on a device (oversimplification, but still).
[12:41:58] <MirahezeRelay>	 <sakurababochka> Custom I'm less sure on, but I believe it's if your gui isn't a modified version of a different one?
[13:28:59] <MirahezeRelay>	 <elisapoly> [1/2] https://issue-tracker.miraheze.org/T16251
[13:28:59] <MirahezeRelay>	 <elisapoly> [2/2] this might be bad
[13:42:27] <MirahezeRelay>	 <person0192837465, replying to sakurababochka> [1/3] There are two main possibilities I would think of for a custom UI:
[13:42:28] <MirahezeRelay>	 <person0192837465, replying to sakurababochka> [2/3] 1) no frameworks
[13:42:28] <MirahezeRelay>	 <person0192837465, replying to sakurababochka> [3/3] 2) a UI already exists but you build a new one
[15:49:48] <MirahezeRelay>	 <unai> templeos
[15:50:23] <MirahezeRelay>	 <person0192837465> I knew I should've added "in regards to websites"
[17:14:59] <MirahezeRelay>	 <zipppee, replying to elisapoly> db182 runs nothing interesting iirc
[17:15:40] <MirahezeRelay>	 <zipppee> matomo is an oh well
[17:15:53] <MirahezeRelay>	 <zipppee> I don't see it as critical to the functioning of mh
[17:16:01] <MirahezeRelay>	 <zipppee> phorge files is probably more important
[17:29:48] <MirahezeRelay>	 <originalauthority, replying to bluemoon0332> backend developers 🔛🔝
[23:39:46] <MirahezeRelay>	 <raidarr> I think I made the blogs explode at https://loathsomecharacters.miraheze.org/ and somehow made them all cease to exist by trying to manually create a blog space which I suppose was a bad idea and conflicted with the BlogPage extension
[23:40:10] <MirahezeRelay>	 <raidarr> naive me thought making a namespace with visualeditor enabled would enable visualeditor and not cease every blog from existing
[23:40:59] <MirahezeRelay>	 <raidarr> so either removing it made the blogs visually explode in which case wtf or it made them all literally blip out of existence in which case wtf and I think I did a data loss
[23:46:11] <MirahezeRelay>	 <raidarr> separately I wonder if it is even possible to compel BlogPage to use visual editor; I thought surely that must be possible but I'm beginning to think no its not
[23:47:52] <MirahezeRelay>	 <raidarr> so that is interesting, making a blog namespace will make all blogs cease to appear to exist, and when it is removed there they are
[23:48:03] <MirahezeRelay>	 <raidarr> meanwhile still evidently no way to get visualeditor to play nice