00:11:49Chris5010 quits [Ping timeout: 260 seconds]
00:21:36Chris5010 (Chris5010) joins
00:35:53DogsRNice joins
00:52:39tzt quits [Ping timeout: 260 seconds]
00:53:52tzt (tzt) joins
01:07:29<SUNDAY>am I still here? Am I the only living person?
01:09:10thenes quits [Remote host closed the connection]
01:09:30thenes (thenes) joins
01:13:21Reedy quits [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
01:13:40Reedy joins
01:25:47<anonymoususer852>I don't think running warrior on cloud/VPS instances would always be a wise choice, then again I have no clue.
01:27:51<anonymoususer852>The specifics on what is allowed and what isn't WRT the preferred connection type is on the wiki FWIW, https://wiki.archiveteam.org/index.php/ArchiveTeam_Warrior#Can_I_use_whatever_internet_access_for_the_Warrior?
01:31:59thenes quits [Remote host closed the connection]
01:32:15thenes (thenes) joins
01:47:16<anonymoususer852>Here is how I suppose it should look like with a clean connection, https://transfer.archivete.am/inline/coZ8m/Screenshot_2025-09-14.png
01:50:43<anonymoususer852>An unclean connection is likely to fail at the very beginning, CheckIP part. Almost every project has a series of URLs that the client runs through to verify their connection is clean, using a specific DNS provider.
02:00:46cyanbox joins
02:04:59<anonymoususer852>Someone else who runs Warrior on dedicated servers would be able to provide a more accurate answer. It is the weekend however, so chances of getting response may vary.
02:40:18<nstrom|m>Cloud/VPS is fine and many people do this. I think azure is banned due to someone doing something janky in the past
02:40:50<nstrom|m>Arkiver ^ FYI
02:45:07<nstrom|m>My only warning in running in something like AWS or Azure would be to watch out for data usage charges
02:46:19<nstrom|m>I much prefer running on unmetered connections or ones that throttle or just plain shut off when bandwidth is exceeded versus just running up a bill
04:27:32DogsRNice quits [Read error: Connection reset by peer]
04:48:53thenes quits [Remote host closed the connection]
04:49:17thenes (thenes) joins
05:04:04unknownsrc quits [Ping timeout: 260 seconds]
05:06:28unknownsrc (unknownsrc) joins
05:26:44unknownsrc quits [Read error: Connection reset by peer]
05:40:21unknownsrc (unknownsrc) joins
05:43:30unknownsrc quits [Client Quit]
05:45:02unknownsrc (unknownsrc) joins
05:50:09unknownsrc quits [Ping timeout: 260 seconds]
05:52:32unknownsrc (unknownsrc) joins
06:47:14Guest58 quits [Quit: My Mac has gone to sleep. ZZZzzz…]
07:03:55IDK quits [Quit: Connection closed for inactivity]
09:13:06Barto quits [Quit: WeeChat 4.7.1]
09:13:23Barto (Barto) joins
09:14:15Guest58 joins
10:02:04NatTheCat quits [Quit: Ping timeout (120 seconds)]
10:02:53NatTheCat (NatTheCat) joins
11:00:01Bleo182600722719623455222 quits [Quit: The Lounge - https://thelounge.chat]
11:02:55Bleo182600722719623455222 joins
11:08:33IDK (IDK) joins
11:15:23@rewby quits [Ping timeout: 258 seconds]
11:17:44Barto quits [Client Quit]
11:19:48Barto (Barto) joins
13:26:50rewby (rewby) joins
13:26:50@ChanServ sets mode: +o rewby
14:14:24Suika quits [Ping timeout: 258 seconds]
14:19:39Suika joins
16:01:02cyanbox quits [Read error: Connection reset by peer]
19:33:58DogsRNice joins
19:39:39tzt quits [Ping timeout: 260 seconds]
19:41:12tzt (tzt) joins
20:43:55IDK quits [Quit: Connection closed for inactivity]
22:23:15cyanbox joins
23:03:01tzt quits [Ping timeout: 258 seconds]
23:04:28tzt (tzt) joins