[06:53:45] [1/2] wondering why notifications of my wikis never shows up on other wikis [06:53:46] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1565619704931029023/image.png?ex=6ae59079&is=6ae43ef9&hm=8e4fb324dc4f9ebd3860260af88fdb6a1750816061918ec2264223403f0ab2da& [07:41:56] Just realized that the kartographer map marker issue seems to be fixed, but on my wiki why does it show only half the icon? [07:42:21] E.g. https://mypt.miraheze.org/wiki/Template:Map-pyl [07:42:57] The bottom of the icon is cropped off [08:09:32] -# mini update: i lost all of my yubikeys [08:18:52] has tech considered switching their status site to Instatus [08:19:40] <_arawynn, replying to songngu.xyz> There's a setting you can turn on to get notes from other Wikis [09:12:49] [1/2] https://cdn.discordapp.com/attachments/1006789349498699827/1565654697329561690/image.jpg?ex=6ae5b110&is=6ae45f90&hm=4e54268b8761a5204569871659a29e86606e877ecc7f873ae46607192440a374& [09:12:49] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1565654698315350026/image.jpg?ex=6ae5b110&is=6ae45f90&hm=fca64efa8309428878d0a265e5d2b3e5b786b2845176499407110a47edfe4f32& [10:31:12] instatus is not that good lol [10:31:14] incident.io is way better [10:31:21] iirc I've brought up that idea before [10:57:41] how lol [11:13:48] looks nicer plus it can actually do incident response instead of instatus which is just a status page [12:56:16] Without it enabled then I am not even getting any notifications in the first place 💀 [12:56:45] I am mentioning the CSP error [13:26:04] k [13:27:10] Why [13:28:16] [1/2] instatus allows you to subscribe to notifs via discord [13:28:17] [2/2] im not sure how yall set up the current status page but i think it could be neat if we could be notified of different databases [13:28:28] and thats what instatus is good at imo [13:30:40] Interesting [13:30:45] I’ll take a look maybe today [13:31:06] I have been talking with tech lately on the whole publishing updates on outages thing [13:31:17] I have a WIP idea to help address it but we’ll see [13:32:11] There’s also the other socials [13:50:43] incident.io can do that if you write a script and it looks nicer [13:51:04] plus incident has better on call and alerting functions 🙃 [13:51:53] and it lets you do cool incident write ups on the status page [13:55:58] have you used it before [14:00:48] yes I use it in WO [14:01:05] the status webhook does that [14:02:37] eh i would prefer if it was a built in feature [14:05:12] it’s less consumer focused than instatus [14:05:25] the only good thing about instatus is it’s cheap [14:05:37] but incident io has a good free plan tbh [14:05:44] i mean [14:05:46] at the end of the day [14:05:53] i would prefer if miraheze status page wasnt on atlassian [14:06:04] anything other than that mess [14:06:32] instatus also limit your statuspage subscriptions [14:06:58] incident is less batteries included but if setup well is really good [14:14:45] atlassian statuspage is awful [14:14:56] tbh uptime kuma isn’t bad [14:15:11] same for cachet but I’m less familiar w/ it [14:15:25] if you want to self host those two are the best [14:48:23] you can host your status page on this github pages with this one workflow, tho you would then need a status page for the status page [15:02:10] lmao [20:38:51] https://mrshu.github.io/github-statuses/ here's the statuspage for the status page [20:38:53] but that's on github too [20:38:54] so [20:38:59] status page for the status page for the status page [20:39:01] statuspage ception [20:40:14] We need a bot that creates status pages for the status pages, we will need a status page for that too tho [20:40:28] THE INFINITE LOOP OF STATUS PAGES