02:21:03 tracker is fixed again, sorry for the trouble 02:21:16 blame fionera for absolutely no reason, thanks 02:53:47 lol 03:11:59 tech234a: Thanks for the edits. I've been wondering about this. We should probably just switch Template:IRC to default to hackint since we don't have anything on EFnet anymore. Only downside is that it'll change the old project pages as well, but those channels are dead anyway. 03:13:13 Yeah it looks like everything that's active has moved at this point right? 03:13:45 Most of the project channels have been over here already for a while anyway. 03:15:19 -purplebot- 1 edits not shown 03:15:19 -purplebot- Dev/Staging edited by Tech234a (+2, Switch EFnet reference to hackint) just now -- https://www.archiveteam.org/?diff=45718&oldid=23598 03:15:19 -purplebot- Frequently Asked Questions edited by Tech234a (+10, Switch EFnet reference to hackint) just now -- https://www.archiveteam.org/?diff=45717&oldid=43524 03:15:19 -purplebot- ArchiveBot edited by Tech234a (+2, Switch EFnet reference to hackint) just now -- https://www.archiveteam.org/?diff=45719&oldid=45661 03:15:19 -purplebot- ISP Hosting edited by Tech234a (+7, Switch EFnet reference to hackint) just now -- https://www.archiveteam.org/?diff=45720&oldid=45362 03:15:20 -purplebot- University Web Hosting edited by Tech234a (-58, Switch EFnet reference to hackint) just now -- https://www.archiveteam.org/?diff=45721&oldid=45374 03:28:43 JAA: is there a page for older projects?... it seems anything left on the homepage on EFNet is old or inactive and this may be a good opportunity to declutter the homepage 03:31:02 tech234a: Yeah, that section isn't being kept up to date at all. :-| 03:31:14 There is another page which is even more out of date. 03:31:44 https://archiveteam.org/index.php?title=Warrior_projects 03:31:54 Well, current ones are in, but everything from 2017 and 2018 is missing. 03:32:12 We could do a better job at documenting things. 03:39:12 Found this from 2009: https://archiveteam.org/index.php?title=TEMP:Columned_frontpage_prototype 03:43:19 -purplebot- NewsGrabber edited by Tech234a (+24, Switch EFnet reference to hackint) just now -- https://www.archiveteam.org/?diff=45722&oldid=30831 03:43:19 -purplebot- Current Projects edited by Tech234a (+160, Switch EFnet references to hackint) just now -- https://www.archiveteam.org/?diff=45723&oldid=45685 04:20:30 The wiki is like something from fiction - an old building, that people keep adding rooms to, and abandoning the old ones 04:21:01 Sounds like an SCP alright. 04:21:21 Maybe write some sort of script to add the parameter, before the template is changed? Might be hard to find logs or similar otherwise 04:21:21 And yes, very accurate. 04:21:41 Nah, let's not go down that route. 04:21:54 The project channels aren't logged anyway. 04:22:00 (Most of the time) 04:22:03 Oh, I suppose you're right 04:22:36 If noone shouts at me, I'll switch the default later. 04:30:25 OrIdow6: I could just add it to those manually, I was gonna look into how long it would take anyways. At this point though it might make sense to just remove those channels from pages so people are directed to #archiveteam instead of an empty channel. 04:32:06 I've been wondering whether we should switch the default channel on project pages to -bs also. 04:32:18 -purplebot- NewsGrabber edited by Hook54321 (+46) 18 minutes ago -- https://www.archiveteam.org/?diff=45724&oldid=45722 04:32:22 It's basically never appropriate to talk about existing projects in #archiveteam. 04:35:15 imo it should be something on the order of '#original (defunct, use #archiveteam-bs)' 04:37:03 i'd be willing to help fix the existing pages (i feel like hiding that info and ending up with something misleading is against the at mission :P) 04:38:00 Yeah, I thought the other day about adding a `dead` parameter to the IRC template, which would produce something like that. 04:38:10 (even if project pages aren't logged, it can be helpful for e.g. knowing where in your own logs to check) 04:38:14 seems unnecessary to me, but eh. people can find it in the revision history, not really hiding. 04:38:15 i think that's a good idea 04:38:35 (s/pages/channels/) 04:39:50 I agree with thuban that it'd be good to keep the original channel name there. 04:41:20 One thing I'd love to see is Semantic MediaWiki or similar where we put everything on the project page and then it places all pages with some category on the homepage, adds them to the 'Warrior projects' page, and possibly other things. 04:41:53 But that's probably too much work for this. 04:42:02 huh, can you not get mediawiki to do that? 04:42:57 Well, the pages themselves yes, but I also mean the IRC channel etc. Not possible with stock MW as far as I know. 04:43:14 ah, i see. pity 04:43:14 Well, I guess you could use and , but that's gross. 04:56:30 * Doranwen recommends putting the new version *first* though, if you're going to include both 04:56:48 like #archiveteam-bs (formerly #original) 04:56:57 put "formerly" in () with the old name 04:57:25 the way people think is the current thing should be the first visible one, with the history after that or tucked away somewhere accessible 04:57:35 you never want to put the old/defunct thing first, because it confuses people 04:59:20 people are notoriously terrible at skimming and picking up the first/main things and missing minor details, and if you stick the old/defunct thing first, there's a much higher probability of someone failing to see the addendum in parentheses noting the new/current one 04:59:29 Yes, good point. 04:59:33 Absolutely. 08:18:46 mgrandi Macricke from VGPC figured out an awesome trick: 08:19:25 Hi, I managed to get some JSON api, which I think is a lot easier to download the info 08:20:26 for some reason Sony decided to roll out the new design to the mobile app next week (28th October)Archive Team can force the old store by having the crawler pretend to be the mobile app`?scope=sceapp&smcid=psapp`if you append that to the end of the string in the URL field, it will force the old site to loadso Archive Team should be able to capture 08:20:26 all pages before the 28th[storeURL]/product/[contentID]?smcid=psappstoreURL would be any of the 94 on the list I gave you and contentID would be something like “EP1001-CUSA18100_00-MAFIAONEREMASTER” which is a unique ID given to each and every product listed on the PS Store 08:21:03 hmm 08:21:15 I think it might need the host key set too, i dunno 08:21:35 I don't think scraping the store is going that well, their app seems to be very javascript heavy and i'm noticing that wget-at is not fetching imgaes 08:21:37 I don't think scraping the store is going that well, their app seems to be very javascript heavy and i'm noticing that wget-at is not fetching images 08:21:49 (sorry, force of habit from teams lol) 08:22:06 Amazingly iy seems to Just Work − https://store.playstation.com/ja-jp/product/JP9000-NPJA00045_00-DETUNED000000001?scope=sceapp&smcid=psapp works but wihtout it does not resolve 08:22:48 hmm ok, that might make it easier to get the list of urls 08:23:11 so : do you know if the SKUs are region specific? like is JP9000-NPJA00045_00-DETUNED000000001 japan only 08:24:22 Macricke helped me there to, they said: "there was discussion around how content IDs are linked to store regions e.g. UP0001 for US, EP0001 for Europe, HP0001 for Asia…that’s not strictly the case. There is loads of UP or EP content on the Japanese storefront, for example. So I believe to be safe we’d need to try every possible combination of 08:24:22 [storeURL] and [contentID] otherwise there’s a risk of missing a bunch of content" 08:24:47 so what i'm thinking of doing, is going to each major region's grid page 08:24:50 getting a list of SKUs 08:25:23 then getting this api called 'valkyrie' to get basic information about the game for each major language: `curl https://store.playstation.com/valkyrie-api/ja/JP/999/resolve/JP9000-NPJA00045_00-DETUNED000000001` 08:25:54 The complete SKU list should be on SerialStation.com in theory − asked the owner for a dump of the SKUs as well ; they told me they might be able to hand me out a script that goes through the API (either the Valkyrie API or the other Chihiro API − I dunno, it’s a bit out my league ^^) 08:26:26 if you could get one of them to join this IRC or maybe ping me on discord or something i can try 08:26:43 basically this is what i've come up with, i think the JSON api response + images is the most important at the moment 08:26:47 They hang out on the VGPC discord 08:27:22 if you have a link i'll join 08:27:49 https://discord.gg/AHTfxQV 08:28:06 but yeha, the API responses i think are what i should be targeting, the HTML is just...a rendered versions of this and take forever to do one region, and they are...aggressive at banning from hitting it too hard 08:35:02 I understand your position ; just to preach for my chapel: 1/ Fairly sure the JSON blobs and images hae been archived by VGPC people / mirrored in SerialStation and 2/ For Wikipedia purposes, it’s difficult to use an archived JSON blob as source for a statement (eg the USK or PEGI rating) while the store HTML page is good for it 08:36:34 (And yes, surprisingly, for some data, the only readily found and official looking source seems to be the Store HTML pages − community websites/DBs like MobyGames or SerialStation, however respectable and serious they are, do not cut it as "not official enough" :-( ) 08:36:54 Let’s continue on the VGPC discord :) 16:22:57 In about an hour I am going to upgrade gitea on git.kiska.pw :D 17:35:23 wooh 17:35:47 Starting upgrade now 17:35:58 :-) 17:38:03 Completed update to 1.11.8 :P 17:38:34 what is the new awesomeness 17:38:55 Probably not much :D 17:39:06 :P 17:39:30 Here are the changes: https://github.com/go-gitea/gitea/releases/tag/v1.11.7 and https://github.com/go-gitea/gitea/releases/tag/v1.11.8 17:39:33 It was 1.11.6 before, just a few bug fixes. 17:40:08 1.12.0 is where the cool new features are. 17:40:33 Looks like I don't need to worry about 1.12.0 breaking things? 17:40:48 There are some breaking changes, so not sure. 17:41:01 Also, this reminds me that I wanted to submit a PR for 1.13.0. 17:41:25 :D 17:41:37 Actually I am going to update to 1.12.5 and see what breaks :D 17:43:10 It seems that the breaking changes on 1.12.0 are not problematic. 17:43:11 Well nothing has exploded yet 17:44:41 JAA: Can you confirm you have received a test email from postmaster⊙kp? 17:45:29 kiska: Yep 17:45:31 :D 17:45:37 Well that didn't break 17:47:12 JAA: So what are the cool features? Before I go and look at the releases 17:50:26 A key one for me personally are system-wide webhooks. That'll allow for proper IRC notifications. I've been wanting to implement that for a while. 17:50:50 Now you can :D 17:51:31 Yeah, if only the webhook payload were documented at all... 17:51:38 Ooops? 17:52:12 https://docs.gitea.io/en-us/webhooks/ 17:52:15 That's all that exists. 17:52:27 Perhaps open an issue? 17:52:34 The example is 3.5 years old and doesn't even reflect the current hooks at all. 17:52:50 https://github.com/go-gitea/gitea/issues/9485 17:55:27 I see... 18:15:51 Cool, docs.gitea.io is always the master branch, not the latest release. WTF? 18:18:43 https://github.com/go-gitea/gitea/issues/5588 18:18:57 Baffles me that they didn't think of that for so long... 18:19:07 But well, the documentation is in a pretty sorry state anyway. 18:57:23 pct rescued: 47.21%, read errors: 247, remaining time: 1d 15h 18m 18:57:32 old cdr rescue 22:00:04 time to ask the important question 22:00:09 does gitea run in docker 22:00:14 cc kiska ^^ 22:25:34 No :D 22:41:03 maybe not _our_ gitea 22:41:07 but does it.. in general 22:41:18 Yes: https://docs.gitea.io/en-us/install-with-docker/ 22:41:34 kiska: remediate as above 22:42:18 there's nothing I'd love to see more than gitea running alongside watchtower 22:43:46 You know my stance with being at least a couple versions behind :D 22:45:13 Changing things would probably break the backups, and Igloo hasn't been around in a while. 22:45:26 I only updated to 1.12.5 because JAA wanted the cool feature 22:46:14 I believe Igloo is running it from /usr/local/bin/gitea --backup I think is the switch 22:46:40 But I have no clue 22:47:26 Sorry --dump is the switch 22:50:52 kiska: ~gitea/backup.sh (warning, pretty gross) 22:51:02 :D 22:51:08 Not gonna lookl 22:52:27 There's also at least three Gitea executables on this system. :-| 22:53:24 Oh well. In any case, yeah, if we change that, definitely make sure the backups aren't affected. 22:58:00 :D 22:58:17 Now down to 2 22:58:21 Where are the rest? 22:58:37 Found one in ~root and one in ~gitea, plus the one in /usr/local/bin. 22:59:08 Done :D 22:59:13 Now there is only 1 23:00:14 :-) 23:05:23 sod the backups 23:05:38 if it's in docker, we just sto the ct, pull the whole volume, start container 23:05:45 and thats the _worst case_ scenario 23:08:45 latest scans and tapes: https://www.patreon.com/posts/digitized-and-10-43228155 23:18:02 Anyway now with 1.12.5 installed on git.kiska.pw, I will not be updating to 1.13 until 1.15 has been released, unless JAA has a feature he would like