[00:12:35] <MirahezeRelay>	 <groupnebula563_0765> https://youtu.be/4Cbd-upm3Z0?si=VtoBcoFoAbtsED0w
[00:12:37] <MirahezeRelay>	 <groupnebula563_0765> fops
[02:14:16] <MirahezeRelay>	 <aeywoo, replying to max20091> Well, Aracham has a pixel so they'll be fine.
[04:22:07] <MirahezeRelay>	 <pixldev, replying to aeywoo> wut
[04:26:58] <MirahezeRelay>	 <aeywoo, replying to pixldev> Google Pixel Phone.
[04:29:01] <MirahezeRelay>	 <aeywoo, replying to pixldev> > NotAracham: Just me out here with my pixel phones
[04:38:35] <MirahezeRelay>	 <pixldev> ah
[04:38:54] <MirahezeRelay>	 <pixldev> thought someone called my name /j
[04:47:49] <MirahezeRelay>	 <aeywoo> :/
[07:01:34] <MirahezeRelay>	 <posix_memalign> [1/2] I'm surprised that no one talked about cppreference here. Just learned that they started maintenance in March to make upgrades from MW 1.21. It was planned to be done in a few weeks, but the maintainer (Nate Kohl) has been busy and the update is still not done, so the site is stuck in readonly mode (in fact, I think they used some tricks to replace MediaWiki with static web pa
[07:01:34] <MirahezeRelay>	 <posix_memalign> [2/2] ges, so only some pages are available right now).
[07:02:09] <BlankEclair>	 wtf it was on mw 1.21?
[07:02:57] <MirahezeRelay>	 <posix_memalign> There was a funny incident where someone vandalized the main page with rust, so from that point onward new user registration was disabled for a few months. Probably an overractoin from people without much experience since they didn't have edit protection or abusefilter.
[07:02:59] <MirahezeRelay>	 <posix_memalign, replying to BlankEclair> https://web.archive.org/web/20250123101945/https://en.cppreference.com/w/Special:Version
[07:03:20] <MirahezeRelay>	 <posix_memalign> Yep. One of the best (if not the best) C++ online reference has been stuck from MW 1.21 for many years.
[07:03:23] <MirahezeRelay>	 <blankeclair, replying to posix_memalign> wow
[07:04:51] <MirahezeRelay>	 <blankeclair> trauma sucks :D
[07:07:13] <MirahezeRelay>	 <posix_memalign> I'd love to see them come to MH, though they have so many quirks that it probably won't end up working.
[07:08:25] <MirahezeRelay>	 <theoneandonlylegroom> [1/2] what kind of quirks on mw 1.21 won't work on 1.4X w/
[07:08:26] <MirahezeRelay>	 <theoneandonlylegroom> [2/2] plenty of new extensions
[07:11:03] <MirahezeRelay>	 <posix_memalign> They use `/w` for articles and `/mwiki` for api, which wouldn't work on MH. The biggest problem, though, is that old wikis like it tend to accumulate several custom extensions that are no longer maintained.
[07:11:54] <MirahezeRelay>	 <posix_memalign> For example, there's https://github.com/p12tic/AddBodyClass
[07:12:07] <MirahezeRelay>	 <posix_memalign> No commits for 9 years.
[07:12:40] <MirahezeRelay>	 <posix_memalign> There are also LiveCodeLink and MetaNoIndexTag, which were made by the site's maintainer and would require lots of work to be compatible with the newest version of MediaWiki.
[07:13:49] <MirahezeRelay>	 <blankeclair> [1/2] i love how this is marked as pre-fail
[07:13:49] <MirahezeRelay>	 <blankeclair> [2/2] https://cdn.discordapp.com/attachments/615786602454581249/1391316188474118176/1751786028403.png?ex=686b73ac&is=686a222c&hm=fb4a1a060feab6ba79d01ae1a5c363d828e7b9066739b63b8f49745ca95b0e7a&
[07:14:30] <MirahezeRelay>	 <posix_memalign> It either has already failed or will fail at some point in the future.
[07:14:49] <MirahezeRelay>	 <blankeclair> isn't the read error rate 0?
[07:17:45] <MirahezeRelay>	 <posix_memalign> I was commenting on the wording "pre-fail". I thought you meant to say that using the word "fail" even though there are no signs of failure is odd.
[07:18:00] <MirahezeRelay>	 <blankeclair> ah
[07:18:18] <MirahezeRelay>	 <blankeclair> yeah, according to random internet blog, old-age is just wear and tear, and pre-fail means failure imminent
[07:24:03] <MirahezeRelay>	 <posix_memalign> It'll mostly depend on the number of write cycles though? If it is close to the limit, then failure is imminent, otherwise the chance should be pretty low.
[07:30:10] <BlankEclair>	 i suppose :p
[07:30:20] <BlankEclair>	 0 being "this is about to fail" is still odd to me though
[08:29:44] <RhinosF1>	 BlankEclair: yup
[08:30:43] <MirahezeRelay>	 <posix_memalign> I can see why Matomo needs to hide analytics by default. For very small wikis, some of these stats can easily leak information about the few people who are active on there.
[10:12:30] <MirahezeRelay>	 <groupnebula563_0765> https://youtu.be/xDGrksJgz-M?si=SmLnZALampHh5ZUX
[10:12:32] <MirahezeRelay>	 <groupnebula563_0765> new this
[10:16:16] <MirahezeRelay>	 <theoneandonlylegroom> is that candyman
[17:06:29] <MirahezeRelay>	 <posix_memalign> [1/2] Autocomplete for Lua in MW 1.44? Did not expect that to ever happen.
[17:06:29] <MirahezeRelay>	 <posix_memalign> [2/2] https://cdn.discordapp.com/attachments/615786602454581249/1391465338222284852/image.png?ex=686bfe94&is=686aad14&hm=b2587a1039aced4f92eb1a90af457f713811b9a7db683294e470e8f2b037ea86&
[17:07:15] <MirahezeRelay>	 <abaddriverlol> There's also autocomplete for other languages like wikitext, e.g. for magic words
[17:22:46] <MirahezeRelay>	 <posix_memalign, replying to abaddriverlol> I couldn't trigger this behavior. May need to turn something on?
[17:33:17] <MirahezeRelay>	 <abaddriverlol, replying to posix_memalign> [1/3] You need to have CodeMirror enabled, then it should work
[17:33:18] <MirahezeRelay>	 <abaddriverlol, replying to posix_memalign> [2/3] https://cdn.discordapp.com/attachments/615786602454581249/1391472084453949480/image.png?ex=686c04dd&is=686ab35d&hm=7d3289aeeca63e8098231c24ce8e19a43c9aa39e45bf499a388340ae741b4070&
[17:33:18] <MirahezeRelay>	 <abaddriverlol, replying to posix_memalign> [3/3] https://cdn.discordapp.com/attachments/615786602454581249/1391472084693028984/image.png?ex=686c04dd&is=686ab35d&hm=c3c1c58cfba923ff5695f21c11ab1ae6a897f4ae4f8239381d764c9b8233d1a2&
[17:43:06] <MirahezeRelay>	 <posix_memalign, replying to abaddriverlol> [1/2] It worked after I enabled this beta feature. Very nice.
[17:43:06] <MirahezeRelay>	 <posix_memalign, replying to abaddriverlol> [2/2] https://cdn.discordapp.com/attachments/615786602454581249/1391474551480651837/image.png?ex=686c0729&is=686ab5a9&hm=e98751e0e7285df56cd1f5edd4d96d1c70729aaf0326d54972d722bf01f1a9ac&
[17:44:10] <MirahezeRelay>	 <abaddriverlol> Ah, then I probably already had it enabled but forgot about it
[17:56:54] <MirahezeRelay>	 <rhinosf1, replying to abaddriverlol> You might have enable all beta features on
[20:36:47] <MirahezeRelay>	 <abaddriverlol> I don't, I think I tested this feature on beta some time ago
[20:43:07] <MirahezeRelay>	 <posix_memalign> [1/3] https://exttest.mirabeta.org/wiki/CSS/Test1
[20:43:07] <MirahezeRelay>	 <posix_memalign> [2/3] https://exttest.mirabeta.org/wiki/CSS/Test2
[20:43:07] <MirahezeRelay>	 <posix_memalign> [3/3] I'm surprised that Extension:CSS allows unprivileged users to do something like these...
[20:50:16] <MirahezeRelay>	 <abaddriverlol> Afaik it doesn't really sanitize CSS apart from removing functions like url() that could be used to leak IPs/user agents
[21:37:20] <MirahezeRelay>	 <theoneandonlylegroom> hmmmmm
[22:00:24] <MirahezeRelay>	 <posix_memalign, replying to abaddriverlol> Lack of CSS sanitization is good for daring non-WMF wikis I suppose. Hence templatestyles/css co-existing.
[22:11:41] <MirahezeRelay>	 <blankeclair, replying to posix_memalign> https://www.youtube.com/watch?v=a5f07DKyi5s
[22:12:45] <MirahezeRelay>	 <pskyechology> oh no
[22:15:30] <MirahezeRelay>	 <blankeclair, replying to pskyechology> could be worse
[22:15:49] <MirahezeRelay>	 <blankeclair> https://www.youtube.com/watch?v=w4jLRhtBg7U
[22:16:53] <MirahezeRelay>	 <pskyechology> parallelograms your windows