| Time |
Nickname |
Message |
|
00:31
🔗
|
|
Dj-Wawa has quit IRC (Quit: Connection closed for inactivity) |
|
02:48
🔗
|
|
systwi has quit IRC (Remote host closed the connection) |
|
03:17
🔗
|
|
systwi has joined #urlteam |
|
03:46
🔗
|
|
odemg has quit IRC (Ping timeout: 246 seconds) |
|
04:17
🔗
|
|
CyberVenu has joined #urlteam |
|
04:19
🔗
|
|
CyberVenu has quit IRC (Client Quit) |
|
04:19
🔗
|
|
CyberVenu has joined #urlteam |
|
04:21
🔗
|
CyberVenu |
I’m curious, is the tracker managed in some way that it could be easily split to have multiple instances of the program running, perhaps 1 instance per domain? Something to have better redundancy should the tracker go offline at some point? |
|
04:22
🔗
|
CyberVenu |
Basically I’m curious if I could volunteer to run an instance of the tracker under such circumstances, but I don’t think I should like run the only instance if the tracker or anything crazy like that. |
|
04:26
🔗
|
|
CyberVenu has quit IRC (Ping timeout: 260 seconds) |
|
04:31
🔗
|
chfoo |
the database is mostly database agnostic. the job quota logic is done in memory and would require rewriting it to work with redis or something similar |
|
04:34
🔗
|
chfoo |
it was never envisioned to run more than 5 shorteners at a time. it just happened to scale up to the single thread bottleneck |
|
05:50
🔗
|
Flashfire |
we didnt think people would be this stupid basically? |
|
06:19
🔗
|
|
kiska1 has quit IRC (Remote host closed the connection) |
|
06:19
🔗
|
|
kiska1 has joined #urlteam |
|
06:19
🔗
|
|
Fusl_ sets mode: +o kiska1 |
|
06:19
🔗
|
|
Fusl sets mode: +o kiska1 |
|
16:53
🔗
|
|
yano has quit IRC (Remote host closed the connection) |
|
16:53
🔗
|
|
yano has joined #urlteam |
|
18:44
🔗
|
|
Dj-Wawa has joined #urlteam |
|
19:04
🔗
|
|
Video has quit IRC (Quit: Page closed) |
|
22:44
🔗
|
|
Dj-Wawa has quit IRC (Quit: Connection closed for inactivity) |