HomeSearchPrevious dayNext day

00:14:54<Irenes>so apparently the Google Groups copy of the historical Usenet archives is less complete than it used to be? is there another comprehensive archive of it somewhere already? https://hachyderm.io/@Obdurodon/110556152642370376
00:15:10<Irenes>this is just one person's observation
00:15:13<Irenes>not a press release or anything
00:50:23Pixi joins
01:23:29mike joins
01:23:45mike is now known as savethestuffyo
01:27:16<Roki_100|m>yo, anyone built an unofficial build of warrior for arm64 yet? i've seen projects like reddit are but warrior would be interesting to run on a pi
01:30:39<nicolas17>Roki_100|m: we don't want unofficial builds here
01:30:41<@JAA>Roki_100|m: Please don't.
01:30:58<nicolas17>wget-at needs to be thoroughly tested to ensure it works correctly on arm64
01:30:59<@JAA>wget-at has not been verified to work correctly on non-x86 architectures.
01:32:41<Roki_100|m>i mean who is supposed to test it if not the community, by looking at the initial issue its not moving for years and its just ignored
01:33:01<Roki_100|m>but whatever i wont then ig
01:33:41<@JAA>Not sure what issue you were looking at, but I explained it in more detail here at the end: https://github.com/ArchiveTeam/warrior-dockerfile/issues/56
01:35:55<nicolas17>Roki_100|m: do you have your own tracker then?
01:36:40<nicolas17>you can't test it live against real projects
01:38:17<Roki_100|m>nicolas17: i mean this response just makes no sense, the issue linked above is *2 years old*, and no real progress seem to have been made
01:38:17<Roki_100|m>i dont have my own tracker but archiveteam doesnt seem to care enough about arm either
01:39:16<nicolas17>okay, how are you going to test it without uploading corrupted data to the project if your build turns out to be broken?
01:42:12<Roki_100|m>im, myself not going to, thats the point, but people do that due to lack of "official" progress, so i just asked out of curiosity after all, its no mystery people that *can* really test it off production could do so within few months probably, i dont think checking if something returns corrupted data takes 2 years, especially considering the fact arm images existed in the past from what i see?
01:43:40<nicolas17>I remember someone tried it recently, his procedure was "it's not giving any visible errors so it must be working fine", and it turns out he already had a reputation of screwing things up in other (non-archiveteam) projects
01:45:47<@JAA>Roki_100|m: Have you read my comments on the issue I linked?
01:47:14<@JAA>The sad fact is that only a couple people are familiar enough with the subtle details to do this work, and these people (myself included) are already lacking the time to do the dev things they want to do.
01:49:03<nicolas17>too bad #imgone doesn't have public logs, that chat with Remocracy would be worth saving lol
01:49:04<Roki_100|m>JAA: yes i have just now, it makes things a little bit clear, my apologies
01:58:06Arcorann (Arcorann) joins
02:20:26TheTechRobo quits [Client Quit]
02:21:56<tech234a>Google Album Archive shutting down July 19 https://support.google.com/picasa/answer/7008270
02:24:27<tech234a>More info: https://cordcuttersnews.com/google-is-shutting-down-album-archive/
02:25:03<tech234a>Seems like some data will be deleted, not sure if public
02:32:31<myself>out of curiosity, would an x86-on-arm emulator like qemu have the same concerns? If it had any basic errors in endianness or whatever, presumably they'd show up in grievous ways and nothing would run at all, so...?
02:38:29<dave>Album Archive seems to be the landfill area where images were sent after previous Google shutdowns. My "Album Archive" contains images I posted on Google+ and in Hangouts chats
02:38:49<dave>so... I don't think it's anything public, they're literally killing off the bin where data from other killed things goes
02:46:52<pabs>from the HN comments "this is basically a collection of media you uploaded to Blogger, Hangouts, and Picasa Web Albums." https://news.ycombinator.com/item?id=36366105
02:46:54<pabs>"The images will not be deleted when it's killed because they actually reside in other products such as Blogger and will still be downloadable using Takeout"
02:50:05<dave>yeah but what about images from dead products? Those don't have any other home.
02:58:03<pabs>I guess they would be gone
02:59:44<nicolas17>https://twitter.com/defunkt/status/1669814114259202048
03:03:10TheTechRobo (TheTechRobo) joins
03:09:13skyrock3t joins
03:10:20skyrocket quits [Ping timeout: 265 seconds]
03:30:33<fireonlive>lol
03:31:38<fireonlive>also like domains registered via google workspace are ok and will stay with google and domains in “Google Cloud Platform Domains” are staying with google??
03:32:09<fireonlive>and you transfer your domains from Google Domains to Google Cloud Platform Domains apparently without too much trouble
03:32:22<fireonlive>you can*
03:33:06<JTL>I was curious about Google Cloud Domains, yes
03:39:37<yasomi>fireonlive: google cloud domains is getting axed too
03:39:57<JTL>eek! :P
03:54:26<fireonlive>:o those too
03:54:39<fireonlive>damn i heard those were safe lol
03:54:41<fireonlive>tks
04:09:36skyrock3t quits [Client Quit]
04:15:03DLoader quits [Ping timeout: 258 seconds]
04:15:22skyrocket joins
04:17:46<dave>not officially confirmed I don't think, but insider info going around that Google Cloud Domains runs on consumer Google Domains under the hood, so it's now "deprecated" because its entire infrastructure got sold
04:18:45DLoader joins
04:22:17hitgrr8 joins
04:23:47skyrocket quits [Ping timeout: 252 seconds]
04:30:01HP_Archivist quits [Read error: Connection reset by peer]
04:42:31skyrocket joins
04:46:51systwi quits [Read error: Connection reset by peer]
04:46:52systwi_ (systwi) joins
04:53:29Hajdar2 quits [Client Quit]
05:04:25skyrocket quits [Client Quit]
05:10:57skyrocket joins
05:19:45railen64 joins
05:20:50Earendil7 quits [Ping timeout: 265 seconds]
05:22:37skyrocket quits [Client Quit]
05:23:04Hajdar (Hajdar) joins
05:23:36skyrocket joins
05:23:44railen69 quits [Ping timeout: 265 seconds]
05:28:22justmolamola joins
05:30:12AmAnd0A quits [Remote host closed the connection]
05:30:29AmAnd0A joins
05:36:01graham quits [Client Quit]
05:58:59Earendil7 (Earendil7) joins
06:16:32skyrocket quits [Ping timeout: 252 seconds]
06:30:01skyrocket joins
06:51:42dumbgoy_ quits [Ping timeout: 265 seconds]
07:11:49nicolas17 quits [Client Quit]
07:12:56yts98 leaves
07:12:59yts98 joins
07:45:33skyrocket quits [Client Quit]
07:49:46skyrocket joins
08:07:05skyrocket quits [Ping timeout: 252 seconds]
08:07:48skyrocket joins
08:16:46sepro quits [Ping timeout: 265 seconds]
08:31:04decky_e quits [Client Quit]
08:41:18decky_e (decky_e) joins
08:42:17skyrock3t joins
08:43:23skyrocket quits [Ping timeout: 252 seconds]
08:45:19<h2ibot>Yts98 edited Banciyuan (+7505, Update website structure): https://wiki.archiveteam.org/?diff=49953&oldid=49945
08:54:23<masterX244>When was that chat with remo nicolas17?
08:54:54<masterX244>anyone using quassel or matrix and bein in the chat while it happened got it logged
09:04:59Island quits [Read error: Connection reset by peer]
09:43:15systwi_ quits [Read error: Connection reset by peer]
09:44:25systwi (systwi) joins
09:53:29<flashfire42>https://transfer.archivete.am/15zTwt/Starting%20CheckIP%20for%20Item1.txt can anyone answer wtf this means in relation to the DPReview warrior project?
10:00:02railen64 quits [Remote host closed the connection]
10:00:17railen64 joins
10:16:38Gereon quits [Ping timeout: 265 seconds]
10:16:45arct quits [Remote host closed the connection]
10:19:05T31M quits [Client Quit]
10:19:25T31M joins
10:28:10Gereon (Gereon) joins
10:50:16<flashfire42>kaz see above you got any idea?
10:53:44<@kaz>no idea
10:54:49spirit quits [Quit: Leaving]
11:00:53Ruthalas5 quits [Ping timeout: 252 seconds]
11:09:16Ruthalas5 (Ruthalas) joins
11:30:02TastyWiener95 quits [Ping timeout: 252 seconds]
11:30:32TastyWiener95 (TastyWiener95) joins
11:52:40decky_e quits [Remote host closed the connection]
12:40:42pseudorizer (pseudorizer) joins
12:54:28dumbgoy_ joins
13:05:30that_lurker quits [Client Quit]
13:05:41that_lurker (that_lurker) joins
13:09:32pseudorizer quits [Client Quit]
13:17:05AmAnd0A quits [Ping timeout: 258 seconds]
13:17:37AmAnd0A joins
13:28:42nighthnh099_ joins
13:31:33pseudorizer (pseudorizer) joins
13:32:39nostalgebraist joins
13:43:21AmAnd0A quits [Read error: Connection reset by peer]
13:43:38AmAnd0A joins
13:50:08AmAnd0A quits [Read error: Connection reset by peer]
13:50:23AmAnd0A joins
14:01:51nighthnh099_ quits [Client Quit]
14:08:59Arcorann quits [Ping timeout: 252 seconds]
14:18:37railen69 joins
14:22:10railen64 quits [Ping timeout: 265 seconds]
14:23:25HP_Archivist (HP_Archivist) joins
14:24:23<@JAA>myself: I'd expect emulation to be fine, yes. But it hasn't been verified either.
14:29:54BearFortress quits [Read error: Connection reset by peer]
14:34:15wyatt8740 quits [Ping timeout: 265 seconds]
14:34:50rubberduckie quits [Ping timeout: 252 seconds]
14:51:34<myself>What's involved in verification, could someone set up a test suite? That sounds like it might be doable by anyone with skills, but not necessarily internal knowledge. (Probably better if they don't have preconceptions about what they're testing, eh?)
14:52:50<@JAA>A test suite for WARCs is sorely needed but doesn't exist. Yeah, doesn't necessarily require internal knowledge, although we're still the only ones using .warc.zst.
14:54:06<myself>is it deterministic enough that simply crawling the same set of input should always produce the same output, identical to the bit? I suppose timestamps might mess with that..
14:54:43<@JAA>With a suitable HTTP server, it can be pretty deterministic. Apart from the timestamps, yeah.
14:55:35<@JAA>You'd need pretty low-level control of the HTTP server anyway to test funny edge cases (whitespace in headers or chunk lines, capitalisation differences, etc.). So hardcoding the Date header is trivial.
14:55:52<myself>Sounds like it's not really an HTTP server such as an expect script
14:56:03<@JAA>And on the WARC software (i.e. wget-at) side, you'd need faketime or similar.
14:56:48<myself>Hmm. Though if things get multithreaded, a real HTTP server is probably indicated.
14:57:27<@JAA>Oh yeah, WARCs also contain random record IDs (UUIDs). So I guess faketime isn't needed since that needs to be treated specially anyway.
14:57:58<myself>Oh that makes sense, yeah. So the output verifier needs handling for all that.
15:01:14Pixi quits [Ping timeout: 252 seconds]
15:16:41nostalgebraist quits [Client Quit]
16:18:50rubberduckie joins
16:59:11emily (pseudorizer) joins
17:01:40pseudorizer quits [Ping timeout: 265 seconds]
17:03:35railen64 joins
17:06:30railen69 quits [Ping timeout: 265 seconds]
17:09:36railen69 joins
17:13:16railen64 quits [Ping timeout: 265 seconds]
17:13:46emily quits [Read error: Connection reset by peer]
17:24:40pseudorizer (pseudorizer) joins
17:41:13BearFortress joins
18:07:15skyrock3t quits [Client Quit]
18:30:51skyrocket joins
18:41:00Dallas (Dallas) joins
18:46:28Ketchup901 quits [Remote host closed the connection]
18:48:49Island joins
18:49:33Ketchup901 (Ketchup901) joins
18:58:47decky_e (decky_e) joins
19:29:44jacksonchen666 (jacksonchen666) joins
19:42:02AmAnd0A quits [Remote host closed the connection]
19:42:15AmAnd0A joins
19:55:36justmolamola quits [Remote host closed the connection]
20:02:55lennier1 quits [Ping timeout: 265 seconds]
20:05:22<h2ibot>Yts98 edited Banciyuan (+752, Update website structure): https://wiki.archiveteam.org/?diff=49954&oldid=49953
20:06:45wyatt8740 joins
20:13:23Twisty quits [Remote host closed the connection]
20:19:13yts98 leaves
20:19:54wyatt8740 quits [Ping timeout: 258 seconds]
20:20:09wyatt8740 joins
20:35:49sepro (sepro) joins
20:37:17wyatt8740 quits [Ping timeout: 252 seconds]
20:37:32wyatt8740 joins
20:42:17decky_e quits [Remote host closed the connection]
20:43:05yts98 joins
20:45:06Aoede quits [Quit: ZNC - https://znc.in]
20:47:54Aoede (Aoede) joins
20:48:29decky_e joins
20:48:38yts98 leaves
20:50:43Dallas quits [Client Quit]
20:54:54<@arkiver>JAA: is Game Atsumaru something for ArchiveBot?
20:54:57<@arkiver>deadline on 28th
20:55:07infiliotech quits [Ping timeout: 265 seconds]
20:56:57<@arkiver>yts98: i see you're not online, but in case you read this later, very nice details about Banciyuan on the wiki!
21:01:38<Naruyoko>I suppose someone's going to archive Miraheze anyways, should I be concerned about this wiki regardless? https://incrementalgames.miraheze.org/wiki/Main_Page
21:02:46<@arkiver>Naruyoko: you can bring it up explicitly in #wikiteam
21:03:05<@JAA>arkiver: Game Atsumaru seems to heavily rely on JS for the games themselves, so probably not.
21:17:05hitgrr8 quits [Client Quit]
21:34:14blake0201 joins
21:34:38blake0201 leaves
21:34:55blake020165 joins
21:37:55blake020165 quits [Remote host closed the connection]
21:58:17yts98 joins
21:58:25nicolas17 joins
22:00:05Hajdar quits [Remote host closed the connection]
22:00:24Hajdar (Hajdar) joins
23:34:24geezabiscuit quits [Read error: Connection reset by peer]
23:35:49geezabiscuit (geezabiscuit) joins
23:36:04Ketchup901 quits [Remote host closed the connection]
23:38:44Ketchup901 (Ketchup901) joins
23:53:32BlueMaxima joins

HomeSearchPrevious dayNext day