[01:12:21] [1/2] fun fact: this is actually a good concept, and he did approach MH to use it, but its based on old tech that the WMF will no longer offer support for and is due to be wound down. And since there are no tests or anything or CI on the code, it was declined for MH. [01:12:21] [2/2] Slight necropost, I know, but heh fun facts. [03:13:26] Sad they are winding down ORES, I actually helped the team that made it out, I had admin on their github repos a couple years ago [03:13:47] Aaron Halfaker is a cool dude [03:46:22] [1/2] steam replay 2022 the sequel [03:46:23] [2/2] https://cdn.discordapp.com/attachments/615786602454581249/1190863493663051847/X.png?ex=65a3590e&is=6590e40e&hm=d9da61d872cdea7ab1be37f3d3fbe6d5a6703f7497debb0cc3c491105f3bfe25& [03:46:35] QUITE the step up huh [03:48:34] including offline hours isaac would probably have 7% more playtime [03:49:48] i 100%ed that game twice in one years it’s insane [03:50:27] chances are in 2024 it’ll probably take top 3 at the very least [03:55:13] Where do you check that? [04:03:20] [1/2] it's sidebar then this (on pc click ur name at the top) [04:03:20] [2/2] https://cdn.discordapp.com/attachments/615786602454581249/1190867762222997725/IMG_9703.png?ex=65a35d07&is=6590e807&hm=7031ef6f9e41c42d9899e10506f882662b65bb6470f9082557205c51dc173a7b& [11:28:31] Yeah, it does seem they are replacing it with something else though so 🤷 [11:29:32] But hey I’ve been starting at ClueBot NGs repo long enough that I’ve deluded myself into thinking I understand how to self run it [11:31:54] Literally gonna rewrite the bot part cause I don’t know PHP and that would need customization [11:33:17] Also looks like it gets data directly from a copy of Wikimedia’s production database [11:33:42] And unless fandom wants to give me root access to prod uh [11:33:48] ¯\_(ツ)_/¯ [11:34:24] Gonna be a pain in the ass, it would need like 4 different API requests for every recent change to get all the info required [11:41:35] Wiki.js is a great option for when you want a wiki but MediaWiki is too much work [11:49:56] right [11:50:04] not to mention [11:50:35] this thing presents itself as github? like github isn't confusing to regular user? [11:54:19] GitHub is relatively easy to use, come on. [11:55:28] nope [11:55:37] even I fail at it [12:15:05] I’ve never had issues [13:07:32] Never used it, how’s it different? [13:39:39] Anything that uses PHP has the additional weight of managing that side of it, and Wiki.JS eliminates it, also the management interface is all on one page and fullyt web based. [13:40:29] PHP is a pain [13:40:46] I managed a lot of XenForo and PhpBB/FluxBB forums during the time, it's a hellscape. [13:41:06] Nevermind the potential for exploits to blow up the whole thing with one file. [13:42:34] I can tell you, as of now phpBB has at least one vuln that allows anyone (as long as they can access the forum) to run whatever they desire and blow up the forum from there. AFIK it has only been used once. [13:43:43] Dang [13:44:44] Also it has to do with why I do not use Wordpress. [13:47:26] https://gohugo.io/ - static, drop dead easy to use, uses markdown for content. What else? [15:30:31] happy new year [15:31:37] oi [18:03:28] [1/3] this band's management or whatever is living in some strange plane of reality [18:03:28] [2/3] I don't even like this album/era but as hyperfixated fan devoted to documentating and archiving shit I'm just <:moonch:794697217826095165> [18:03:29] [3/3] https://cdn.discordapp.com/attachments/615786602454581249/1191079189827297370/IMG_20231231_204909.jpg?ex=65a421f0&is=6591acf0&hm=b0599c7697605c5198c41ecb3cb8d1cda79090f01a6113a32de80d30187d42e4& [18:06:12] [1/3] >release bonus stuff strictly on vinyl and CDs in limited quantities [18:06:13] [2/3] >fans who aren't into physical formats or just broke beg for digital versions [18:06:13] [3/3] >release digital version w/ more bonus stuff limited to even LESS amount of copies (for £30) [18:19:13] [1/2] and guess? [18:19:14] [2/2] those who already own vinyls and CDs will buy it! [18:25:14] stonks [18:25:20] well not for the fans [23:07:29] * RhinosF1 sees dmehus has shown up [23:12:02] hey RhinosF1, what are your New Year's plans? [23:15:08] I haven't seen Dmehus in a while [23:15:20] hey tali64 :) [23:16:51] * dmehus bets RhinosF1 will have a drink or two this New Year's Eve [23:16:51] didn’t know irc had that [23:19:13] dmehus: I'm in bed. No alcohol. I will go to the window as the fireworks from the pub start. [23:26:52] What about you dmehus [23:28:47] RhinosF1: cool, sounds much like my plans then...if I can stay up to midnight my time (7.5 hours to go) [23:33:01] dmehus: I read your RfC comments [23:33:09] WikiTide will be complying with GDPR [23:33:29] and any other data protection laws that apply in a users home country [23:33:56] And also any data transfer would be fully compliant with EU law & the obligations that exist [23:34:34] I would also say that database migrations really aren't as messy as you think if both platforms are on the same mediawiki version [23:34:56] * RhinosF1 already has a plan for central auth and has spoken numerous time with the WikiTide team [23:36:05] Indeed. [23:36:23] WikiTide incorporated is still required to comply with GDPR for any citizens of a relevant country. I believe that's a misunderstanding of the law that GDPR would not apply. [23:36:51] before I finally go sleep - question [23:36:57] RhinosF1: that's good to hear re: GDPR compliance. As for database mergers, we've had issues in the past with Betaheze, so things like that make me nervous [23:37:15] This wouldnt be like betaheze. [23:37:34] Oh? [23:38:04] there will be some threshold? time between vote deadline and announcement of what path Miraheze is choosing [23:38:27] or the year in some time zone will start w/ a bang [23:38:30] eh no - not really [23:38:36] yep - EST [23:38:51] 1C will be adopted by Miraheze and approved, pending some insane voting in the next few hours [23:39:00] dmehus: the issues with betaheze are down to resource issues meaning caches got mixed up [23:39:09] There's no cache pollution from two farms [23:39:17] I asked board members tbb [23:39:17] Or I don't see any reason why there should be [23:39:20] Miraheze board will take some time to ratify I'm sure (not sure how long), but MH board has always said they'd go with community decision [23:39:28] theoneandonlylegroom: a merger, should that outcome prevail, would not take place immediately. I suspect there would be at least a three week lag time before that would be effected, perhaps longer [23:39:31] I asked board members tbh [23:39:46] RhinosF1:, oh was that the only reason behind Miraheze and Betaheze? [23:39:52] Pretty much [23:39:54] Yeah RhinosF1 just simplified my explanation significantly. But that is a better explanation and accurate. [23:40:05] RhinosF1: ack, thanks :) [23:40:08] Pretty sure they'll say the same thing (cc: @cosmicalpha) [23:40:18] theoneandonlylegroom: fair. @Owen: ^ [23:40:18] Betaheze was significantly under resourced because SRE have never invested in it [23:40:26] obviously, but I meant like an announcement, maybe w/ @/everyone lol [23:40:38] true [23:40:56] I will within the next few days publish an actual idea of how technically I think the merger should work [23:41:09] And lots of thoughts of Tide's technical setup [23:41:24] RhinosF1: that's good. Phabricator task/paste? [23:41:32] No idea yet [23:41:36] ah [23:41:39] The merger will take several months to fully complete, but the initial steps would be taken soon if not immediately. [23:41:52] eventually we'll need to migrate Phabricator to Phorge, but that'll come later [23:41:54] The fire works are very early [23:42:03] brandon, respectfully - ain't taking your words [23:42:03] dmehus: we're running ohorge [23:42:05] That is already done dmehus [23:42:16] because you tend to go like [23:42:25] onto different things [23:42:43] RhinosF1, CosmicAlpha: really? It showed Phabricator when I logged in...I knew WikiTide was on Phorge [23:42:48] confused as to what that has to do with anything...? 😆 [23:43:09] Both MH and WT use Phorge now. [23:43:16] CosmicAlpha: ah [23:43:17] I tend to delve into tangents, true, but am pretty confident in what I've said. [23:43:23] Brandon & Lego: be civil [23:43:34] I am not starting 2024 pissed off at users [23:43:55] Lego [23:43:57] mate [23:44:10] why you had to do this to me lmao [23:44:16] dmehus: on the side of the law, they are many discussions about gdpr happening but it still applies. They are a lot of rules about transferring data and it's heavily regulated. [23:44:20] /it's fine/ [23:44:26] Although the ICO are nice people [23:44:38] At least based on my 4 discussions so far [23:44:39] RhinosF1, you've made hungry for an Eggo waffle now [23:45:06] With fossbots / Miraheze for breaches and with my personal life for companies that won't follow the law [23:45:43] Indeed. Everything will be done 100% legally. The GDPR will continue to apply to EU/UK residents at the very least. [23:45:59] good night people [23:46:03] happy new year [23:46:12] looking forward for good stuff [23:46:19] RhinosF1: yeah, that's true...I just mean that for corporations in other countries (i.e., Canada), they're subject to the privacy laws of Canada. Many will adhere to the GDPR either because they have to because they have EU subsidiaries or affiliates or in practice as a best practice, but not all do [23:46:26] and brighter future of mira ofc [23:46:36] dmehus: they don't and they can be prosecuted [23:46:52] GDPR applies to EU/UK citizens data [23:46:53] CosmicAlpha: I'm pleased to here that, and, of course, COPPA comes back for U.S. residents [23:46:58] No matter where you are based [23:47:20] RhinosF1, yeah, but EU courts have little jurisdiction over solely Canadian or U.S. firms [23:48:03] dmehus: well I'm sure CosmicAlpha doesn't need the threat of me taking regulatory action against him [23:48:34] I've complained against companies on 2 occasions for breaches of GDPR / DPA [23:48:49] One was upheld and one is still in progress [23:49:56] RhinosF1: lol, true. On the other hand, I've had issues with a UK company not complying with Canadian anti-money laundering and KYC verification laws (Wise). They seem to believe they're only subject to UK laws... [23:50:24] US authorities have jurdisticion over transfer of data too [23:50:31] I believe it's the FTC in our case [23:50:49] dmehus: then you should notify the responsible regulator [23:50:49] yeah [23:50:56] dmehus: also just to note WikiTide is not an LLC as you call it on the RfC, just thought I would clarify that. [23:51:23] RhinosF1: I probably will eventually, yeah [23:51:27] dmehus: but ye in case you want to change your vote. You have a few errors. [23:51:41] CosmicAlpha: oh, it's not? What's the legal name? [23:51:52] * RhinosF1 is currently arguing with his bank over their failure to comply with GDPR and expects a decision from the ICO soon [23:52:02] dmehus: WikiTide Incorporated [23:52:28] WikiTide Foundation, Inc. On the secretary of state, and WikiTide Incorporated to the IRS. [23:54:37] CosmicAlpha: it's two entities, then? Otherwise, why would it be different for the IRS? [23:54:52] One is pending update [23:55:04] RhinosF1: ah, that makes sense, thanks :) [23:55:07] Agent said the right paperwork has been done [23:55:14] * RhinosF1 has already asked that [23:55:20] Yeah, that's correct. [23:55:31] I've spent the last week grilling Agent, NotAracham and CosmicAlpha and listening to users [23:55:37] heh [23:55:58] Has Reception123 been around lately? [23:56:07] Yes [23:56:15] I spoke to them on discord this morning [23:56:23] To moan about French strikes [23:56:35] RhinosF1: oh that's good :) [23:57:13] * RhinosF1 passes through St Pancras on his way between parents and where he lives [23:57:21] * RhinosF1 is doing to journey home tomorrow